GitHub Copilot

GitHub Copilot in VS Code reads MCP servers from the workspace’s .vscode/mcp.json.

Set up

Step 1: Add the registry

GitHub Copilot 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 GitHub Copilot

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.

Add cilo to the workspace's .vscode/mcp.json. VS Code asks for the key once and keeps it, so the file holds no key:

.vscode/mcp.jsonJSON
{
"inputs": [
{
"type": "promptString",
"id": "cilo-token",
"description": "Cilo MCP access key",
"password": true
}
],
"servers": {
"cilo": {
"type": "http",
"url": "https://mcp.cilo.com",
"headers": {
"Authorization": "Bearer ${input:cilo-token}"
}
}
}
}

Step 3: Check the connection

In VS Code, run MCP: List Servers from the command palette: cilo is listed, with Start, Stop, Restart and Show Output. Ask for a block and open the tool call to see cilo answer.

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 GitHub Copilot 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

  • VS Code starts servers from workspace files only once you trust the workspace.
  • These instructions configure Copilot in VS Code; other Copilot clients have their own MCP setup.

VS Code's MCP configuration reference(opens in a new tab)