apply_patch_plan
Apply a patch plan after explicit confirmation. Creates backups before writing.
LABSCO SUMMARY
Redaction on the diagnostic report is the detail that makes this shareable — MCP config files are full of keys, and a diagnostic nobody can paste is a diagnostic nobody uses.
The whole point of a config diagnostic is showing it to someone else, and MCP configuration is exactly where API keys live. Redacting by default rather than as an option means the report can go into an issue or a chat without a review step. The write path is separated the way it should be — scan, explain, plan, then apply behind an explicit confirmation with backups already written — which matters more here than usual, because the thing being modified is the configuration the agent itself runs on. Context weight as a first-class diagnostic is a good instinct: an over-attached MCP setup degrades every turn quietly, and nothing else measures it.
What it is
A diagnostic tool for the MCP configuration itself: it scans local config files, explains what it found, generates a reversible patch plan, and applies it only after explicit confirmation.
What you get
- dr_mcp_scan is the one-step check for an agent session — context weight and stale entries among them — and dr_mcp_cleanup returns the highest-value cleanup candidates without applying anything.
- scan_mcp_setup reads local configuration files and returns a redacted diagnostic report, so the output can be shared without leaking credentials.
- explain_issue expands a single diagnostic rather than leaving a finding as a label.
- generate_patch_plan produces a reversible plan and apply_patch_plan applies it only after explicit confirmation, creating backups before it writes.
- export_report writes the redacted report as Markdown, HTML or JSON.
Requirements
Nothing to supply — it reads the MCP configuration already on the machine.
Setup effort
One command — npx -y @inferensys/dr-mcp server
USE CASES
01
Finding out why the session feels heavy
Run the one-step scan for context weight and stale entries, and read the highest-value cleanup candidates before changing anything.
02
Understanding a finding rather than acting on a label
Expand the specific diagnostic to see what it means and why it was raised.
03
Fixing it without risking the config
Generate the reversible patch plan, review it, then apply with explicit confirmation — backups are written before anything changes.
04
Showing someone else what is wrong
Export the redacted report as Markdown, HTML or JSON, safe to paste because the credentials are already stripped.
7 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
dr_mcp_cleanup
Scan and return the highest-value MCP cleanup candidates. Does not apply patches.
dr_mcp_scan
One-step MCP cleanup scan for agent sessions. Checks context weight, stale packages, abandoned repos, duplicates, and safe patch plans.
explain_issue
Explain a diagnostic from the current MCP setup scan.
export_report
Export a redacted dr-mcp report as Markdown, HTML, or JSON.
generate_patch_plan
Generate a reversible patch plan for a scan finding.
scan_mcp_setup
Scan local MCP configuration files and return a redacted diagnostic report.
BEFORE YOU INSTALL
What to know first
Tools you get
7 tools when we connected.
Requires
npx on PATH
CONTEXT COST
Light Standing cost
Rated by the size of the 7 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"dr-mcp": {
"command": "npx",
"args": [
"-y",
"@inferensys/dr-mcp",
"server"
]
}
}
}npx
TERMINAL
npx -y @inferensys/dr-mcp server
