OpenCode

OpenCode runs in your terminal and reads its MCP servers from opencode.json at the project's root, or ~/.config/opencode/opencode.json for every project.

Set up

Step 1: Add the registry

OpenCode 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.

components.jsonJSON
{
"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}"
}
}
}
}
.env.local
CILO_TOKEN=your-licence-key

Step 2: Connect OpenCode

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 opencode.json. OpenCode fills {env:…} from its environment, so the file holds no key:

opencode.jsonJSON
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"cilo": {
"type": "remote",
"url": "https://mcp.cilo.com",
"oauth": false,
"headers": {
"Authorization": "Bearer {env:CILO_MCP_TOKEN}"
},
"enabled": true
}
}
}

opencode mcp add walks you through a remote server too, but asks for no header; add it to the file afterwards.

Step 3: Check the connection

List the servers OpenCode can reach; cilo shows as connected:

Terminal
opencode mcp list

If it does not, opencode mcp debug cilo tests the connection.

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 OpenCode 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: without it OpenCode may start its own sign-in when a call is refused.
  • An unset CILO_MCP_TOKEN becomes an empty string and the server refuses the call: export it before you start opencode, or read the key from a file with {file:~/.config/cilo/token}.

OpenCode's guide to MCP servers(opens in a new tab)