Free tool · MCP config · updated Oct 27, 2026

Convert MCP servers from Codex to VS Code

Got MCP servers working in Codex and want the same ones in VS Code? 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)
VS Code: .vscode/mcp.json in the workspace

Before and after

Codex

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

VS Code

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

What changes

Tables go under servers, and VS Code wants a type on each one (stdio for a command, http for a URL).

Open the converter set to VS Code → 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

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

Questions people ask

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

Paste the Codex config into PickAPlugin's free MCP config converter with the target set to VS Code, then save the result to .vscode/mcp.json in the workspace.

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