Qwen DAP MCP

Bridges a native debugger (DAP) to MCP so an assistant can diagnose crashes, hangs, dumps, and runtime state in compiled programs.

What you can do

A local Debug Adapter Protocol to MCP bridge that exposes debugger evidence to coding agents. Its default agent toolset has 18 tools, including debug_this_crash, debug_this_hang, debug_compare_runs, debug_trace_value, debug_causal_trace, debug_progress_probe, debug_runtime_report, debug_open_dump, and debug_snapshot. Optional forensics and full toolsets add reverse execution, crash clustering, symbol diagnosis, dump batch analysis, and raw DAP controls. It supports CodeLLDB, LLVM lldb-dap, and GNU GDB 14+ DAP adapters, including remote gdbserver attach and postmortem dump inspection.

When to use it

Use it when a coding agent needs runtime evidence that source reading cannot provide: native crashes, hangs or deadlocks, crash dumps, suspicious values, good-versus-bad run comparison, or bounded fix-and-verify loops. It is aimed at native debugging workflows rather than general shell or file access.

Requirements

Runs locally over stdio, typically via npx @slp-dev1/qwen-dap-mcp. Node.js 20+ is required. A supported debug adapter (CodeLLDB, lldb-dap, or GDB 14+ DAP) and its prerequisites must be installed and discoverable. Optional environment variables select toolsets and child debugging. Remote targets need validated gdbserver or lldb-server endpoints.