Codex

Codex keeps its MCP servers in config.toml, in your home folder for every project or in a project's own .codex folder, and its terminal app, IDE extension and desktop app share them.

Set up

Step 1: Add the registry

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

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 with Codex's own command. It goes into ~/.codex/config.toml, which stores the variable's name, never the key:

Terminal
codex mcp add cilo --url https://mcp.cilo.com --bearer-token-env-var CILO_MCP_TOKEN

Or add it by hand, there or in the project's .codex/config.toml, which Codex reads once you trust the project:

~/.codex/config.tomlTOML
[mcp_servers.cilo]
url = "https://mcp.cilo.com"
bearer_token_env_var = "CILO_MCP_TOKEN"

Step 3: Check the connection

List the servers; cilo is in the HTTP table, with its URL and CILO_MCP_TOKEN as its bearer variable:

Terminal
codex mcp list

In the terminal app or the desktop composer, /mcp shows the active servers.

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 Codex 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.
  • Codex has no --header flag and no ${…} in its config: bearer_token_env_var is how it sends the key.
  • Codex waits 10 seconds for a server to start and 60 for a tool call. Raise them with startup_timeout_sec and tool_timeout_sec under [mcp_servers.cilo] if you need to.

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