Skip to main content
Glama
SLP-DEV1

qwen-dap-mcp

by SLP-DEV1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to qwen-dap-mcp

Related Servers

  • debug-dap-mcp

    FlyDut
    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
    260 npm
    MIT

  • vibe-debug

    illscience
    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

  • DebugPilot

    inkan-tech
    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

  • hostproto-dap-debugpy

    bayleafwalker
    A
    license
    Not graded
    quality
    B
    maintenance
    Enables launching and controlling a debugpy debug session through MCP, including setting breakpoints, stepping, evaluating expressions, and observing debugger state and events.
    MIT

  • VSCode Debug MCP

    primax79
    A
    license
    Not graded
    quality
    B
    maintenance
    Exposes VS Code's Debug Adapter Protocol as MCP tools, enabling AI coding agents to set breakpoints, step through code, inspect variables, and read exceptions in a real debug session.
    GPL 3.0
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

A4.4/5.0

Scored across 14 tools

Disambiguation4/5

Each tool targets a distinct phase of debugging, but debug_this_crash, debug_diagnose_stop, and debug_snapshot overlap in stopped-crash analysis, and debug_find_writer/debug_trace_value are closely related. The detailed usage guidance largely prevents misselection.

Naming Consistency4/5

All tools share the debug_ prefix and most use verb_object forms like compare_runs or find_writer, but noun-style names such as debug_sessions, debug_status, and debug_source_disassembly, plus debug_this_crash/debug_this_hang, break the pattern. The naming is still predictable enough to infer the domain.

Tool Count5/5

14 tools is within the ideal range for a specialized debugging server, with each tool covering a distinct aspect: session management, run control, stopped-state inspection, postmortem analysis, and watch/trace workflows. No tool feels superfluous.

Completeness5/5

The surface provides strong coverage of the DAP debugging lifecycle: session creation/status/disconnect, run-to-stop and continue, snapshot and diagnosis, crash and hang workflows, dump analysis, differential comparison, and value-write tracking. For the evident native crash and hang diagnosis purpose, there are no critical missing operations.

Maintenance

ActivityMaintained
ResponsivenessResponsive

Resources