A
licenseNot graded
qualityA
maintenanceMCP server that lets AI coding tools control and observe a running Node.js process through the chrome devtools protocol (CDP), via a lightweight Debug Adapter Protocol (DAP) bridge.
20 npm
2
MIT
mcp-debugger-node
Related Servers
Alternatives to mcp-debugger-node
No user-submitted related servers found.
Related Servers
- 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 gradedqualityCmaintenanceMCP server for AI-assisted Python debugging using debugpy and Debug Adapter Protocol, enabling AI agents to run tests, set breakpoints, and inspect variables via natural language.8MIT
- FlicenseNot gradedqualityAmaintenanceAn MCP server and VS Code extension that enables AI clients to interactively debug code using breakpoints, execution control, and state inspection. It is language-agnostic and works with any debugger that supports VS Code's launch.json configurations.-
- AlicenseNot gradedqualityBmaintenanceAn MCP server that lets AI agents debug Python code by running scripts, setting breakpoints, stepping through execution, inspecting live variable values, and editing or reverting files to verify fixes. It relies only on Python's standard sys.settrace, requiring no debugpy, DAP, pdb, or PTY.MIT
- FlicenseNot gradedqualityDmaintenanceA lightweight MCP server that enables AI assistants to control Chrome DevTools via CDP for debugging tasks like navigation, screenshots, and JavaScript execution.-
TDQS
B3.4/5.0
Scored across 11 tools
Disambiguation5/5
Each tool has a distinct purpose with clear descriptions; continue and resume are differentiated by return behavior, and all other tools target unique debugger actions.
Naming Consistency2/5
Tool names mix single-word verbs (continue, stop) with underscore-separated phrases (set_breakpoint, wait_for_pause), and 'getvariables' lacks a separator, creating an inconsistent pattern.
Tool Count5/5
11 tools cover essential debugger operations without being excessive, fitting well within the typical 3-15 range for a focused domain.
Completeness2/5
Missing critical features like removing or listing breakpoints, retrieving call stacks, and setting variables, which are essential for productive debugging sessions.
Maintenance
ActivityInactive
ResponsivenessNo issues