MCP NodeJS Debugger
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Capabilities
Server capabilities have not been inspected yet.
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_overB | Steps over to the next line of code |
| step_intoC | Steps into function calls |
| step_outC | Steps out of current function |
| continueC | Continues code execution |
| delete_breakpointC | Deletes a specified breakpoint |
| list_breakpointsB | Lists all active breakpoints |
| evaluateC | Evaluates a JavaScript expression in the current context |
| get_locationB | Gets the current execution location when paused |
| get_console_outputC | Gets the most recent console output from the debugged process |
| retry_connectB | 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 | |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/workbackai/mcp-nodejs-debugger'
If you have feedback or need assistance with the MCP directory API, please join our Discord server