Free tool · MCP config · updated Oct 27, 2026

Convert MCP servers from Claude Code to Codex

Got MCP servers working in Claude Code and want the same ones in Codex? The servers don't change, only the config wrapper does. Here's exactly what to change.

Where each file lives

Claude Code: .mcp.json in the project, or ~/.claude.json
Codex: ~/.codex/config.toml (or .codex/config.toml in a trusted project)

Before and after

Claude Code

{
  "mcpServers": {
    "context7": {
      "command": "npx",
      "args": ["-y", "@upstash/context7-mcp"],
      "env": {"API_KEY": "..."}
    }
  }
}

Codex

[mcp_servers.context7]
command = "npx"
args = ["-y", "@upstash/context7-mcp"]
env = { API_KEY = "..." }

What changes

JSON becomes TOML. Each entry under mcpServers turns into its own [mcp_servers.NAME] table, and env becomes an inline table. For remote servers, use url plus http_headers, or bearer_token_env_var so the token stays out of the file.

Open the converter set to Codex → Paste your Claude Code config, copy the result. It runs in your browser and nothing gets uploaded.

Double-check before you paste the result anywhere: if your config has tokens in it, they'll be in the output too.

Other conversions

Claude Desktop → Codex · Claude Code → VS Code · Cursor → Codex · VS Code → Codex

Questions people ask

How do I convert an MCP config from Claude Code to Codex?

Paste the Claude Code config into PickAPlugin's free MCP config converter with the target set to Codex, then save the result to ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Do I need to change the MCP server itself?

No. A local server runs the same command in every app. Only the config format around it changes.

All guides · Free tools · FAQ · Browse all 346 plugins