MCP config checker
Find the configuration mistake before you restart your client.
Checks JSON syntax, duplicate keys and common server fields. Does not connect to servers, run commands or validate credentials.
Ready to check
Your results will appear here.
Configuration checks are a first step.
A valid structure does not prove a working connection.
What to do with the result
Changes needed: fix the reported line in a backup copy, then check again. Duplicate members can silently replace an earlier server definition. A string such as "server.js" must be inside the args array, not used as the array itself.
Review recommended: the JSON parses, but a transport or field needs confirmation against your client's documentation. The checker deliberately leaves uncommon client extensions for manual review.
Structure checks passed: save the file in the correct client location, restart the client, and inspect its real MCP connection status. This result cannot check executable paths, permissions, network reachability, authentication, model compatibility, or installed analysis engines.
Working with REA? Continue to REA setup or interpret REA doctor output. For authoritative field definitions, read the Claude Code MCP documentation and Cursor MCP documentation.
Can I check a real configuration?
Yes, but use a sanitized copy. This page has no advertising iframe. Site analytics records only the selected client and the result category. Use privacy controls to disable analytics. Do not paste private configuration into a shared screen or shared computer.
Will this repair or install a server?
No. It produces explanations without rewriting your input, contacting a server or running a command. You stay in control of the actual configuration file.