Windsurf
Windsurf is now Devin Desktop. Its default agent, Devin Local, reads MCP servers from the project's .devin folder and from ~/.config/devin/mcp_config.json; Cascade, the agent Windsurf shipped with, reads only that one file for every project.
Set up
Step 1: Add the registry
Windsurf installs with the shadcn CLI in your project. Name cilo's two registries in components.json, give both an Authorization header with your account's API key, and keep the key in .env.local. Free items and catalog searches require a key too. Skip this if Installation already had you do it.
{"registries": {"@cilo": {"url": "https://dev-api.cilo.sh/r/styles/{style}/{name}.json","headers": {"Authorization": "Bearer ${CILO_TOKEN}"}},"@cilo-pro": {"url": "https://dev-api.cilo.sh/r/styles/{style}/{name}.json?tier=pro","headers": {"Authorization": "Bearer ${CILO_TOKEN}"}}}}
CILO_TOKEN=your-api-key
Step 2: Connect Windsurf
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 registry requests, including free installs; do not assume the two keys are interchangeable.
Add cilo with the Devin CLI. It writes .devin/mcp_config.local.json, which git ignores; the CLI has no header flag, so add the header to that file:
devin mcp add cilo https://mcp.cilo.com
{"mcpServers": {"cilo": {"url": "https://mcp.cilo.com","transport": "http","headers": {"Authorization": "Bearer <your MCP access key>"}}}}
Using the legacy Cascade agent? Its file, ~/.config/devin/mcp_config.json, fills ${env:…}, so the key can stay in your environment:
{"mcpServers": {"cilo": {"url": "https://mcp.cilo.com","headers": {"Authorization": "Bearer ${env:CILO_MCP_TOKEN}"}}}}
The Devin CLI and Devin Local read this same file (~/.config/devin/mcp_config.json); they do not document ${env:} in headers.
Step 3: Check the connection
From the Devin CLI:
devin mcp listdevin mcp get cilo
In Devin Desktop, Open customizations lists cilo among its MCP servers. In Cascade, the Actions menu's MCPs lists it with its tools and a switch.
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 Windsurf 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
- Give the address exactly as https://mcp.cilo.com: cilo answers at the root, not at /mcp.
- Always set the Authorization header; without it the CLI may offer a sign-in cilo does not use.
- Devin Local asks before each tool call until you allow it.