MCP Config Builder & Validator
Describe your MCP servers once and get the exact config file for Claude Desktop, Claude Code, Cursor, VS Code, Windsurf or Zed. Paste an existing config to find out why a server won’t start.
Frequently Asked Questions
Why is my MCP server not showing up?
The most common causes are using the wrong top-level key (VS Code expects "servers"; Claude, Cursor and Windsurf expect "mcpServers"; Zed uses "context_servers"), putting a whole command line in "command" instead of splitting it into "args", forgetting -y on npx so it waits for a prompt, and on Windows needing "cmd /c npx". The Validate tab checks for all of these.
Where is claude_desktop_config.json?
On macOS: ~/Library/Application Support/Claude/claude_desktop_config.json. On Windows: %APPDATA%\Claude\claude_desktop_config.json. Restart Claude Desktop after editing it.
How do I add a remote MCP server to Claude Desktop?
Remote servers are added in Claude Desktop under Settings → Connectors rather than in the config file. If you need it in the file, the builder can wrap the URL with the mcp-remote bridge.
Should I put API keys in my MCP config?
Avoid committing them. Claude Code supports ${VAR} expansion in .mcp.json, VS Code can prompt for secrets with input variables, and Windsurf supports ${env:VAR}. The builder flags values that look like secrets.
Does this send my config anywhere?
No. Building, validating and converting all happen in your browser.