Node.js Debugger MCP Server

Node.js Debugger MCP server enabling AI agents to debug Node.js applications — connecting to Node.js debug protocol, setting breakpoints, stepping through execution, inspecting variables and call stacks, and integrating Node.js debugging into agent-driven JavaScript/TypeScript development and troubleshooting workflows.

Evaluated Mar 06, 2026 (0d ago) vcurrent
Homepage ↗ Repo ↗ Developer Tools nodejs debugger debugging mcp-server javascript v8 inspector
⚙ Agent Friendliness
74
/ 100
Can an agent use this?
🔒 Security
74
/ 100
Is it safe for agents?
⚡ Reliability
65
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
65
Documentation
68
Error Messages
65
Auth Simplicity
95
Rate Limits
88

🔒 Security

TLS Enforcement
78
Auth Strength
70
Scope Granularity
65
Dep. Hygiene
68
Secret Handling
88

Localhost debug port only. Full code execution access via inspector. No credentials. Community MCP.

⚡ Reliability

Uptime/SLA
68
Version Stability
65
Breaking Changes
65
Error Recovery
62
AF Security Reliability

Best When

An agent needs to debug Node.js/TypeScript applications — stepping through code, inspecting runtime state, or diagnosing JavaScript errors via the V8 inspector protocol.

Avoid When

You're debugging Python, Java, or other languages — use language-specific debugger MCPs. Or prefer IDE-based debugging.

Use Cases

  • • Setting breakpoints and inspecting variable state from debugging agents
  • • Stepping through Node.js execution to understand behavior from coding agents
  • • Diagnosing runtime errors and exceptions from troubleshooting agents
  • • Profiling and analyzing Node.js performance from optimization agents
  • • Testing and verifying async JavaScript behavior from QA agents
  • • Automating debugging workflows for complex Node.js applications

Not For

  • • Python, Java, or other language debugging (Node.js V8 inspector only)
  • • Production debugging without proper safeguards (debug port security considerations)
  • • Teams preferring browser DevTools or IDE debuggers for Node.js

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes ↗
SDK
No
Webhooks
No
OpenAPI Spec ↗

Authentication

Methods: none
OAuth: No Scopes: No

No MCP auth — connects to Node.js process started with --inspect flag. Node.js debug port (9229 by default) should be restricted to localhost. No external auth needed.

Pricing

Model: free
Free tier: Yes
Requires CC: No

Free and open source. Requires only Node.js (free). No external service costs.

Agent Metadata

Pagination
none
Idempotent
Partial
Retry Guidance
Not documented

Known Gotchas

  • ⚠ Node.js app must start with --inspect or --inspect-brk flag before connecting
  • ⚠ Default debug port 9229 — ensure port matches configuration
  • ⚠ Debug port should be localhost-only — never expose to network in production
  • ⚠ Breakpoints are stateful — debugging session state affects program execution
  • ⚠ Community MCP — niche tool with limited testing across Node.js versions
  • ⚠ V8 inspector API changes across Node.js major versions — verify version compatibility

Alternatives

gdb-mcp-server mcp-server-code-runner tmux-mcp

Full Evaluation Report

Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for Node.js Debugger MCP Server.

$99
API endpoint ↗ Agent guide ↗ Report inaccuracy

Scores are editorial opinions as of 2026-03-06.

5211
Packages Evaluated
26151
Need Evaluation
173
Need Re-evaluation
♥
Community Powered