Catalog My learning Blog
Search courses and lessons
Cheat sheet

MCP Config File Locations

Where every major AI tool keeps its MCP servers, what the file looks like and how it reads secrets. Bookmark it for the next time a README only shows the config for some other tool.

By Naveed Karimi · Checked November 7, 2026 · Print-friendly

Files and top-level keys

ToolProject fileUser fileTop-level keyGuide
Claude Code.mcp.json~/.claude.json (local and user scope)mcpServersDay 15
Cursor.cursor/mcp.json~/.cursor/mcp.jsonmcpServersCursor guide
VS Code.vscode/mcp.jsonMCP: Open User ConfigurationserversDay 15
Codex CLInone~/.codex/config.toml (TOML)[mcp_servers.<name>]Codex guide
Gemini CLI.gemini/settings.json (trusted folders only)~/.gemini/settings.jsonmcpServersGemini guide
Claude Desktopnoneclaude_desktop_config.json (macOS: ~/Library/Application Support/Claude/)mcpServersDay 15
JetBrains AI AssistantServer level: projectServer level: global (set in Settings, Tools, AI Assistant, MCP)mcpServers (pasted JSON)JetBrains guide
ZednoneZed settings.jsoncontext_serversZed guide

Secrets: environment variable syntax

Never paste a token into a file you commit. Each tool has its own way to read one from the environment:

ToolSyntaxExample
Claude Code .mcp.json${VAR}, ${VAR:-default}"Authorization": "Bearer ${GITHUB_PAT}"
Cursor${env:VAR}, plus ${workspaceFolder}, ${userHome}"Bearer ${env:GITHUB_PAT}"
VS Code${input:id} with an inputs entry (prompted once, stored securely)"Bearer ${input:github_pat}"
Gemini CLI$VAR, ${VAR}, ${VAR:-default}-H 'Authorization: Bearer $GITHUB_PAT'
Codex CLIbearer_token_env_var for remote servers, env table for local onesbearer_token_env_var = "GITHUB_PAT"
Claude Desktop, JetBrains, ZedNo documented interpolation: values are literalKeep the file private, prefer OAuth

An unset variable is often passed through as literal text, so a server receives $GITHUB_PAT as the token and answers 401. Export the variable, then restart the tool.

Add a server, then check it

ToolAdd a local serverAdd a remote serverCheck
Claude Codeclaude mcp add <name> -- npx -y <pkg>claude mcp add --transport http <name> <url>claude mcp list, /mcp
Codex CLIcodex mcp add <name> -- npx -y <pkg>codex mcp add <name> --url <url>codex mcp list
Gemini CLIgemini mcp add -s user <name> npx -y <pkg>gemini mcp add -s user -t http <name> <url>gemini mcp list, /mcp
CursorEdit mcp.jsonEdit mcp.jsonCustomize panel, Output: MCP Logs
VS CodeMCP: Add ServerMCP: Add Server, then HTTPMCP: List Servers
ZedSettings, AI, MCP Servers, Add ServerSame, Add Remote ServerGreen dot: "Server is active"

Scopes: Claude Code --scope local|project|user (default local), Gemini CLI -s user|project (default project). OAuth sign-in: /mcp or claude mcp login <name> in Claude Code, codex mcp login <name> in Codex.

Entry shapes side by side

JSON (Claude Code, Cursor, Claude Desktop, Gemini CLI, JetBrains)

JSON
{
  "mcpServers": {
    "playwright": { "command": "npx", "args": ["-y", "@playwright/mcp@0.0.84"] },
    "sentry": { "url": "https://mcp.sentry.dev/mcp" }
  }
}

Claude Code's .mcp.json and Gemini CLI add "type": "http" to remote entries.

VS Code

JSON
{
  "servers": {
    "playwright": { "type": "stdio", "command": "npx", "args": ["-y", "@playwright/mcp@0.0.84"] },
    "sentry": { "type": "http", "url": "https://mcp.sentry.dev/mcp" }
  }
}

Zed

JSON
{
  "context_servers": {
    "playwright": { "command": "npx", "args": ["-y", "@playwright/mcp@0.0.84"], "env": {} },
    "sentry": { "url": "https://mcp.sentry.dev/mcp" }
  }
}

Codex CLI (~/.codex/config.toml)

TOML
[mcp_servers.playwright]
command = "npx"
args = ["-y", "@playwright/mcp@0.0.84"]

[mcp_servers.sentry]
url = "https://mcp.sentry.dev/mcp"

Don't want to convert by hand? The MCP config generator writes these for you.