Validate your config

Tip: you can also drop a .json file onto the box. Nothing you paste is stored or sent anywhere.

Results

Paste a config to begin.

Configs often contain secrets

This page runs entirely in your browser, and its security policy blocks background network requests, so the tool has no way to send what you paste anywhere. Even so, treat API keys with care: any key that appears in a file you have shared or committed should be rotated, and found secrets are always masked in the results here.

What it checks

Checked

  • JSON syntax with the exact line: Windows backslashes, curly quotes, missing and trailing commas, comments, duplicate server names.
  • The right shape for your client: mcpServers or servers, command vs url, valid type.
  • Values that break startup: args that aren’t a string array, numbers in env, a whole command line in command, npx without -y.
  • Typos: arg, environment, header and other fields that are silently ignored.
  • Secrets: API keys, tokens, private keys and database passwords stored in plain text, in env, headers, args, the command or the URL.
  • Risky commands: scripts piped from the internet into a shell, sudo, and privileged Docker containers.
  • Variables: ${input:…}, ${env:…} and ${VAR} used in the right client.
  • Remote servers: invalid or insecure URLs and the wrong transport type.

Not checked

  • Whether a server works. We never start a command or connect to a URL, so we can’t tell if a package exists or a server is online.
  • Authentication. We can’t tell whether a token is valid.
  • Every client-specific option. Newer or unusual fields are shown as notes, not errors.
  • Server code. A valid config says nothing about whether a server is safe to run. We flag a few risky command patterns, but we can’t inspect what a package does. Only add servers you trust.

Questions, answered

Is my config sent anywhere?

No. Validation runs inside your browser tab. The page carries a security policy that blocks background network requests, and nothing you paste is saved. You can turn off your internet connection once the page has loaded and it will still work.

Where is my config file?

Claude Desktop: claude_desktop_config.json in its settings folder (Settings → Developer → Edit Config). Claude Code: .mcp.json in your project. VS Code: .vscode/mcp.json. Cursor: .cursor/mcp.json. Windsurf: mcp_config.json.

My config is valid but the server still won’t connect. Why?

The most common causes are things a validator can’t see: the command isn’t on the client’s PATH (apps launched from the dock often have a shorter PATH than your terminal), a missing runtime such as Node or uv, an expired token, or the client not being restarted after the edit. Check the client’s MCP logs for the real error.

Why does Auto-detect pick a format?

If your file has a top-level servers key it is treated as VS Code; mcpServers is used by Claude, Cursor and Windsurf. Choose a client from the list to get checks that are specific to it, such as which variable syntax it expands.

Can I use comments in my config?

Only in VS Code’s mcp.json. Claude Desktop, Claude Code and Cursor expect strict JSON, so a comment or trailing comma will stop the file loading. The validator flags this for those clients.

More free tools

See all free tools
  • Photos & videos
  • Use responsibly

Metadata Cleaner

Remove GPS location, device details, edit history, and AI generation details such as prompts and Content Credentials from JPEG, PNG, WebP, MP4, MOV, WebM and MKV files. No quality loss.

  • Developers
  • OpenAPI

API Contract Drift Analyzer

Compare two versions of an OpenAPI 3.0, 3.1 or 3.2 spec and see which changes break existing clients: removed operations, new required fields, type, enum, response and security changes, each explained.

Need MCP servers built for your business?

AICEA builds custom MCP servers, AI agents and integrations that connect your tools and data.

Talk to us