# MCP config generator: Claude Code, Codex, Cursor

> Describe your MCP server once and copy the exact config for Claude Code (claude mcp add or .mcp.json), Codex (config.toml), Cursor, VS Code and Claude Desktop. Free, runs in your browser, checked against each client's docs.

Canonical: https://dejo.run/tools/mcp-config-generator

> For AI agents: the index of this site is https://dejo.run/llms.txt, and every page is also served as markdown (add .md to its address, or send Accept: text/markdown).

**The short answer:** describe your MCP server once (its name, the command that starts it, its arguments and any environment variables) and copy the exact config for each AI client. Every format below was checked against the client's own documentation on 10 November 2026.


It runs in your browser; nothing you type is sent anywhere. It covers local servers, the kind started with a command (stdio). It starts with [Dejo](https://dejo.run/), a browser MCP that remembers websites, filled in; press "Any server" to start from scratch.

## Where each client keeps its MCP config

| Client | How to add a server | Top-level key |
|---|---|---|
| Claude Code | `claude mcp add` in a terminal, or `.mcp.json` in the project | `mcpServers` |
| Codex | `codex mcp add`, or `~/.codex/config.toml` | `[mcp_servers.NAME]` table |
| Cursor | `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (one project) | `mcpServers` |
| VS Code | `.vscode/mcp.json` in the workspace | `servers` |
| Claude Desktop | `claude_desktop_config.json` | `mcpServers` |

## Claude Code

The command is the simplest way. Everything after `--` is the command that starts the server, passed through untouched. Environment variables go before the server's name with `--env KEY=value`, and another option must sit between `--env` and the name, which is why the generator puts `--transport stdio` there.

`--scope` decides where the server is saved: `user` for every project, `project` for a `.mcp.json` file the whole team shares, and `local`, the default, for you in this project only.

## Codex

Codex reads `~/.codex/config.toml`, or a `.codex/config.toml` inside a trusted project. Each server is its own table, `[mcp_servers.NAME]`, with `command` and an optional `args` list. Environment variables go in a separate `[mcp_servers.NAME.env]` table. Codex waits 10 seconds for a server to start unless you set `startup_timeout_sec`.

## Cursor

Cursor reads `~/.cursor/mcp.json` for servers you want everywhere and `.cursor/mcp.json` for one project. Its documentation lists `type` as required, so the generator includes `"type": "stdio"`.

## VS Code

VS Code reads `.vscode/mcp.json` in the workspace, or a `mcp.json` in your user profile. It is the one client here whose top-level key is `servers`, not `mcpServers`. A config copied from another client fails until that key is renamed.

## Claude Desktop

Claude Desktop reads `claude_desktop_config.json`:

- macOS: `~/Library/Application Support/Claude/claude_desktop_config.json`
- Windows: `%APPDATA%\Claude\claude_desktop_config.json`
- Linux: `~/.config/Claude/claude_desktop_config.json`

Quit Claude Desktop completely and open it again after you save, so it loads the new server.

## Sources

- Claude Code: [code.claude.com/docs/en/mcp](https://code.claude.com/docs/en/mcp)
- Codex: [learn.chatgpt.com/docs/extend/mcp](https://learn.chatgpt.com/docs/extend/mcp?surface=cli)
- Cursor: [cursor.com/docs/context/mcp](https://cursor.com/docs/context/mcp)
- VS Code: [code.visualstudio.com, MCP configuration](https://code.visualstudio.com/docs/agents/reference/mcp-configuration)
- Claude Desktop: [modelcontextprotocol.io, connect local servers](https://modelcontextprotocol.io/docs/develop/connect-local-servers)

## FAQ

## FAQ

### Where is the Claude Code MCP config file?

Claude Code stores servers you add with `claude mcp add` for you. A server added with `--scope project` goes into `.mcp.json` in the project root, under a top-level `mcpServers` key, so the whole team gets it. `--scope user` makes it available in every project, and `local` (the default) keeps it to you in this project.

### How do I add an MCP server to Codex?

Either run `codex mcp add NAME -- COMMAND ARGS`, or add a `[mcp_servers.NAME]` table to `~/.codex/config.toml` with `command` and `args`, and environment variables in a `[mcp_servers.NAME.env]` table.

### Why does my VS Code MCP config not work when I copy it from Cursor?

VS Code uses a top-level `servers` key, while Cursor, Claude Code and Claude Desktop use `mcpServers`. Each VS Code entry also says `"type": "stdio"` for a local server.

### Is anything I type sent anywhere?

No. The generator runs entirely in your browser. Nothing you type, including API keys in environment variables, leaves the page.

## Related

- [Dejo: browser automation MCP that remembers websites](https://dejo.run/)
- [Dejo MCP server setup: install in a minute](https://dejo.run/docs)
