$ loading_
Debug Node.js programs via V8 Inspector with breakpoints and variable inspection.
This is an open-source MIT-licensed MCP server for debugging Node.js programs, with no declared secrets or remote endpoints and no obvious high-risk red flags in the provided materials. Its core functionality inherently involves local debugging and code-execution-adjacent control, so it should be used with least privilege in an isolated environment.
The materials explicitly state that no keys or environment variables are required, and there is no description of credential collection, storage, or upload; based on the available information, credential exposure appears low.
No remote endpoints or external API connections are declared. The description focuses on debugging local Node.js programs via the V8 Inspector Protocol, with no clear indication of user data being sent out.
The system flags executes-code, and the tool's functionality includes attaching to Node.js programs, setting breakpoints, stepping through execution, and inspecting runtime variables. This implies local process interaction and strong debugging control, but the provided materials do not show suspicious permission requests beyond its stated purpose.
A debugger can inspect variables and program state, which typically gives indirect visibility into memory, source paths, or runtime data accessible to the target process. The materials do not specify additional file read/write scope, so this appears to be inherent debugger visibility rather than clear over-privileged access.
Positive factors include being open source under the MIT license, making it more auditable than closed-source alternatives. However, it comes from a third-party registry, the GitHub repository has 0 stars, and maintenance status is unknown, so trust is limited; review the source and dependencies before using it in sensitive environments.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "mcp-debugger-node" yet — see the docs or source repo.
Connect to my Node.js service debug session, set a breakpoint in the /api/users request handler, reproduce the 500 error, and inspect variable values and the call stack before the exception is thrown.
Returns breakpoint hits, key variable states, the call stack, and likely causes of the error.
Debug this Node.js script and step through execution starting from the job queue consumer entry point, focusing on parameter passing and state changes across async functions.
Outputs the function path, parameter changes during stepping, and suggestions for locating abnormal behavior.
Attach to the running Node.js process, inspect objects in the current context while the data processing function executes, and determine why a specific field is empty.
Provides inspection results, possible reasons the field is empty, and suggested code locations to verify.
Debug Node.js code for AI agents with breakpoints, stepping, and variable inspection.
Debug Python with natural language, tests, breakpoints, and variable inspection.
Control and debug running Node.js processes through a CDP-to-DAP bridge.
Let AI control GDB via MCP for breakpoints, stepping, and inspection.
Debug Electron apps via MCP with process control and deep inspection.
Connect Chrome DevTools so AI can debug pages and inspect performance.