Free tool · MCP config · updated Oct 27, 2026

Convert MCP servers from Codex to Cursor

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

Where each file lives

Codex: ~/.codex/config.toml (or .codex/config.toml in a trusted project)
Cursor: .cursor/mcp.json in the project, or ~/.cursor/mcp.json

Before and after

Codex

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

Cursor

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

What changes

Each [mcp_servers.NAME] table becomes a key under mcpServers. Inline tables like env = {...} become plain JSON objects. Codex-only fields such as startup_timeout_sec or bearer_token_env_var have no direct match, so you'll have to handle them yourself.

Open the converter set to Cursor → Paste your Codex 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

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

Questions people ask

How do I convert an MCP config from Codex to Cursor?

Paste the Codex config into PickAPlugin's free MCP config converter with the target set to Cursor, then save the result to .cursor/mcp.json in the project, or ~/.cursor/mcp.json.

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