node-devtools-cli

CLI for debugging Node.js backend processes with non-blocking inspection. Use when the user needs to connect to Node.js processes (by PID, name, Docker, or port), set tracepoints/logpoints/exceptionpoints, capture call stacks and local variables, or inspect console logs. Requires daemon; connect before other debug commands.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "node-devtools-cli" with this command: npx skills add serkan-ozal/browser-devtools-skills/serkan-ozal-browser-devtools-skills-node-devtools-cli

Node DevTools CLI

Command-line interface for non-blocking debugging of Node.js backend processes. Connects via the Inspector Protocol (Chrome DevTools Protocol) and provides tracepoints, logpoints, exceptionpoints, and watch expressions without pausing execution.

Installation

Same package as browser-devtools-mcp:

npm install -g browser-devtools-mcp

Quick Start

# 1. Start daemon (if not running)
node-devtools-cli daemon start

# 2. Connect to a Node.js process (by PID)
node-devtools-cli --session-id my-debug debug connect --pid 12345

# 3. Set a tracepoint on server.js line 42
node-devtools-cli --session-id my-debug debug put-tracepoint \
  --url-pattern "server.js" \
  --line-number 42

# 4. Trigger the code path (e.g., make API request to your app)
# 5. Get captured snapshots
node-devtools-cli --session-id my-debug --json debug get-probe-snapshots

Global Options

OptionDescriptionDefault
--port <number>Daemon server port2020
--session-id <string>Session for Node connection persistenceauto
--jsonOutput as JSON (recommended for AI)false
--quietSuppress log messagesfalse
--verboseEnable debug outputfalse
--timeout <ms>Operation timeout30000

AI Agent Recommended:

node-devtools-cli --json --quiet --session-id "debug-session" <command>

Tool Domains

DomainDescriptionReference
debugConnection, tracepoints, logpoints, exceptionpoints, watch, snapshots

Connection Methods

Connect via debug connect with one of:

MethodOptionExample
PID--pid <number>--pid 12345
Process name--process-name <pattern>--process-name "server.js"
Docker container--container-id or --container-name--container-name my-api
Inspector port--inspector-port <number>--inspector-port 9229
WebSocket URL--ws-url <url>--ws-url "ws://127.0.0.1:9229/abc"

If the process doesn't have --inspect active, the CLI activates it via SIGUSR1 (no code changes). For Docker: expose port 9229 and use --inspect=0.0.0.0:9229.

CLI Management Commands

Daemon

node-devtools-cli daemon status
node-devtools-cli daemon start
node-devtools-cli daemon stop
node-devtools-cli daemon restart
node-devtools-cli daemon info

Session

node-devtools-cli session list
node-devtools-cli session info <session-id>
node-devtools-cli session delete <session-id>

Tools

node-devtools-cli tools list
node-devtools-cli tools search <query>
node-devtools-cli tools info <tool-name>

Config & Updates

node-devtools-cli config
node-devtools-cli update --check

Examples

Connect by PID

SESSION="--session-id api-debug"

# Connect
node-devtools-cli $SESSION debug connect --pid $(pgrep -f "node server.js")

# Set tracepoint on route handler
node-devtools-cli $SESSION debug put-tracepoint \
  --url-pattern "routes/api.ts" \
  --line-number 25

# Trigger: curl http://localhost:3000/api/users
# Get snapshots
node-devtools-cli $SESSION --json debug get-probe-snapshots

Connect by Process Name

node-devtools-cli debug connect --process-name "api"

Docker Container

# App runs in container with -p 9229:9229
node-devtools-cli debug connect \
  --container-name my-node-app \
  --host host.docker.internal \
  --inspector-port 9229

Exception Catching

SESSION="--session-id exc-debug"

node-devtools-cli $SESSION debug connect --pid 12345
node-devtools-cli $SESSION debug put-exceptionpoint --state uncaught

# Trigger error in app
# Check snapshots
node-devtools-cli $SESSION --json debug get-probe-snapshots --types exceptionpoint

Interactive Mode

node-devtools-cli interactive
CommandDescription
helpShow commands
exit, quitExit
debug connectConnect to process
debug statusConnection status
<domain> <tool>Execute tool

Shell Completions

eval "$(node-devtools-cli completion bash)"
eval "$(node-devtools-cli completion zsh)"

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Coding

browser-testing

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

react-debugging

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

browser-devtools-cli

No summary provided by upstream source.

Repository SourceNeeds Review