Cline
Cline runs in VS Code and keeps every MCP server in one settings file of its own, cline_mcp_settings.json, shared by all your projects.
Set up
Step 1: Add the registry
Cline 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 Cline
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 Cline and choose the MCP Servers icon in its toolbar.
- Open the Configure tab and choose Configure MCP Servers.
- Add cilo to the file Cline opens, and save.
{"mcpServers": {"cilo": {"type": "streamableHttp","url": "https://mcp.cilo.com","headers": {"Authorization": "Bearer ${env:CILO_MCP_TOKEN}"},"disabled": false,"autoApprove": []}}}
Set the type to streamableHttp: without it, Cline falls back to the older SSE transport.
Step 3: Check the connection
Back in MCP Servers, cilo is listed and switched on, with its tools. Ask Cline for a block to see it call one.
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 Cline 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
- The VS Code extension fills ${env:CILO_MCP_TOKEN} from VS Code's own environment. 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.
- Cilo tools return information and commands; running an install command is a separate action by your agent. Keep the approval settings that fit your project.