Devin

Devin works on a machine of its own in the cloud, on your repository, and takes MCP servers from Customize in its web app.

Set up

Step 1: Add the registry

Devin installs with the shadcn CLI in your project, so the project names cilo's two registries in components.json, @cilo-pro with the header that carries your licence key, and keeps the key in .env.local. Skip this if Installation already had you do it.

components.jsonJSON
{
"registries": {
"@cilo": "https://registry.cilo.com/r/styles/{style}/{name}.json",
"@cilo-pro": {
"url": "https://registry.cilo.com/r/styles/{style}/{name}.json",
"headers": {
"Authorization": "Bearer ${CILO_TOKEN}"
}
}
}
}
.env.local
CILO_TOKEN=your-licence-key

Step 2: Connect Devin

Use the access key supplied for MCP. Where a configuration below names CILO_MCP_TOKEN, export that variable in the environment that starts your agent. This is separate from the project’s CILO_TOKEN for pro installs; do not assume the two keys are interchangeable.

  1. In Devin, open Customize, then MCPs.
  2. Choose Add MCP, then Add custom MCP, and name it cilo.
  3. Pick the HTTP transport and set the Server URL to https://mcp.cilo.com.
  4. Set the Authentication method to Auth Header, with the key Authorization and the value Bearer and your MCP access key, then save.

The form's settings, as Devin's reference writes them:

Add custom MCPJSON
{
"transport": "HTTP",
"url": "https://mcp.cilo.com",
"auth_method": "auth_header",
"headers": {
"Authorization": "Bearer <your MCP access key>"
}
}

Step 3: Check the connection

On the server's page, choose Test tools: Devin connects and lists cilo's tools. If it fails, the message names the cause: the address, the credentials, or a timeout.

Ask for Cilo’s block families and confirm a tool call succeeds. A visible server or tool list alone does not confirm access.

Step 4: Ask for a block

Ask Devin for a block by what it does, and name cilo, so it uses https://mcp.cilo.com rather than another source:

  • “Using cilo, add an order tracking card with the courier on a map to the order page.”

It finds the block with components_list, gets one install command from component_install, and runs it in your project once you agree. More asks are on MCP server.

Good to know

  • Devin installs with the shadcn CLI on its own machine, which has no .env.local since git leaves it out. Give Devin CILO_TOKEN as a secret too, so its add commands reach @cilo-pro.
  • Adding a custom server takes the Manage MCP Servers permission, which organisation admins have; others can suggest one.
  • On your own machine, Devin Desktop and the Devin CLI read .devin/mcp_config.json, .devin/mcp_config.local.json and ~/.config/devin/mcp_config.json instead; the Windsurf page shows how to add cilo there.

Devin's guide to MCP(opens in a new tab)