How to Use It Well
- Setup time ~10 minutes (npm + connect from your MCP client)
- GitHub stars + forks (verified): see Source & Thanks
- One MCP tool call can replace multiple “please step/print/inspect” prompt turns
If your agent’s debugging loop is “edit → run → read logs → guess”, you waste tokens and time. With mcp-debugger, you can make debugging state explicit: set one breakpoint, step a few frames, and inspect locals/stack via structured calls.
FAQ
Q: What does it actually expose? A: A set of MCP tools that map to DAP-style debugging actions like create session, breakpoints, stepping, stack and variables.
Q: Do I need an IDE UI? A: No. Agents can drive debugging headlessly by calling MCP tools; your IDE is optional.
Q: Is it safe for production? A: Use it in dev/CI environments. Limit what files/processes the debugger can touch and run it with least privilege.