Kiro
Kiro reads a workspace's MCP servers from .kiro/settings/mcp.json, and the ones you want everywhere from ~/.kiro/settings/mcp.json.
Set up
Step 1: Add the registry
Kiro 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 Kiro
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 the workspace's file from the command palette, with Kiro: Open workspace MCP config (JSON), and add cilo:
{"mcpServers": {"cilo": {"url": "https://mcp.cilo.com","headers": {"Authorization": "Bearer ${CILO_MCP_TOKEN}"}}}}
Kiro fills ${CILO_MCP_TOKEN} only for variables you approve: open Settings, search for Mcp Approved Env Vars and add CILO_MCP_TOKEN. It picks the change up when you save.
Step 3: Check the connection
Open the Kiro panel and its MCP servers view: cilo shows as connected, with its tools. If the view is empty, turn on MCP support in Kiro's settings.
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 Kiro 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
- 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.
- Kiro's terminal app loads a workspace's servers only once you trust the folder. How it approves environment variables is not documented; check your version's docs.