Where does Codex CLI read its config from?

Codex CLI reads MCP config from config.toml. Top-level JSON key: `mcp_servers`. Format: TOML.

Is my config sent to your server during conversion?

No. Conversion runs entirely in your browser as JavaScript. Your config — and any API keys it contains — never leaves your machine.

Back to converter (any format)

Convert Cursor mcp.json to Codex CLI config.toml

Q: How do I convert Cursor config to Codex CLI?

Paste your mcp.json into the converter. Cursor's JSON `mcpServers` becomes Codex's TOML `[mcp_servers. ]` tables. The conversion is mechanical for the common shape (command, args, env, url, headers); Cursor-specific fields like `envFile` and `auth` get warnings.

Convert your Cursor mcp.json (JSON) to OpenAI Codex CLI config.toml ([mcp_servers.x] tables). Handles env, headers, and the JSON→TOML structural shift.

Your config never leaves your browser.

From

Paste your mcp.json

Runs in your browser. Nothing uploaded.

0 chars

Paste your mcp.json to convert it to config.toml, or click to see how it works.

What's actually different

Cursor's JSON `mcpServers` becomes Codex's TOML `[mcp_servers.<id>]` tables. The conversion is mechanical for the common shape (command, args, env, url, headers); Cursor-specific fields like `envFile` and `auth` get warnings.

Conversion gotchas

•Each Cursor server entry becomes a `[mcp_servers.<name>]` table in TOML.
•Cursor's `type: "stdio"` is dropped — Codex CLI infers transport from `command` vs `url`.
•`env` and `headers` JSON objects become TOML inline tables.
•Cursor `envFile` and `auth` blocks have no Codex equivalent and are flagged.

Other conversions

Convert Claude Desktop config to Cursor mcp.json

Convert Claude Desktop JSON to Codex CLI config.toml

Convert Claude Desktop config to VS Code .vscode/mcp.json

Convert Cursor mcp.json to Claude Desktop config

Validate after converting

Paste the converted output into our Codex CLI validator to confirm it'll load.

Codex CLI validator →All conversions