Install
$ agentstack add mcp-qckfx-node-debugger-mcp ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Node.js Debugger MCP Server
An MCP server that provides Node.js debugging capabilities with process management for AI agents.
Features
- Process Management: Start/stop Node.js processes with debugging enabled
- Debugging Tools: Set breakpoints, step through code, evaluate expressions
- Inspector Integration: Connect to Node.js Inspector API
- AI Agent Friendly: Designed for long-running debugging sessions
Installation
- Build the server:
``bash npm install npm run build ``
- For Project-Specific Use: The
.mcp.jsonfile is already configured in this project
- For User-Wide Use: Add to your global Claude Code configuration:
``bash claude mcp add --scope user debugger-mcp node /absolute/path/to/debugger-mcp/build/index.js ``
- For Global Use: Copy the
.mcp.jsonto your projects or add to global config
Usage with Claude Code
Once configured, you'll have access to these tools in Claude Code:
Process Management
start_node_process- Launch Node.js scripts with debuggingkill_process- Terminate processes by PIDlist_processes- Show all managed processes
Debugging
attach_debugger- Connect to debug portset_breakpoint- Set breakpoints with optional conditions- Important: Use full
file://URLs for reliable breakpoint hits - Example:
file:///Users/you/project/script.js step_debug- Step through code (next/step/continue/out)pause_execution- Manually pause a running processevaluate_expression- Evaluate expressions in debug context
Resources
debug://session- Current debug session statedebug://processes- List of managed processes
Example Usage
- Start a Node.js process:
`` Use the start_node_process tool with script: "example-app.js" ``
- Attach debugger:
`` Use attach_debugger tool with the port returned from step 1 ``
- Set breakpoints and debug:
``` # Set a breakpoint using full file URL Use set_breakpoint tool with:
- file: "file:///absolute/path/to/example-app.js"
- line: 5
# Control execution Use step_debug tool with action: "continue" ```
Key Features
- Automatic Pause on Start: Uses
--inspect-brkflag to pause at first line - Full Chrome DevTools Protocol: Real debugging, not simulation
- Reliable Breakpoints: Use
file://URLs for consistent breakpoint hits - Process Management: Track and manage multiple debugging sessions
Testing
Test with the included example app:
node --inspect=9229 example-app.js
Then use the MCP tools to debug it!
Debug the MCP Server
npm run inspector
Source & license
This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: qckfx
- Source: qckfx/node-debugger-mcp
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.