Clean your MCPs with config audits, context-weight analysis, abandoned-package checks, upgrade plans, usage history, and safe patch plans.
If you already use Dr MCP, the dr mcp mcp server is the piece that lets your assistant work with it directly. Clean your MCPs with config audits, context-weight analysis, abandoned-package checks, upgrade plans, usage history, and safe patch plans.
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.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
dr_mcp_scan — dr_mcp_cleanupscan_mcp_setup — explain_issuegenerate_patch_plan — apply_patch_planCursor — ~/.cursor/mcp.json, .cursor/mcp.jsonWindsurf — ~/.codeium/windsurf/mcp_config.json, .windsurf/mcp.jsonCline — ~/.cline/data/settings/cline_mcp_settings.json, .cline/data/settings/cline_mcp_settings.jsonContinue — ~/.continue/config.yaml, .continue/config.yamlZed — Zed user settings, .zed/settings.jsonCodex — The Codex tool exposed by this serverInstallation goes through your MCP client rather than a global install: point it at @inferensys/dr-mcp 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.
Among the file and storage access options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Dr MCP's toolset — dr_mcp_scan, scan_mcp_setup, generate_patch_plan and 6 more — is a fair guide to whether it matches your workflow. It is maintained by inferensys; 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.
| Tool | What it does |
|---|---|
| dr_mcp_scan | dr_mcp_cleanup |
| scan_mcp_setup | explain_issue |
| generate_patch_plan | apply_patch_plan |
| Cursor | ~/.cursor/mcp.json, .cursor/mcp.json |
| Windsurf | ~/.codeium/windsurf/mcp_config.json, .windsurf/mcp.json |
| Cline | ~/.cline/data/settings/cline_mcp_settings.json, .cline/data/settings/cline_mcp_settings.json |
| Continue | ~/.continue/config.yaml, .continue/config.yaml |
| Zed | Zed user settings, .zed/settings.json |
| Codex | The Codex tool exposed by this server. |
{
"mcpServers": {
"dr-mcp": {
"command": "npx",
"args": ["-y", "@inferensys/dr-mcp", "server"]
}
}
}Configuration as documented by the project. Restart the client after saving.
Scoped local file access — read, write, search and reorganise files in directories you explicitly allow.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Build a programmable telecommunications stack for connecting telephony services with the Internet via a cloud-based utility.
Chat with your second brain — search, read and write vault notes through the Local REST API.
Connects AI models to an Obsidian knowledge base for direct access and manipulation of notes and folders.