MCP Doctor
diagnose why your MCP servers won't connect — in one command
npx mcp-doctorThanks for going Pro 🎉 Your license key is on its way by email. Paste it with
export MCP_DOCTOR_LICENSE=<key> and run mcp-doctor --remote.Ever run into this?
Adding an MCP server to Claude, Cursor, or Windsurf is a coin flip. When it fails you get a silent 'failed to connect' with zero detail — wrong command, missing env var, bad path, or a server that crashes on boot. You burn 30 minutes guessing.
The fix
mcp-doctor reads your MCP config, actually spawns each server, runs the real initialize handshake, and tells you exactly which one broke and why — in plain English.
What it does — free
- Auto-detects Claude Desktop, Cursor, Windsurf and .mcp.json configs
- Spawns each local stdio server and runs the real JSON-RPC initialize handshake
- Pinpoints the cause: missing env var, bad command or path, timeout, or protocol mismatch
For production & teams
MCP Doctor Pro
Free tests your local stdio servers. Most production MCP servers are remote HTTP/SSE — Pro actually connects to those and gates them in CI.
¥1,400 / month (≈ $9)
- Test remote HTTP / SSE / Streamable-HTTP servers — real handshake, auth check, tool count & latency
- CI mode — emits JUnit XML so a broken MCP config fails the build instead of shipping
- Pinpoints remote failures: 401/403 auth, wrong endpoint, timeout, protocol mismatch
- watch mode — get alerted the moment a server breaks (coming soon)
# after checkout you'll get a key by email
export MCP_DOCTOR_LICENSE=<key>
mcp-doctor --remote # or --ci for your pipeline
export MCP_DOCTOR_LICENSE=<key>
mcp-doctor --remote # or --ci for your pipeline