MCP Debugger
Related Servers
Alternatives to MCP Debugger
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to debug code inside VS Code by setting breakpoints, stepping through execution, inspecting variables, and evaluating expressions across multiple languages.523MIT
- AlicenseNot gradedqualityDmaintenanceBridges 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.3597 npm16MIT
- 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.189 npm2Apache 2.0
- AlicenseNot gradedqualityBmaintenanceGives 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 21 tools
Most tools are clearly distinct (session lifecycle, breakpoints, stepping, inspection), but start_debugging vs create_debug_session vs attach_to_process have some overlap in session creation. get_variables vs get_local_variables is intentional convenience but could cause confusion.
Consistent verb_noun pattern (create_, list_, set_, get_, step_, continue_, pause_, attach_, detach_, close_, evaluate_). Minor deviation: redefine_classes uses a verb_object pattern but is still readable and consistent with the style.
21 tools is on the heavier side but appropriate for a full debugger surface covering session lifecycle, breakpoints, stepping, inspection, and evaluation. Each tool maps to a standard debugger operation, so the count is justified.
Covers the core debugger lifecycle well: create/attach/start, breakpoints, stepping, continue/pause, threads, stack, scopes, variables, evaluation, and source context. Minor gaps: no remove_breakpoint, no disconnect/terminate distinction beyond detach/close, and no explicit session selection parameter on inspection tools (assumed current session).