Node.js Debugger MCP Server
Related Servers
Alternatives to Node.js Debugger MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to debug Node.js applications using Chrome DevTools Protocol. Provides comprehensive debugging capabilities including breakpoints, stepping, variable inspection, expression evaluation, and console monitoring.676 npm348MIT
- FlicenseAqualityCmaintenanceEnables coding agents to debug Node.js programs via MCP tools, using Chrome DevTools Protocol for launching, attaching, breakpoints, stepping, variables, and console access.212-
- AlicenseNot gradedqualityCmaintenanceA Node.js debugger for AI agents that enables setting breakpoints, stepping through code, and inspecting variables via the Chrome DevTools Protocol.60 npm2MIT
- AlicenseCqualityAmaintenanceEnables AI agents to perform step-through debugging of Python, JavaScript/Node.js, and Rust programs using the Debug Adapter Protocol, with support for breakpoints, variable inspection, and stack traces.21166MIT
- AlicenseNot gradedqualityBmaintenanceGives AI agents full control of VS Code's debugging engine — set breakpoints, launch/attach sessions, step through code, inspect call stacks and variables, and evaluate expressions in the paused frame.MIT
- AlicenseBqualityDmaintenanceMCP server for debugging Node.js programs through the V8 Inspector Protocol, allowing AI agents to set breakpoints, inspect variables, and step through code.117 npm5MIT
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose within the Node.js debugging domain, with no overlapping functionality. For example, attach_debugger, start_node_process, and list_processes handle different aspects of process management, while pause_execution, step_debug, and set_breakpoint target specific debugging actions without ambiguity.
All tool names follow a consistent verb_noun pattern using snake_case, such as attach_debugger, evaluate_expression, and pause_execution. This uniformity makes the tool set predictable and easy to understand, with no deviations in naming conventions across the eight tools.
With 8 tools, the server is well-scoped for Node.js debugging, covering essential operations like process management, execution control, and expression evaluation. Each tool earns its place by addressing a specific need in the debugging workflow, avoiding both bloat and gaps in functionality.
The tool set provides comprehensive coverage for core Node.js debugging tasks, including process lifecycle (start, list, kill), execution control (pause, step), and debugging setup (attach, set breakpoint). A minor gap exists in missing tools for removing breakpoints or inspecting variables, but agents can still perform most debugging workflows effectively.