MCP config generator
Tick the MCP servers you want and get a working config for Claude Desktop, Cursor, VS Code or Claude Code.
Result
The result will appear here.Every MCP client stores the same information in a slightly different file, and the differences are where setups break: Claude Desktop and Cursor want an mcpServers object, VS Code wants servers with a type field and prompts for secrets, and Claude Code wants a claude mcp add command with the server's own flags after a double dash. Pick the servers — the reference ones from modelcontextprotocol/servers (filesystem, fetch, git, memory, sequential thinking, time) plus GitHub's official server, Microsoft's Playwright server and Upstash Context7 — choose your client, and copy a config whose commands and package names were checked against each project's README and the npm and PyPI registries.
How it works
- Each server is written as a local stdio process, the one transport all four clients accept in their config files; secrets are left as placeholders such as YOUR_GITHUB_PAT.
- For VS Code, tokens become promptString inputs with password set, so .vscode/mcp.json can be committed without the token in it.
- On Windows, npx-based servers are wrapped in cmd /c for the JSON clients, as the reference servers' README instructs; uvx and docker commands are left unchanged.
Where your data goes
Nowhere. This tool runs entirely in your browser: the text you paste is processed by the page and is never transmitted to a server or written to a log.
This tool is free and needs no account. Its results exist only in your open page and are not saved anywhere.
What it costs
This tool is free, with no sign-in and no points.
Common questions
- Where does the config file go?
- Claude Desktop reads ~/Library/Application Support/Claude/claude_desktop_config.json on macOS and %APPDATA%\Claude\claude_desktop_config.json on Windows, and needs a restart afterwards. Cursor reads .cursor/mcp.json in the project or ~/.cursor/mcp.json globally. VS Code reads .vscode/mcp.json. Claude Code has no file to edit here: run the commands in a terminal, then check them with claude mcp list.
- Why does the GitHub server use Docker instead of npx?
- The old @modelcontextprotocol/server-github package on npm is marked as no longer supported. GitHub now maintains github/github-mcp-server and ships it as the ghcr.io/github/github-mcp-server image, which reads a personal access token from GITHUB_PERSONAL_ACCESS_TOKEN. Give that token only the repository scopes you are comfortable handing to an AI agent.
- What do I need installed for these commands to work?
- npx needs Node.js, uvx needs uv from Astral (fetch, git and time are Python servers published on PyPI), and the GitHub server needs Docker running. The tool lists which of the three your selection requires. The filesystem server also needs at least one allowed directory, either as the path argument written here or through a client that supports MCP roots.
The open-source behind it
This tool is a self-contained implementation. modelcontextprotocol/servers (Apache-2.0 / MIT) does the same job as a library — if you need this behaviour inside your own program, start there rather than calling a web page.
modelcontextprotocol/serversAlso known as
- mcp config generator
- claude_desktop_config.json
- cursor mcp.json
- vscode mcp.json
- claude mcp add
- mcp server setup