MCP NodeJS Debugger
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| nodejs_inspectC | Executes JavaScript code in the debugged process |
| set_breakpointC | Sets a breakpoint at specified line and file |
| inspect_variablesC | Inspects variables in current scope |
| step_overA | Steps over to the next line of code |
| step_intoC | Steps into function calls |
| step_outB | Steps out of current function |
| continueC | Continues code execution |
| delete_breakpointC | Deletes a specified breakpoint |
| list_breakpointsA | Lists all active breakpoints |
| evaluateC | Evaluates a JavaScript expression in the current context |
| get_locationA | Gets the current execution location when paused |
| get_console_outputC | Gets the most recent console output from the debugged process |
| retry_connectC | Manually triggers a reconnection attempt to the Node.js debugger |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
Most tools have distinct purposes, but 'evaluate' and 'nodejs_inspect' both execute code, causing potential confusion. The stepping and breakpoint tools are clearly differentiated.
Naming mixes conventions: 'continue' is a verb alone, 'nodejs_inspect' is noun_verb, and 'retry_connect' is verb_verb. Most others follow verb_noun, but inconsistency lowers clarity.
13 tools cover essential debugging actions—breakpoints, stepping, inspection, evaluation, and connection—without being excessive or sparse for the domain.
Core debugging workflows are covered, but missing features like call stack inspection, watch variables, and conditional/exception breakpoints create minor gaps.