LLM-driven debugger server – give your AI agents step-through debugging superpowers
Copy the install, test the workflow, then decide if it earns a permanent slot.
Fresh repo activity plus visible builder pull. This is the kind of tool people test before it turns obvious.
Copy the install, test the workflow, then decide if it earns a permanent slot.
Reasonable to try, but it will take more than a quick skim to get real signal.
GitHub health 87/100. no security policy. Fresh enough repo health and manageable issue load keep the risk controlled.
AI Agent
Universal
Model
Multiple
Build Time
Instant
Fastest way to find out if mcp-debugger belongs in your setup.
Copy the install command, run a real test, and back it out cleanly if it slows you down.
git clone https://github.com/debugmcp/mcp-debugger ~/.claude/agents/mcp-debuggerRun this first. You will know quickly if the workflow earns a permanent slot.
rm -rf ~/.claude/agents/mcp-debuggerNo messy cleanup loop. If it misses, remove it and keep moving.
Install Location
~/ └─ .claude/ ├─ commands/ ├─ agents/ │ └─ mcp-debugger/ ← installs here └─ settings.json
LLM-driven debugger server – give your AI agents step-through debugging superpowers