Amp

Amp runs in your terminal and your editor, and keeps its MCP servers in its settings, under amp.mcpServers.

Set up

Step 1: Add the registry

Amp 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 Amp

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 your own settings, ~/.config/amp/settings.json, so it is there in every project. Amp reads ${…} from the environment, so the key stays out of the file:

~/.config/amp/settings.jsonJSON
{
"amp.mcpServers": {
"cilo": {
"url": "https://mcp.cilo.com",
"headers": {
"Authorization": "Bearer ${CILO_MCP_TOKEN}"
}
}
}
}

Step 3: Check the connection

Open Amp’s MCP server settings and verify cilo is available. Ask it to list Cilo’s block families to confirm a tool call succeeds.

Approve the project’s server when Amp asks, then verify a tool call succeeds.

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 Amp 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.
  • Cilo uses a Bearer access key rather than OAuth sign-in.

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