Node.js Debugger MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| start_node_processC | Start a Node.js process with debugging enabled |
| kill_processC | Kill a managed Node.js process |
| list_processesB | List all managed Node.js processes |
| attach_debuggerC | Attach debugger to a running Node.js process |
| set_breakpointA | Set a breakpoint in the debugged process. Use full file:// URLs for reliable breakpoint hits. |
| step_debugC | Step through code execution |
| pause_executionB | Pause execution of the debugged process |
| evaluate_expressionC | Evaluate an expression in the current debug context |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Debug Session State | Current debugging session information |
| Managed Processes | List of managed Node.js processes |
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.