Skip to main content
Glama
debugmcp

MCP Debugger

by debugmcp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to MCP Debugger

No user-submitted related servers found.

    Related Servers

    • DebugMCP by microsoft

      DebugMCPofficial

      microsoft
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to debug code inside VS Code by setting breakpoints, stepping through execution, inspecting variables, and evaluating expressions across multiple languages.
      551
      MIT

    • mcp-debug-tools

      hwanyong
      A
      license
      Not graded
      quality
      D
      maintenance
      Bridges AI agents with VS Code's debugger, enabling breakpoint management, step execution, variable inspection, and stack tracing via CLI commands.
      24
      GPL 3.0

    • cdp-tools-mcp

      InDate
      A
      license
      B
      quality
      A
      maintenance
      Enables AI agents to debug code and automate browsers using Chrome DevTools Protocol, supporting breakpoints, variable inspection, and replayable interaction recording.
      35
      604 npm
      17
      MIT

    • MCP JS Debugger

      johngrimes
      A
      license
      A
      quality
      C
      maintenance
      Enables 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.
      18
      10 npm
      2
      Apache 2.0

    • vscode-debug-mcp

      laststance
      A
      license
      Not graded
      quality
      D
      maintenance
      Gives 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
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.5/5.0

    Scored across 28 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes (e.g., step_over vs step_into vs continue_execution, get_scopes vs get_variables). However, create_debug_session, attach_to_process, and start_debugging overlap in session attachment/launch semantics, which could cause an agent to hesitate between them. Descriptions help but do not fully resolve the boundary.

    Naming Consistency5/5

    All 28 tools follow a consistent snake_case verb_noun pattern (e.g., set_breakpoint, list_breakpoints, get_stack_trace, close_debug_session). Even the few exceptions like step_over and step_into fit the same naming family. No mixed conventions or chaotic naming.

    Tool Count3/5

    28 tools is on the heavy side for an MCP server, and some features are convenience layers (get_local_variables) or advanced/niche (expose_session, redefine_classes). The debugger domain legitimately requires many operations, so it is borderline rather than clearly excessive, but a few tools could be merged or omitted.

    Completeness4/5

    The surface covers core debugger lifecycle: session management, breakpoints, stepping, inspection (variables, stack, scopes, threads), evaluation, output, and session teardown. Minor gaps exist (e.g., no explicit conditional breakpoint or logpoint update tool, no watch expression management), but agents can work around most of these.

    Maintenance

    ActivityActive
    ResponsivenessWithin a week

    Resources