⩜
MCP Config Validator
Paste an MCP config and check it against each client's own conventions: top-level key, mandatory type, remote field name, plaintext URLs, suspected real credentials. One config is checked against four clients, and problems that only affect some of them are called out separately.
Runs in browserAI configTroubleshooting
Loading tool…
How to use
- Paste or drop an MCP config file and see, item by item, whether each client will actually accept it. Everything runs in your browser; the config never leaves this page.
- This tool reads the generator's spec table and keeps no second copy of field names or top-level keys. Two tables drift apart, and the symptom is “the generator says it is valid, the validator says it is not” with no way to tell which one to believe.
- It validates against our spec table, not an official JSON Schema — all five clients allow extension fields and no single schema covers them. That is why every rule is labelled by basis: written in the spec, or observed in the wild. Mixing the two lets people mistake “everyone writes it this way” for “it must be written this way”.
- The same mcpServers block is checked against four clients. Working in Cursor and failing silently in Claude Desktop is the most common way this config breaks; problems that affect only some clients name the ones affected instead of failing outright.
- Duplicate keys get their own pass, because JSON.parse keeps the last occurrence, drops the rest, and reports nothing. Such a config opens looking fine and only turns out wrong when you edit a value that was not the one you wrote.
- “Suspected real credential” is a shape check, not a lookup. It will produce false positives and will miss custom token formats — one warning is enough; do not treat it as a security scanner.