MCP Doctor MCP Server

Diagnose, secure, and benchmark your MCP servers. The mcp doctor mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 7 defined tools rather than through you.

What it actually does

Zero-config CLI that auto-discovers MCP server configs across Claude Code, Cursor, VS Code, Windsurf, and Claude Desktop — then tests connections, flags security issues, and benchmarks latency in seconds.

• Servers go down — and you don't notice until a tool call fails mid-conversation
• Secrets leak — — API keys hardcoded in config files, tokens visible in process args
• Slow servers — drag down your entire AI workflow without you realizing it
• Configs drift — between tools — what works in Cursor might be broken in Claude Desktop

Its toolset

Everything the assistant can do here goes through one of these:

• doctor — Run all checks at once (scan + security + bench)
• scan — Test all MCP server connections
• security — Audit configs for security issues
• bench — Benchmark server response times
• serve — Run as an MCP server (stdio transport)
• Cursor — ✅
• Windsurf — ✅

Adding it to your client

Installation goes through your MCP client rather than a global install: point it at @wigu/mcp-doctor on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MCP Doctor's toolset — doctor, scan, security and 4 more — is a fair guide to whether it matches your workflow. It is maintained by realwigu; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the mcp doctor mcp server does with a few real requests.