MCP Debugger
Related Servers
Alternatives to MCP Debugger
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to debug code inside VS Code by setting breakpoints, stepping through execution, inspecting variables, and evaluating expressions across multiple languages.580MIT
- AlicenseNot gradedqualityCmaintenanceBridges AI agents with VS Code's debugger, enabling breakpoint management, step execution, variable inspection, and stack tracing via CLI commands.24GPL 3.0
- AlicenseBqualityDmaintenanceEnables AI agents to debug C/C++ programs with GDB or LLDB, supporting breakpoints, stepping, variable inspection, and function calls.20MIT
- AlicenseBqualityAmaintenanceEnables AI agents to debug code and automate browsers using Chrome DevTools Protocol, supporting breakpoints, variable inspection, and replayable interaction recording.353,254 npm19MIT
- AlicenseAqualityCmaintenanceEnables AI assistants to debug JavaScript and TypeScript applications by connecting to Chrome DevTools Protocol-compatible debuggers, allowing them to set breakpoints, step through code, inspect variables, and evaluate expressions with full source map support.188 npm2Apache 2.0
- AlicenseNot gradedqualityDmaintenanceGives AI agents full control of VS Code's debugging engine — set breakpoints, launch/attach sessions, step through code, inspect call stacks and variables, and evaluate expressions in the paused frame.MIT
TDQS
Scored across 29 tools
Most tools map to a distinct DAP operation (set/remove/clear breakpoints, step_over/into/out, pause vs continue vs wait_for_stop), and the descriptions actively clarify the run-state distinctions. The main overlaps are create_debug_session (which accepts every attach_to_process argument) versus attach_to_process, and get_variables versus get_local_variables, both of which an agent could plausibly misselect.
All 29 names are snake_case with a verb-first or clear noun-object pattern (list_threads, set_breakpoint, start_debugging, wait_for_stop), with the only mild deviation being the domain term hot_reload. The expose/unexpose_session pair is internally symmetric, so the convention holds throughout.
At 29 tools the surface is heavy, exceeding the comfortable range, though a full DAP debugger genuinely spans sessions, breakpoints, stepping, inspection, output, and hot reload. Some tools (expose_session/unexpose_session, hot_reload, list_supported_languages) are niche relative to the core debugging loop, pushing the set past what most agent sessions need.
Coverage is strong: session lifecycle (create/close/restart/detach), breakpoint CRUD plus clear, full stepping and pause/continue/wait, stack/scopes/variables/evaluate inspection, output streaming, source context, and hot reload. Gaps remain around exception-breakpoint configuration, conditional/watch (data) breakpoints, and explicit frame/thread selection or variable mutation outside evaluate_expression.