skills.rest
Aradotso
AradotsoOFFICIAL
Explore all skills by this author →
Website𝕏@aradotsoGitHub

devtools-debugger-mcp-nodejs

Control Node.js debugging via Chrome DevTools Protocol with breakpoints and stepping.

4|Updated May 16, 2026
Search Tags:#debugging#mcp#nodejs#breakpoints#chrome devtools protocol#typescript source maps#ai debugging workflow
One-click install
npx skills add https://github.com/Aradotso/devtools-skills --skill devtools-debugger-mcp-nodejs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: devtools-debugger-mcp-nodejs
Source: https://github.com/Aradotso/devtools-skills/tree/main/skills/devtools-debugger-mcp-nodejs
Command: npx skills add https://github.com/Aradotso/devtools-skills --skill devtools-debugger-mcp-nodejs

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

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 Node.js applications using AI without the browser DevTools UI?▼

You can debug Node.js applications via an MCP interface that connects the Chrome DevTools Protocol programmatically, letting you set breakpoints, step through execution, and inspect state directly from your AI client without manual UI interaction.

Can I set conditional breakpoints and logpoints for Node.js debugging through MCP?▼

Yes, MCP-driven Node.js debugging supports configuring line breakpoints, conditional breakpoints, logpoints, and pause-on-exceptions for both uncaught and all exceptions, enabling precise control over execution pauses.

Does Node.js MCP debugging support TypeScript source maps for inspecting scopes?▼

Yes, source-map-aware debugging is supported, allowing you to inspect scopes and objects with TypeScript source-mapped line mapping. You can evaluate JavaScript expressions in specific call frames during execution pauses.

How do I start a Node.js debug session with the Chrome DevTools Protocol via MCP?▼

Start your Node.js process with the inspector enabled, then ask your MCP client to initiate the debug session. You can set breakpoints at absolute file paths and line numbers to pause execution and inspect variables.

Can I capture console output between breakpoints to correlate logs with program state?▼

Yes, the MCP debugging tool buffers and retrieves console output between pauses, allowing you to correlate console logs with the exact program state at each breakpoint or step during the debug session.

What's the best way to diagnose a failing async API endpoint in Node.js?▼

Use MCP tools to pause on a condition at the failing endpoint, inspect request-derived variables at the exact call frame, evaluate expressions to confirm assumptions, and step through the async call stack with TypeScript source-map-backed line mapping.

Related Skills

Explore More Software Engineering Skills→
RheasilviaRheasilvia

node-inspect-debugger

Debug Node.js applications via V8 inspector and Chrome DevTools Protocol.

Community
Advanced
BradliebsBradliebs

investigate

Diagnose software failures through a four-phase root-cause investigation workflow.

Community
Advanced
regybeanregybean
1

openrouter-typescript-sdk

Integrate OpenRouter's TypeScript SDK to access 300+ AI models via callModel.

Community
Intermediate
projectedanxprojectedanx
1

node-inspect-debugger

Control the Node.js V8 inspector for breakpoints, call stacks, and profiling.

Community
Advanced