Node.js Debugger MCP

An MCP server that provides comprehensive Node.js debugging capabilities using the Chrome DevTools Protocol. This server enables AI assistants to debug Node.js applications with full access to breakpoints, stepping, variable inspection, call stacks, expression evaluation, and source maps.

Why use this MCP server?

This MCP server is useful when you need AI assistance with debugging Node.js applications. It provides programmatic access to all the debugging features you'd find in Chrome DevTools or VS Code, allowing AI assistants to help you set breakpoints, inspect variables, step through code, and analyze runtime behavior.

Features

• Full Node.js debugger: Set breakpoints, conditional breakpoints, logpoints, and pause-on-exceptions
• Stepping controls: Step over/into/out, continue to location, restart frame
• Variable inspection: Explore locals/closure scopes, this preview, and drill down into object properties
• Expression evaluation: Evaluate JavaScript expressions in the current call frame with console output capture
• Call stack analysis: Inspect call stacks and pause-state information
• Source map support: Debug TypeScript and other transpiled code with full source map support
• Console monitoring: Capture and review console output during debugging sessions

Installation

npm install devtools-debugger-mcp

Configuration

Add the server to your MCP settings configuration:

{
  "devtools-debugger-mcp": {
    "command": "node",
    "args": ["path/to/devtools-debugger-mcp/dist/index.js"]
  }
}

Alternatively, if installed globally, you can use the CLI binary:

{
  "devtools-debugger-mcp": {
    "command": "devtools-debugger-mcp"
  }
}

Node.js Debugging

This MCP server can debug Node.js programs by launching your script with the built‑in inspector (--inspect-brk=0) and speaking the Chrome DevTools Protocol (CDP).

How it works

• start_node_debug spawns node --inspect-brk=0 your-script.js, waits for the inspector WebSocket, attaches, and returns the initial pause (first line) with a pauseId and top call frame.
• You can then set breakpoints (by file path or URL regex), choose pause-on-exceptions, and resume/step. At each pause, tools can inspect scopes, evaluate expressions, and read console output captured since the last step/resume.
• When the process exits, the server cleans up the CDP session and resets its state.

Quickstart (from an MCP-enabled client)

1. Start a debug session

{ "tool": "start_node_debug", "params": { "scriptPath": "/absolute/path/to/app.js" } }

2. Set a breakpoint (file path + 1-based line)

{ "tool": "set_breakpoint", "params": { "filePath": "/absolute/path/to/app.js", "line": 42 } }

3. Run to next pause (optionally include console/stack)

{ "tool": "resume_execution", "params": { "includeConsole": true, "includeStack": true } }

4. Inspect at a pause

{ "tool": "inspect_scopes", "params": { "maxProps": 15 } }
{ "tool": "evaluate_expression", "params": { "expr": "user.name" } }

5. Step

{ "tool": "step_over" }
{ "tool": "step_into" }
{ "tool": "step_out" }

6. Finish

{ "tool": "stop_debug_session" }

Node.js tool reference (summary)

• start_node_debug({ scriptPath, format? }) — Launches Node with inspector and returns initial pause.
• set_breakpoint({ filePath, line }) — Breakpoint by file path (1-based line).
• set_breakpoint_condition({ filePath?, urlRegex?, line, column?, condition, format? }) — Conditional breakpoint or by URL regex.
• add_logpoint({ filePath?, urlRegex?, line, column?, message, format? }) — Logpoint via conditional breakpoint that logs and returns false.
• set_exception_breakpoints({ state }) — none | uncaught | all.
• blackbox_scripts({ patterns }) — Ignore frames from matching script URLs.
• list_scripts() / get_script_source({ scriptId? | url? }) — Discover and fetch script sour

... View full README on GitHub