Skip to main content
Glama
spk-c
by spk-c

Related Servers

Alternatives to qwen-dap-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      Enables coding agents to connect to Debug Adapter Protocol debuggers over MCP, allowing them to launch or attach to native targets, control execution, set breakpoints and watchpoints, inspect stacks, variables, memory, and exceptions, and capture agent-friendly debugger snapshots.
      18
      266 npm
      3
      Apache 2.0
    • A
      license
      A
      quality
      B
      maintenance
      Enables any MCP client to debug programs through the Debug Adapter Protocol, supporting launch/attach, breakpoints, stepping, variable inspection, evaluation, and memory operations via a single debug tool.
      1
      13 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables step-through debugging for C#, Node.js/TypeScript, Python, and Dart applications on Windows through a unified MCP interface. Acts as a bridge between MCP clients and various debug adapters, providing consistent debugging workflows with breakpoints, variable inspection, and process attachment capabilities.
      12 npm
      ISC
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables coding agents to use a real debugger (Python via debugpy) for launching, attaching, setting breakpoints, stepping through code, inspecting stack frames, and evaluating expressions through MCP tools.
      27
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to inspect debug state, control execution, and set breakpoints in VS Code by exposing the Debug Adapter Protocol as an MCP server.
      Apache 2.0
    • A
      license
      A
      quality
      C
      maintenance
      Enables native Windows x64 debugging from MCP clients, including launching or attaching to processes, managing breakpoints, stepping, inspecting call stacks and expressions, and opening crash dumps without requiring Unreal Editor or plugins.
      20
      MIT

    TDQS

    A4.1/5.0

    Scored across 18 tools

    Disambiguation3/5

    The lifecycle tools are distinct, but the evidence tools overlap heavily: debug_snapshot, debug_diagnose_stop, debug_source_disassembly, debug_adaptive_evidence, and debug_runtime_report all inspect a stopped session with different levels of derivation. The descriptions help by stating when to prefer each, but an agent can still struggle to choose among them.

    Naming Consistency5/5

    Every tool uses the same debug_ snake_case prefix with descriptive noun/verb phrases. The convention is highly predictable across lifecycle, evidence, tracing, and workflow tools.

    Tool Count3/5

    Eighteen tools is heavy for an agent-facing server, and several evidence/reporting tools could plausibly be consolidated into fewer parameterized operations. The debugger domain is broad, so the count is not absurd, but it is borderline over-scoped.

    Completeness3/5

    The set covers crash, hang, postmortem, differential, and tracing workflows well, but it lacks explicit general breakpoint management, stepping operations, expression evaluation, and thread listing that agents often expect from a DAP debugger. These are notable gaps, though some workflows partially compensate through run-to-stop and temporary watchpoints.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive