Cursor

Cursor reads a project's MCP servers from .cursor/mcp.json, and the ones you want everywhere from ~/.cursor/mcp.json.

Set up

Step 1: Add the registry

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

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 file. Cursor fills ${env:…} from its environment, so the file holds no key and can be committed:

.cursor/mcp.jsonJSON
{
"mcpServers": {
"cilo": {
"url": "https://mcp.cilo.com",
"headers": {
"Authorization": "Bearer ${env:CILO_MCP_TOKEN}"
}
}
}
}

Cursor has no command that adds a server; edit the file, or ~/.cursor/mcp.json for every project.

Step 3: Check the connection

Restart Cursor, open Customize in the sidebar and choose MCPs: cilo is listed with its tools. Switch it on there if it is off.

From the terminal, the Cursor CLI lists the same:

Terminal
agent mcp list
agent mcp list-tools 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 Cursor 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

  • Cursor reads no env file for a remote server, so CILO_MCP_TOKEN must be in Cursor's own environment. An editor opened from the Dock or the Start menu may not see variables exported in your shell profile. Open it from a terminal, or set CILO_MCP_TOKEN for the whole system. Starting it with cursor . does that.
  • If cilo shows an error, the Output panel's MCP Logs say why.

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