Node.jsNode.jsDebugger MCPDebugger MCP

2025Solo DeveloperActive

An MCP server that gives AI coding agents real Node.js debugging capabilities.

Most AI coding agents debug by reading code and adding console.log statements. This MCP server gives them access to an actual debugger—breakpoints, stepping, expression evaluation, call stacks—the same Chrome DevTools Protocol interface that powers VS Code’s debugger, exposed as MCP tools.

The server manages the full process lifecycle. It spawns Node.js processes with the inspector flag, auto-discovers available debug ports, and connects via CDP. Processes start paused at the first line to eliminate timing race conditions between spawning and attaching. When a process exits, the server cleans up its debug session, port allocation, and state automatically.

The interesting part is how this changes the debugging loop for an AI agent. Instead of guessing at what’s wrong from static code, the agent can set a breakpoint, run the code, inspect the actual values at that point, and step through the execution. It’s a much tighter feedback loop.

Stack
TypeScriptNode.jsChrome DevTools ProtocolMCP
Features
  • Spawn and manage Node.js processes with debug ports
  • Set breakpoints with optional conditions
  • Step through code (into, over, out, continue)
  • Evaluate expressions in the current call frame
  • Automatic port discovery and conflict avoidance
  • Process lifecycle cleanup on exit or disconnect