Catalog My learning Blog
Search courses and lessons
Free tool

MCP Config Generator

Pick your AI tool and the MCP servers you want. Get the exact command or config file, with secrets kept in environment variables wherever your tool supports it.

Servers

How it works

Every MCP client needs the same three facts about a server: a name, a transport (a local program over stdio, or a remote server over HTTP) and either the command to start it or the URL to reach it. What changes from tool to tool is the file format and how secrets are written. The generator applies the rules for each tool, and every format was checked in November 2026 by running Codex CLI 0.167 and Gemini CLI 0.67 or against each tool’s documentation.

  • Versions are pinned, for example @playwright/mcp@0.0.84, so a server only updates when you choose to.
  • Tokens go in environment variables: ${VAR} for Claude Code, ${env:VAR} for Cursor, ${input:name} for VS Code, $VAR for Gemini CLI and bearer_token_env_var for Codex.
  • Servers that support OAuth (Supabase, Sentry, Figma) get no token at all. You sign in in the browser the first time.
  • Safe defaults are on: GitHub read-only, Supabase read-only, Chrome DevTools with an isolated profile.

Each server has a full guide in MCP Setup Guides, and if a server won’t connect, start with the troubleshooting guide.

Questions

Where does each AI tool store its MCP config?

Claude Code uses .mcp.json (project) or ~/.claude.json, Cursor uses .cursor/mcp.json or ~/.cursor/mcp.json, VS Code uses .vscode/mcp.json, Codex CLI uses ~/.codex/config.toml, Gemini CLI uses ~/.gemini/settings.json and Zed uses context_servers in its settings.json. The MCP config file locations cheat sheet has the full table.

Why does the same server need different config in each tool?

Every tool needs the same facts: a name, a transport, and a command or URL. They differ in file format (JSON or TOML), the top-level key (mcpServers, servers or context_servers) and how they read secrets from environment variables.

Is it safe to commit these files?

Yes, when the output uses an environment variable reference such as ${VAR}, ${env:VAR} or ${input:name}. Outputs that contain a YOUR_... placeholder need the real value pasted in, so keep those files out of version control.

Does this tool send my settings anywhere?

No. The generator runs entirely in your browser. Nothing you type, including project refs or slugs, leaves the page.