About Qwen DAP MCP
Qwen DAP MCP bridges native debuggers to MCP for coding agents, exposing runtime evidence and bounded diagnostic workflows for crashes, hangs, and dumps. It keeps raw debugger controls in opt-in toolsets.
Key features
- 01Diagnose native crashes and hangs
- 02Compare runtime sessions and trace values
- 03Inspect crash dumps and remote targets
- 04Collect structured debugger evidence
- 05Separate core, forensic, and raw toolsets
Use cases
- 01Trace a native crash to project frames
- 02Triage a hang using thread stacks
- 03Compare a failing run with a baseline
- 04Analyze crash dumps without launching a program
MCP support
The server bridges Debug Adapter Protocol (DAP) to MCP over stdio and exposes agent-oriented debugger tools. It supports local adapters and validated remote targets.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
18Saved tool list · updated 2w ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| action | enum | No | Management action: list current sessions, create a new isolated session, or close one session.list | create | close |
| sessionId | string | No | Requested ID for create, or target ID for close. Omit on create to generate a bounded session-N identifier. |
| terminateDebuggee | boolean | No | For close only: request debugger termination of the live target before resetting/removing the session. |
Details
The maintainer has not added details yet. Check the README in the repository.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.