Free tool · MCP config · updated Oct 27, 2026

Convert MCP servers from VS Code to Codex

Got MCP servers working in VS 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

VS Code: .vscode/mcp.json in the workspace
Codex: ~/.codex/config.toml (or .codex/config.toml in a trusted project)

Before and after

VS Code

{
  "servers": {
    "context7": {
      "type": "stdio",
      "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

Drop the type field and turn each entry under servers into a [mcp_servers.NAME] TOML table. VS Code's ${env:NAME} and ${input:...} variables don't carry over, so put the real env var names in Codex's env or env_vars.

Open the converter set to Codex → Paste your VS 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 → Codex · Cursor → Codex · VS Code → Claude Desktop · VS Code → Claude Code · VS Code → Cursor

Questions people ask

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

Paste the VS 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