●  MCP tools · validators · runs 100% in your browser
EST. 20241 makerBuilt in public
MCP tools · Validator · Claude Desktop

claude_desktop_config, checked.

Paste your claude_desktop_config.json, hit Validate, fix the red rows before you restart Claude Desktop. Runs 100% in your browser — nothing is uploaded, nothing logged.

§ 01

Paste & validate

claude_desktop_config.json
Waiting for input.
    § 02

    What this checks

    7 checks
    1. JSON syntax — the file must parse. A trailing comma or a JavaScript comment is the usual culprit.
    2. Top-level mcpServers object — the root must be an object with an mcpServers key holding an object of servers.
    3. At least one server — an empty mcpServers object means nothing will start.
    4. Per-server command — every server needs a non-empty command string (e.g. npx, uvx, node, python).
    5. Per-server args — args must be an array of strings when present; a missing args raises a warning since most servers need launch arguments.
    6. env object — env must be an object of string values when present. On Windows, an ENOENT referencing ${APPDATA} often means you need an expanded APPDATA entry in env.
    7. Absolute paths — directory arguments must be absolute, not relative (./data will not resolve). Relative-looking paths raise a warning.
    8. Universal screens on every validator: possible secret values pasted in env (heuristic warning — prefer input variables or an env file) and insecure http:// URLs in any URL field.
    Checks grounded in the official guide: modelcontextprotocol.io/docs/develop/connect-local-servers (config shape, absolute-path troubleshooting, env/APPDATA note, log locations). Common failure notes: restart Claude Desktop after saving · macOS config at ~/Library/Application Support/Claude/claude_desktop_config.json, Windows at %APPDATA%\Claude\claude_desktop_config.json · logs at ~/Library/Logs/Claude/mcp*.log.
    § 03

    Sibling validators