Junie

Junie, JetBrains' coding agent, runs in their IDEs and in a terminal app, and reads MCP servers from .junie/mcp/mcp.json in a project, or ~/.junie/mcp/mcp.json for every project.

Set up

Step 1: Add the registry

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

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.

Junie documents no way to read the key from the environment, so put cilo in your own file, which stays out of every repository:

~/.junie/mcp/mcp.jsonJSON
{
"mcpServers": {
"cilo": {
"url": "https://mcp.cilo.com",
"headers": {
"Authorization": "Bearer <your MCP access key>"
}
}
}
}

From the IDE: open Settings, then Tools, Junie, MCP Settings, choose Add, and paste the same entry into the file it opens.

Step 3: Check the connection

In MCP Settings, cilo shows as active, with its tools. In Junie's terminal app, /mcp shows the same.

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 Junie 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 the key out of the project's .junie/mcp/mcp.json, which is meant to be committed.
  • Junie waits 60 seconds for a remote call by default; a timeout field in milliseconds changes it.

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