Skip to main content
Glama
wallter

smart-xdebug-mcp

by wallter

Related Servers

Alternatives to smart-xdebug-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      A
      maintenance
      Enables AI assistants to debug PHP applications through Xdebug's DBGp protocol, providing full debugging control including breakpoints, variable inspection, stack traces, and advanced features like watch expressions and code coverage.
      46
      283 npm
      27
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to deeply interact with the PHP ecosystem, including runtime, static analysis, security scanning, testing, Composer, and frameworks like Laravel and Symfony. It exposes over 30 tools, 8 resources, and 7 prompts via MCP, allowing natural language commands to run PHP linting, static analysis, audits, tests, and project initialization.
      41
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Connects the x32dbg debugger to Claude AI through the Model Context Protocol, enabling natural language control of 48+ debugging operations such as breakpoints, memory analysis, and reverse engineering automation.
      11
      -
    • 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
    • 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.
      539
      MIT

    TDQS

    A4.8/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a unique, non-overlapping purpose: session start, breakpoint setting, variable inspection, execution control, status checking, and history querying. No ambiguity between them.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern (e.g., start_debug_session, set_breakpoint), making them predictable and easy to understand.

    Tool Count5/5

    With 6 tools, the set is well-scoped for a debugging server. Each tool is essential, covering the full debugging workflow without unnecessary bloat or shortage.

    Completeness4/5

    The tool set covers the core debugging lifecycle: start, breakpoints, inspect, control, status, and history. Minor gap is the lack of a tool to remove individual breakpoints without ending the session, but the set is otherwise complete.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues