devtools-debugger-mcp-nodejs

Debug Node.js applications via Chrome DevTools Protocol with breakpoints, stepping, and variable inspection.

4|Updated May 16, 2026
One-click install
npx skills add https://github.com/reason-machines/devtools-skills --skill devtools-debugger-mcp-nodejs-reason-machines
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: devtools-debugger-mcp-nodejs
Source: https://github.com/reason-machines/devtools-skills/tree/main/skills/devtools-debugger-mcp-nodejs
Command: npx skills add https://github.com/reason-machines/devtools-skills --skill devtools-debugger-mcp-nodejs-reason-machines

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires devtools-debugger-mcp.

What problem does it solve? Debugging Node.js applications through AI assistants normally lacks programmatic control over breakpoints, stepping, and runtime state inspection. This MCP server exposes the full Chrome DevTools Protocol debugging surface as MCP tools, letting an AI launch Node.js processes with the inspector, pause execution, and examine variables without manual debugger setup. ## Core Features & Use Cases - Breakpoint Management: Set line breakpoints, conditional breakpoints, logpoints, and pause-on-exception states using absolute file paths or URL regex patterns. - Execution Control & Inspection: Resume, step over/into/out, continue to location, restart frames, inspect scopes and call stacks, and evaluate arbitrary JavaScript expressions in paused frames. - Source Map & Script Support: Debug TypeScript and transpiled code through automatic source map resolution, list loaded scripts, fetch sources, and blackbox dependency patterns. - Use Case: Debug an Express API by launching the server with environment variables, setting a breakpoint in a route handler, adding a logpoint in auth middleware, resuming execution, then evaluating req.body and inspecting scopes when paused. ## Quick Start Ask the AI to start a Node.js debug session for your script with an absolute path, set a breakpoint at a specific line, and inspect the variables when execution pauses.

Frequently Asked Questions about devtools-debugger-mcp-nodejs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug a Node.js application with breakpoints using MCP?▼

Start a session with the start_node_debug tool using an absolute script path, then set breakpoints with set_breakpoint by file path and 1-based line number. Resume execution and inspect scopes or evaluate expressions when the process pauses.

How to set conditional breakpoints in Node.js debugging?▼

Use the set_breakpoint_condition tool with a file path, line number, and a JavaScript condition expression such as "user.age > 18". Execution pauses only when the condition evaluates to true, and URL regex patterns work for modules in node_modules.

Does Chrome DevTools Protocol debugging support TypeScript source maps?▼

Yes, source maps are detected automatically when debugging compiled JavaScript. Ensure sourceMap is enabled in tsconfig.json and .map files exist alongside output, then set breakpoints using original .ts file paths.

Why is my Node.js breakpoint not being hit during debugging?▼

Breakpoints fail when file paths are relative instead of absolute, line numbers are 0-based, or code is unreachable. Use list_scripts to confirm the exact loaded URL, or fall back to a URL regex breakpoint pattern.

Can I evaluate expressions in a paused Node.js process?▼

Yes, the evaluate_expression tool runs JavaScript in any paused call frame, optionally targeting a specific frameIndex and returning results by value. It also supports side effects, such as mutating arrays during the paused state.

How do I avoid pausing inside node_modules while stepping?▼

Use the blackbox_scripts tool with patterns like "node_modules/express/*" to skip matching frames during step-into operations. Blackboxed scripts still execute but will not pause the debugger.