MCP Config Auditor & Merger

Audit your MCP client JSON configs for syntax errors, missing API key placeholders, and argument errors. Merge new servers from the AllMCPs directory directly into your config with 1 click.

  • Free
  • No sign-in
  • Runs in your browser

1 Paste your config

claude_desktop_config.json · .cursor/mcp.json · …
Valid JSON
Merge a server from the directory
Popular:

2 Audit report

Claude DesktopDetected format
2Servers
0Errors
1Warnings
  • Environment variable "GITHUB_PERSONAL_ACCESS_TOKEN" in server "github" contains unreplaced placeholder: "<YOUR_GITHUB_TOKEN>".

    Replace "<YOUR_GITHUB_TOKEN>" with your actual GITHUB_PERSONAL_ACCESS_TOKEN secret before running.

What the Config Auditor checks

Paste a Claude Desktop, Cursor, Windsurf, Cline, VS Code or Zed MCP config and the auditor parses it, detects which client format it is, and checks every server entry: that it has a command or url, that args is an array, and that no argument or environment variable still contains template text such as <YOUR_API_KEY> copied from a README.

The merge panel adds a server from the directory to your existing config without retyping it, so you can build up a working config file in one place and paste it back into your client. For step-by-step setup in each client, see the MCP client setup guides.

Frequently asked questions

The most common causes are a JSON syntax error, a server entry missing its command, args written as a string instead of an array, or a placeholder API key that was never replaced. The auditor flags each of these. Most clients also only reload MCP servers after a full restart.

It reads the mcpServers format used by Claude Desktop, Cursor, Windsurf, Cline and most other clients, the servers key used by VS Code, and the context_servers key used by Zed.

Paste your existing config, then use the merge panel to add servers from the directory. Each server is added under its own key, so existing entries are kept. Review the result for duplicate server names before saving.

No. Auditing and merging run entirely in your browser, so API keys and file paths in the config never leave your device.