SLP-DEV1/qwen-dap-mcp

**Give coding agents a real native debugger.**
qwen-dap-mcp is a local **Debug Adapter Protocol (DAP) → Model Context Protocol (MCP)** bridge for native crash debugging, hang/deadlock triage, crash dumps, differential runtime analysis, remote targets, and bounded fix/verify workflows.
Built for **Qwen Code**, usable from any stdio MCP client, and designed to expose debugger evidence without turning MCP into a general-purpose shell.
**Quick start · Capabilities · Debugger support · Safety · Docs · Contributing**
Why this exists
Coding agents can read source and propose patches, but native failures often cannot be diagnosed reliably from source alone. The useful evidence lives at runtime: thread stacks, registers, locals, disassembly, exception state, modules, memory, wait states, symbols, and crash dumps.
qwen-dap-mcp makes that evidence available through MCP and adds agent-oriented workflows on top of raw debugger primitives:
- **Evidence first** — inspect the actual failing process instead of guessing from source.
- **High-level workflows** — crash, hang, differential, causal tracing, progress probing, runtime-report, dump, and verification tools are designed for agents rather than humans driving a debugger console.
- **Bounded automation** — autonomous fix/verify state is explicit, serializable, iteration-limited, and re-checks the original reproduction.
- **Small default surface** — 18 core agent tools stay visible by default; forensic workflows and raw DAP controls are separate opt-in tiers.
- **Local by default** — the MCP server communicates over stdio and debugger adapters run locally unless you explicitly configure a validated remote target.
Quick start
Qwen Code
Install directly from GitHub:
Or install the published npm package:
Then verify the extension:
You should see the qwen-dap-mcp server and the bundled native-runtime-debug skill.
Any stdio MCP client
Typical configuration:
CLI discovery is available without starting the stdio server:
30-second example
The MCP server supplies debugger evidence and bounded workflow state. Source editing, builds, tests, and source-control operations stay with the coding agent's normal authorized tools.
What it does
| Problem | Agent-oriented capability |
| --- | --- |
| Native crash | Diagnose a stopped process, identify project frames, collect runtime evidence, and drive bounded fix/verify loops |
| Hang or deadlock | Observe, pause when needed, capture all-thread stacks, classify waits, and surface conservative deadlock candidates |
| Good run vs bad run | Compare stopped sessions semantically while suppressing raw ASLR/address noise |
| Suspicious value | Trace real writers with data breakpoints/watchpoints and bounded temporal tracing |
| Runtime causality | Build a bounded suspicious-value consumer → writer/producer chain with debug_causal_trace |
| Suspected busy loop | Resume/pause sample a live target with debug_progress_probe to distinguish repeated state from observed execution movement |
| Record/replay target | Move backward with capability-gated debug_reverse_execution using DAP stepBack / reverseContinue |
| Crash fleet triage | Build debug_runtime_report fingerprints, cluster them with debug_cluster_crashes, and classify regression reproductions with debug_regression_oracle |
| Child/fork signal | Inspect fail-closed adapter startDebugging requests with debug_child_requests without auto-spawning child sessions |
| Crash dump | Inspect Windows minidumps and supported LLDB/GDB postmortem targets without launching the failed program |
| Remote native target | Attach through validated gdbserver / lldb-server gdbserver endpoints with loopback-first policy |
| Multiple targets | Keep isolated DAP sessions and route requests by sessionId |
| Agent safety | Keep the default surface high-level and optionally gate executable/mutating DAP actions with HOL Guard |