Mcp Debugger
Give your agent debugger-grade control over Node.js and TypeScript runs so you can reproduce failures and inspect state without leaving the IDE.
Overview
io.github.Digital-Defiance/mcp-debugger is a MCP server for the Ship phase that equips AI agents with 25+ Node.js and TypeScript debugging tools.
What is this MCP server?
- 25+ debugging tools for Node.js and TypeScript aimed at AI agents
- npm package @ai-capabilities-suite/mcp-debugger-server v1.1.8
- stdio MCP transport for Claude Code, Cursor, and similar hosts
- Debugger MCP server, not a linter-only or log-tail skill
- 25+ debugging tools documented
- Server version 1.1.8
Community signal: 2 GitHub stars.
What problem does it solve?
Agents often suggest fixes for Node/TS bugs without seeing runtime state, which slows solo builders during test failures and pre-release regressions.
Who is it for?
Indie developers on Node or TypeScript stacks who debug interactively with Claude Code or Cursor during test and fix cycles.
Skip if: Teams on non-JS runtimes only, or anyone who wants hosted production monitoring instead of IDE-linked debugging.
What do I get? / Deliverables
You get agent-driven debug sessions with concrete inspection tools so fixes target verified behavior instead of speculative patches.
- Agent-invokable Node/TS debug tool surface
- Faster root-cause passes on failing runs before ship
Recommended MCP Servers
Journey fit
Canonical shelf is Ship because systematic debugging sits between feature work and safe release, alongside test and review loops. Testing subphase covers interactive debugging sessions, breakpoints, and run inspection—not just unit test runners.
How it compares
Runtime debugger MCP for Node/TS, not a static analysis-only skill or cloud error tracker.
Common Questions / FAQ
Who is io.github.Digital-Defiance/mcp-debugger for?
Solo and indie builders using Node.js or TypeScript who want their agent to debug with real tooling instead of only reading source files.
When should I use io.github.Digital-Defiance/mcp-debugger?
Use it during Ship testing and fix loops, and again in Operate when reproducing errors locally before you patch and redeploy.
How do I add io.github.Digital-Defiance/mcp-debugger to my agent?
Install @ai-capabilities-suite/mcp-debugger-server from npm, add the stdio server entry to your MCP config, then ask the agent to drive debug tools on your project.