Skip to main content
Glama
kpanuragh

Xdebug MCP Server

by kpanuragh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Xdebug MCP Server

No user-submitted related servers found.

    Related Servers

    • smart-xdebug-mcp

      wallter
      A
      license
      A
      quality
      D
      maintenance
      Connects AI assistants like Claude to PHP's XDebug debugger for runtime inspection, breakpoint control, and variable tracking, enabling natural language debugging of PHP applications.
      6
      1
      Apache 2.0

    • MCP Debugger

      debugmcp
      A
      license
      C
      quality
      A
      maintenance
      Enables AI agents to perform step-through debugging of Python, JavaScript/Node.js, and Rust programs using the Debug Adapter Protocol, with support for breakpoints, variable inspection, and stack traces.
      21
      166
      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
      9 npm
      2
      Apache 2.0
    • DebugMCP by microsoft

      DebugMCPofficial

      microsoft
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to debug code inside VS Code by setting breakpoints, stepping through execution, inspecting variables, and evaluating expressions across multiple languages.
      523
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.1/5.0

    Scored across 46 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, but there is some overlap in the variable inspection/evaluation trio (get_variables, get_variable, evaluate) and session termination trio (stop, detach, close_session) where users may need to read carefully to pick the right one. Overall, however, the tool names and descriptions are specific enough to disambiguate.

    Naming Consistency4/5

    The majority of tools follow a consistent verb_noun snake_case pattern (e.g., set_breakpoint, get_variable, add_watch). A few exceptions like continue, detach, evaluate, and stop break the pattern, and there is mild inconsistency between profile vs profiling terminology (start_profiling vs get_profile_stats). These are minor deviations rather than chaotic naming.

    Tool Count2/5

    At 46 tools, the surface is very large and exceeds the point where users can easily hold the toolset in mind. While Xdebug is a feature-rich debugger with many legitimate operations, many of these tools (e.g., separate snapshot/export/profile tools) could be consolidated or exposed as optional sub-commands.

    Completeness4/5

    The tool set covers the main debugging workflow well: sessions, breakpoints, stepping, variables, watches, logpoints, source, profiling, and coverage. There are a few gaps such as no remove_step_filter or delete_debug_profile, but these are edge operations rather than core workflow blockers.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources