Kilo Code
Kilo Code runs in VS Code and in a terminal app, and keeps its MCP servers in its own config, kilo.json, in the project or in your home folder.
Set up
Step 1: Add the registry
Kilo 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 Kilo 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.
Add cilo to the project's config. Kilo fills {env:…} from its environment, so the file holds no key:
{"$schema": "https://app.kilo.ai/config.json","mcp": {"cilo": {"type": "remote","url": "https://mcp.cilo.com","headers": {"Authorization": "Bearer {env:CILO_MCP_TOKEN}"},"oauth": false,"enabled": true}}}
Use your own global Kilo config for a key you do not want in project files. Kilo’s Settings, MCP page can add the same remote URL and header.
Step 3: Check the connection
In Kilo's settings, Agent Behaviour, MCP Servers lists cilo with no error. From a terminal:
kilo mcp listkilo mcp debug cilo
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 Kilo 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
- Keep "oauth": false: with a Bearer key there is no sign-in, and without it Kilo may start one on a refused call.
- Your agent reads CILO_MCP_TOKEN from the environment it was started in, not from .env.local, which holds the project’s pro-install credential. Export it in your shell profile (export CILO_MCP_TOKEN=…) and start the agent from a new terminal.
- Older Kilo pages show mcp_settings.json with streamable-http; that is the format from before the rebuild. Use kilo.json.