Roo Code
Roo Code runs in VS Code and reads a project's MCP servers from .roo/mcp.json, and the ones for every project from its global mcp_settings.json.
Set up
Step 1: Add the registry
Roo Code 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.
{"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}"}}}}
CILO_TOKEN=your-licence-key
Step 2: Connect Roo Code
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.
- Open Roo Code and choose the MCP icon at the top of its pane.
- At the foot of the view, choose Edit Project MCP, which opens .roo/mcp.json.
- Add cilo and save.
{"mcpServers": {"cilo": {"type": "streamable-http","url": "https://mcp.cilo.com","headers": {"Authorization": "Bearer ${env:CILO_MCP_TOKEN}"}}}}
Keep the transport type explicit and use the full server URL.
Step 3: Check the connection
cilo is listed in the same view, with its tools, a switch to turn it off and a button to restart it.
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 Roo Code 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
- Roo Code's makers shut the extension down on 15 May 2026, so it gets no more updates. Cline and Kilo Code, above, take the same server.
- Roo Code fills ${env:CILO_MCP_TOKEN} from VS Code's environment, and an unset one becomes empty, which the server refuses. An editor opened from the Dock or the Start menu may not see variables exported in your shell profile. Open it from a terminal, or set CILO_MCP_TOKEN for the whole system.