Zed

Zed's agent reads MCP servers, which Zed calls context servers, from your settings: your own for every project, or .zed/settings.json in a project.

Set up

Step 1: Add the registry

Zed installs with the shadcn CLI in your project. Name cilo's two registries in components.json, give both an Authorization header with your account's API key, and keep the key in .env.local. Free items and catalog searches require a key too. Skip this if Installation already had you do it.

components.jsonJSON
{
"registries": {
"@cilo": {
"url": "https://dev-api.cilo.sh/r/styles/{style}/{name}.json",
"headers": {
"Authorization": "Bearer ${CILO_TOKEN}"
}
},
"@cilo-pro": {
"url": "https://dev-api.cilo.sh/r/styles/{style}/{name}.json?tier=pro",
"headers": {
"Authorization": "Bearer ${CILO_TOKEN}"
}
}
}
}
.env.local
CILO_TOKEN=your-api-key

Step 2: Connect Zed

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 registry requests, including free installs; do not assume the two keys are interchangeable.

Zed fills in no environment variables in a header, so put cilo in your own settings, which stay out of every repository:

~/.config/zed/settings.jsonJSON
{
"context_servers": {
"cilo": {
"url": "https://mcp.cilo.com",
"headers": {
"Authorization": "Bearer <your MCP access key>"
}
}
}
}

Or from Zed's settings: choose AI, then MCP Servers, then Add Server and Add Remote Server.

Step 3: Check the connection

On the same MCP Servers page, cilo has a green dot, and its tooltip reads Server is active.

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

  • Always set the Authorization header: without it Zed starts a sign-in that cilo does not answer.
  • The agent runs the add command with its terminal tool, so keep that tool on in the profile you use.

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