Add MCP servers to Codex CLI

Manage Codex CLI’s MCP servers from one canonical config with mcpfold — the free, open-source CLI. Write your servers once and fold them out to Codex CLI’s own mcp_servers config, with secrets kept as references, not hardcoded values.

Set up Codex CLI in 4 steps

Install mcpfold. Install the free, open-source mcpfold CLI — no account required.npm install -g mcpfold
Create your config. Create one canonical mcp.config.jsonc — the single source of truth mcpfold folds out to every client.mcpfold init
Add a server. Add an MCP server from the registry (secrets stay references, versions stay pinned), or run `mcpfold import` to pull in servers you already configured.mcpfold add <server> --from-registry
Fold it out to Codex CLI. Write your servers into Codex CLI's own config (/Users/you/.codex/config.toml) under its `mcp_servers` key.mcpfold sync

What mcpfold writes for Codex CLI

Config file

/Users/you/.codex/config.toml

Windows: C:\Users\you\.codex\config.toml

Config key

mcp_servers

Secrets

Secrets stay as `${env:…}` / `${op:…}` references; mcpfold's launcher resolves them at run time, so Codex CLI's config file never contains a raw token.

Remote servers

Codex CLI reaches http/sse remotes natively — mcpfold writes a native remote entry, no bridge needed.

After sync

Changes are picked up without restarting Codex CLI.

Looking for servers to add? Browse the MCP server directory — every entry adds in one mcpfold add. Or see the install options.

mcpfold is an independent, open-source project and is not affiliated with or endorsed by Codex CLI. Names are used only to describe compatibility.