devtools-debugger-mcp-nodejs

What problem does it solve?

It removes the friction of debugging Node.js applications by letting you set breakpoints, step through execution, and inspect state through an MCP interface rather than manually using the browser debugger UI.

Core Features & Use Cases

• Breakpoint and exception control: Configure line breakpoints, conditional breakpoints, logpoints, and pause-on-exceptions (uncaught or all).
• Step-by-step execution & location control: Resume execution and step over/into/out or continue to a specific file location.
• Deep inspection and evaluation: Inspect scopes and objects and evaluate JavaScript expressions (including in specific call frames) while supporting source maps for TypeScript debugging.
• Console capture: Buffer and retrieve console output between pauses to correlate logs with program state.
• Use Case: Diagnose a failing async API endpoint by pausing on a condition, inspecting request-derived variables at the exact frame, evaluating expressions to confirm assumptions, and stepping through the failing call stack with source-map-backed TypeScript line mapping.

Quick Start

Ask your MCP client to start a Node.js debug session with the command line tool configured for devtools-debugger, then set a breakpoint at an absolute file path and line number to pause on execution and inspect variables.