
dr-mcp
If you run multiple MCP clients like Claude Desktop, Cursor, Windsurf, or Codex across different projects, your server configs accumulate quietly: duplicate GitHub tools, abandoned packages, broad filesystem grants, context-heavy servers your agent considers on every turn. This audits your MCP setup without deleting anything during scan. It parses JSON, TOML, and YAML configs, scores them for reliability and security, checks npm for stale pins and major upgrades, estimates tool surface area, flags archived repos, and generates reversible patch plans. Run `npx @inferensys/dr-mcp cleanup` at the command line or call `dr_mcp_scan` from inside your agent to see duplicates, dead entries, permission risks, and which servers are adding the most tools to your context window.
- tools
- 7
- transport
- STDIO
- last updated
- May 15, 2026
Tools
7 toolsPublic tool metadata for what this MCP can expose to an agent.
dr_mcp_scanRun a scan of the MCP setup from an MCP client.
Run a scan of the MCP setup from an MCP client.
No parameter schema in public metadata yet.
dr_mcp_cleanupSurface cleanup candidates, upgrades, abandoned servers, and long-lived installs.
Surface cleanup candidates, upgrades, abandoned servers, and long-lived installs.
No parameter schema in public metadata yet.
scan_mcp_setup
No parameter schema in public metadata yet.
explain_issue
No parameter schema in public metadata yet.
generate_patch_plan
No parameter schema in public metadata yet.
apply_patch_plan
No parameter schema in public metadata yet.
export_report
No parameter schema in public metadata yet.
Sponsors
Readme
dr-mcp
Clean your MCPs.
dr-mcp is a local-first MCP audit and cleanup tool for developers who use agentic coding every day. It scans the Model Context Protocol configs your tools load, finds stale servers, abandoned packages, duplicate entries, context-heavy tools, risky permissions, and major upgrades, then generates reversible patch plans.
If you use Claude Code, OpenAI Codex, Cursor, Windsurf, GitHub Copilot, VS Code, Cline, Roo Code, Continue, or Zed across multiple projects, your MCP setup can grow quietly: old demo servers, duplicate GitHub tools, broad filesystem access, package pins behind npm latest, abandoned repositories, and large tool surfaces your agent has to consider before it writes code.
dr-mcp shows what to clean up without deleting anything during scan.
npx @inferensys/dr-mcp cleanup
That starts a local cleanup scan in the current project. You get a redacted report, a ranked list of context-heavy MCPs, package and repository freshness signals, and patch plans you can apply after review.
For the full cleanup scan with package/repo checks and local install-history tracking:
npx @inferensys/dr-mcp cleanup --registry --track-usage
Details
- Repository
- github.com/inferensys/dr-mcp
- Website
- inferensys.github.io/dr-mcp
- Package
@inferensys/dr-mcp- Transport
- STDIO
- Registry
- MCP registry, active