MCP Config Doctor
Already running MCP servers? Paste your mcpServers config and get an instant health check — combined tool count vs Cursor's limit, security notes, stale servers, and better alternatives. Nothing leaves your browser.
FAQ
What does the Config Doctor check?
It parses your mcpServers config, matches each server against this directory, and reports the combined tool count (vs Cursor's ~40-tool ceiling), which servers carry security notes, which look stale (no commits in 6+ months), and which have better-maintained alternatives.
Is my config sent anywhere?
No. The analysis runs entirely in your browser — nothing you paste leaves your machine. There's no upload and no server call.
Why does the total tool count matter?
Cursor works best under roughly 40 active MCP tools. Stack several servers and you can blow past that, which degrades tool selection. The Doctor sums the real tool counts so you can see it before it bites.
How does it know a server is stale or risky?
Every server in the directory carries a last-commit date and crawled security notes. The Doctor surfaces those for the servers it recognizes, and links to alternatives for stale or unverified ones.
Starting fresh instead? Use the config generator or browse servers by capability.