io.github.spk-c由 GitHub 账号 spk-c 发布v0.19.4更新于 Nov 3, 2026
通过 GDB、LLDB 和 MCP 为 Claude Code、Codex 和 Qwen 提供 C/C++ 崩溃、挂起和转储调试
AI 翻译由 AI 模型根据下方的原文描述翻译，可能有误。
C/C++ crash, hang and dump debugging for Claude Code, Codex and Qwen via GDB, LLDB and MCP
发布方自己的服务：Claude Platform Docs
Qwen DAP MCP — C/C++ Debugger for Claude Code, Codex & Qwen 的本地 MCP 服务；无需登录；STDIO；18 个工具。
暂无 AI 概览：以下信息来自注册中心条目和服务本身。
Desktop only，通过 STDIO。 STDIO 服务会启动本地进程，因此需要 SourceWeft 桌面宿主。
参照 仓库 中的启动说明。
Debug native C/C++ crashes, hangs, deadlocks, Windows minidumps and core dumps with Claude Code, OpenAI Codex CLI, Qwen Code, Gemini CLI and other local MCP-compatible coding agents. Connect a real GDB, LLDB or CodeLLDB debugger through the Debug Adapter Protocol (DAP) and Model Context Protocol (MCP).
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.
Originally designed for Qwen Code, but usable from other local stdio MCP clients including Claude Code and Codex CLI. The AI model may run in the cloud; the debugger bridge and target binary still run where the MCP process is started.
[npm version] [CI] [License] [Node] [GitHub stars]
Quick start · Capabilities · Debugger support · Safety · Docs · Contributing
Maintained Apache-2.0 fork of the original project by SLP-DEV1. The maintained source is spk-c/Qwen-dap-mcp; npm distributes
@slp-dev1/qwen-dap-mcp. GitHub'smainmay be ahead of the latest published npm version. See fork notes and TypeScript migration status.
Illustrated architecture/workflow, not a captured AI session or fabricated debugger transcript. Reproduce an actual intentional crash in the project's own C++ fixture, collect a GDB backtrace, apply an illustrative change only in a temporary copy, and rerun the same command:
Requires Linux, g++ and gdb. CI also executes the demo with a real debugger. View step-by-step verified demo and Claude/Codex MCP setup.
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:
Install the current published npm version:
Or install the newest code directly from the maintained GitHub repository (this can be ahead of npm):
In Qwen Code, run /mcp and /skills to check that the qwen-dap-mcp server and the native-runtime-debug skill were discovered.
Prerequisites: Node.js 20+, and a supported native DAP debugger installed separately (CodeLLDB, LLVM lldb-dap, or GNU GDB DAP). This package is a bridge, not a bundled debugger. See platform setup.
Use a local Claude Code CLI with Node.js 20+ and an installed native DAP debugger:
See Claude Code native debugging guide for a setup check, test prompt, Windows notes and safety boundaries.
See Codex CLI + IDE debugging guide and versioned Codex TOML configuration.
Use a local stdio MCP entry pointing to npx -y @slp-dev1/qwen-dap-mcp. These clients have different configuration schemas: Gemini CLI and Cursor use mcpServers, while VS Code's .vscode/mcp.json uses servers. See multi-client setup and compatibility matrix and the tested configuration examples.
Cloud execution boundary: Claude Code or Codex CLI may call a cloud AI model while the CLI and debugger remain on your desktop. A browser-only Claude.ai/ChatGPT session or a remote Codex task cannot automatically access your PC's local stdio MCP server or Windows processes. Remote debugging requires separately authorized local execution or a protected connection; never expose a raw debugger port to the public internet.
Run the published package with npx:
Configure a trusted local MCP client with:
When started without --help or --version, the CLI operates as a local stdio MCP server. Client configuration syntax may vary.
Update the npm-backed Qwen extension using the extension manager in your installed Qwen Code version, or reinstall the package with the command above. For npx, restart the MCP client to use newly resolved versions. npm releases are immutable: README changes appear on npmjs.com only after publishing a new package version, not when GitHub's README changes.
The project includes automatic protocol-level stdio initialize + tools/list smoke tests with Claude Code, Codex CLI and Gemini client identities. These prove the shared MCP server protocol and example configuration consistency, not full end-to-end verification inside proprietary client applications. Native debugger E2E checks run separately. Run npm run test:clients from a built checkout.
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.
The default agent toolset intentionally exposes 18 core tools so coding models spend less context and selection effort on rarely needed forensic workflows.
Set QWEN_DAP_MCP_TOOLSET=forensics when deeper investigation is needed. It keeps the raw manual DAP surface hidden while adding:
Set QWEN_DAP_MCP_TOOLSET=full only when raw stacks/scopes/variables, manual breakpoints/watchpoints, evaluate, memory reads, stepping, or adapter-specific controls are intentionally required. See docs/toolsets.md.
Adapter discovery, prerequisites, and platform-specific setup are documented in docs/README.md.
Raw DAP is intentionally low level. qwen-dap-mcp keeps raw debugger access available in the full toolset, but its default surface focuses on workflows an agent can reason about directly.
A debugger can execute and mutate target state, so the bridge treats that power explicitly.
Read the full policy and threat model in docs/hol-guard.md and SECURITY.md.
The repository includes native crash, hang, postmortem, Windows minidump, and remote-debugger fixtures. On a development checkout:
The checks include source/build integrity, MCP tests, document consistency, and inspection of the actual npm tarball. Native adapter end-to-end tests run in dedicated CI jobs and require their debugger/toolchain prerequisites. See the integration tests and the benchmark harness; no performance claims are made without recorded, reproducible results.
These focused tutorials describe setup, expected debugger evidence and limitations with real native targets; the MCP bridge does not bundle a debugger.
The maintained package publishes its MCP metadata under io.github.spk-c/qwen-dap-mcp when a matching npm version and official registry publication succeed. This is separate from any historical registry listing for the original author. See publishing and registry verification; a listing is not proof of a particular feature until its exact package version is verified.
Discover the maintained fork: Official MCP Registry · npm · Source and checksums · Directory-ready listing and attribution.
Start with the documentation index.
Requirements: Node.js 20+.
src/**/*.ts is the source of truth for 51 runtime modules; generated JavaScript mirrors and declarations are checked by CI. The full TypeScript strict: true migration is complete (issue #24, PRs #52–#56). CI enforces zero strict compiler diagnostics; native debugger support remains limited to the adapters and scenarios tested in CI.
See CONTRIBUTING.md before opening a pull request.
@slp-dev1/qwen-dap-mcp — installable published versions; verify the npm version before assuming a GitHub change is included.spk-c/Qwen-dap-mcp — qwen extensions install spk-c/Qwen-dap-mcp.vX.Y.Z tag on a verified main commit or by manual workflow dispatch; npm Trusted Publishing uses GitHub Actions OIDC without a long-lived npm publication token.The npm listing is updated from the README inside the published tarball. The GitHub README and npm README can temporarily differ until the next release.
Bug reports, reproducible native failure cases, adapter compatibility findings, documentation fixes, and focused feature proposals are welcome. Please keep additions evidence-driven and prefer high-level agent workflows over expanding the default surface with raw debugger commands.
If this project saves you a debugging session, consider starring the repository — it helps other MCP and coding-agent users discover it.
来源：README.md，提交 5a60130
Manage Debug Sessions
Use this tool to list, create, or close isolated DAP sessions before routing other debugger tools with sessionId. Omit sessionId on normal debug tools only when the backward-compatible default session is intended; do not use a global session selector for concurrent work.
actionsessionIdterminateDebuggeeCompare bounded runtime evidence from two existing stopped DAP sessions. Use this for baseline or known-good versus candidate or failing differential debugging after both sessions have reached comparable stops. It compares stack identities, locals, registers, exception state, symbol health, and modules semantically; non-null raw address-only changes are marked unstable rather than causal evidence. Do not use it to launch, resume, or alter either target; prepare both runtime states with the normal lifecycle tools first.
snapshottimeoutMsbaselineSessionId必填candidateSessionId必填Capture Runtime Debug Snapshot
Capture bounded evidence from the current stopped debug state without resuming execution. Use this when an agent needs raw stack, locals, registers, exception details, modules, or nearby instructions; prefer debug_diagnose_stop when you also want ranked crash hypotheses and project-frame selection. This is read-only with respect to the debuggee and returns best-effort evidence plus collection errors for optional data that an adapter cannot provide.
threadIdsessionIdmoduleCountstackLevelsincludeModulesdisassembleAfterdisassembleBeforeincludeDisassemblyincludeExceptionInfomaxVariablesPerScopeDebug Session Status
Inspect debugger lifecycle state, the selected stop, recent DAP events, and bounded adapter stderr without changing target execution. Use this to determine whether a session is initialized, running, stopped, postmortem, exited, or failed before choosing another debug tool; it is diagnostic only and does not resume, launch, attach, or terminate the debuggee.
无需输入参数。
Disconnect Debugger
End the active DAP session and stop its local adapter process. Use this when debugging is finished or the session must be reset; do not call it when more runtime evidence is still needed. With terminateDebuggee=true it may also terminate a live target process, so this operation can destroy the current runtime state and cannot be treated as read-only.
sessionIdterminateDebuggeeRun Until Debug Stop or Exit
Run one live launch or attach through an already initialized DAP adapter until the first stopped, exited, or terminated event. Use this when you need deterministic runtime evidence from a reproduction; do not use it for a postmortem dump or when executing/attaching to the local target is not authorized. Launch mode executes application code and attach mode changes debugger control of an existing process, so normal target side effects may occur before the stop. Returns the request result, terminal/stopped outcome, session status, and a bounded snapshot only when a stopped event is captured.
requestsnapshotsessionIdtimeoutMsbreakpointsconfiguration必填Diagnose Current Debug Stop
Diagnose an already stopped live or postmortem debug session without changing execution state. Use this when a debugger has captured the failure and you want project-frame selection, crash classification, operand/register/variable bindings, call-chain provenance, ranked hypotheses, and a fix/rebuild/reproduce/verify plan; use debug_snapshot instead when only raw evidence is needed. The tool is read-only and returns both the bounded snapshot and the derived diagnosis, including collection limitations when optional debugger evidence is unavailable.
analysisthreadIdsessionIdmoduleCountstackLevelsincludeModulesdisassembleAfterdisassembleBeforeincludeDisassemblyincludeExceptionInfomaxVariablesPerScopeCorrelate Source and Disassembly
Correlate source locations, disassembly, registers, and pointer-like locals for the raw fault frame and the first likely project-controlled frame. Use this for low-level root-cause evidence when a crash is already stopped and instruction/operand provenance matters; prefer debug_diagnose_stop for a broader ranked diagnosis. This is read-only, does not resume the target, and returns frame-selection reasoning, both correlations, operand bindings, and any best-effort collection errors.
analysisthreadIdsessionIdstackLevelsdisassembleAfterdisassembleBeforeDebug This Crash
Preferred high-level native crash workflow. Use mode=current for an already stopped session, dump for read-only postmortem analysis, codelldb to discover CodeLLDB, lldb-dap to discover upstream LLVM lldb-dap, gdb to discover GNU GDB built-in DAP interpreter, or live with an already initialized generic DAP adapter. Do not use codelldb/lldb-dap/gdb/live when executing or attaching to the target is not authorized: those modes can run application code and cause its normal side effects, while current/dump only inspect stopped evidence. workflow.stage selects initial diagnosis, verification against a prior baseline, or the bounded autonomous cycle. Returns runtime evidence, diagnosis, verification/autonomous metadata, and debugger status with deterministic fixed/blocked/budget-exhausted outcomes where applicable.
cwdenvargsmodeprogramrequestanalysisdumpPathsnapshotworkflowsessionIdsourceMap另有 7 个Trace Runtime Causality
Build a bounded consumer-to-writer evidence chain for one suspicious debugger-visible value. Use it after crash or differential evidence identifies a value whose runtime producers matter. It combines the current stopped snapshot with repeated watchpoint writer tracing. Do not use it for frozen dumps or unsafe-to-resume targets, and do not treat an observed writer as automatic proof of root cause.
name必填maxDepthmaxStopssessionIdtimeoutMsProbe Runtime Progress
Sample a live target across short resume/pause intervals to distinguish no observed progress, same-frame execution movement, and probable busy loops. Use it when a process appears hung but a single thread snapshot cannot distinguish blocking from spinning. Do not use it when resuming the target is unsafe; sampling perturbs scheduling and is not proof of application-level progress.
samplesthreadIdsessionIdintervalMsBuild Runtime Debug Report
Create a shareable structured report from the current stopped target with normalized crash fingerprinting, Symbol Doctor status, sanitizer stderr correlation, poison-pattern memory hazard detection, ABI register-to-argument mapping, and recent debugger output. Use it only for evidence-driven triage and issue handoff. Do not treat heuristic poison patterns, ABI mappings, or sanitizer text correlation as standalone proof.
abisessionIdredactPathsincludeOutputTailTrace Object Lifetime
Trace lifetime evidence for one debugger-visible pointer or object handle using the current snapshot, sanitizer/runtime output, bounded forward writer tracing, and optional reverse stepping when supported. Use this for suspected use-after-free, stale ownership, or unexpected pointer replacement. Do not use forward tracing on a frozen dump or when resuming the target is unsafe.
name必填maxStopsdirectionsessionIdtimeoutMsreverseStepsCollect Adaptive Runtime Evidence
Collect runtime evidence in progressively richer bounded phases instead of immediately requesting a maximal snapshot. Use it when token/DAP cost matters or the amount of evidence needed is unknown: it starts with stack and small locals, expands only when symbols, exception state, or variables are insufficient, and finishes with a full runtime report when needed. Do not use it to replace deliberate deep inspection when the required evidence is already known.
forceFullsessionIdmaxVariablesDebug This Hang
High-level native hang workflow for all-thread triage. Use it when a live process appears stuck, deadlocked, waiting forever, or spinning and you need bounded stacks from every thread, wait-state/deadlock heuristics, and cross-thread Pointer-Provenance v2. In current mode it inspects an existing configured session and pauses a running live target when necessary; codelldb, lldb-dap, gdb, and live modes can launch or attach to an authorized local target, observe it for a bounded interval, then pause it for evidence. Do not use executable/attach modes when target execution or debugger control is not authorized, and do not treat a deadlock-candidate as a proven lock cycle because generic DAP does not expose portable lock ownership.
cwdenvpidargsmodeprogramrequestanalysisobserveMssessionIdmaxThreadsadapterPath另有 8 个Find Runtime Writer
Temporarily watch a variable or debugger expression, resume an authorized live target, and capture the first resulting stop to identify the immediate writer candidate. Use this after a stopped-state diagnosis suggests a value was corrupted and runtime provenance is needed; do not use it for crash dumps or when resuming is unsafe. Adapters with DAP data-breakpoint support use that protocol directly; GDB 14/15 uses a bounded watch/rwatch/awatch command through DAP REPL because those releases do not advertise native data breakpoints. The tool removes only the temporary watch it created and never automatically continues through an unrelated stop.
name必填frameIdsnapshotthreadIdconditionsessionIdtimeoutMsaccessTypehitConditionvariablesReferencereplaceExistingDataBreakpointsTrace Runtime Value Writes
Build a bounded temporal write timeline for one debugger-visible variable or expression. Use this after differential or crash evidence identifies a suspicious value and repeated live-target resume is safe. The tool installs one temporary data breakpoint or watchpoint at a time, resumes to the next confirmed writer, captures bounded runtime evidence, removes only its own temporary watch, and repeats. Do not use it for crash dumps, unsafe-to-resume targets, or as proof that an observed writer is the root cause; it stops on unrelated debugger events rather than continuing through them.
name必填maxStopssnapshotthreadIdsessionIdtimeoutMsaccessTypeperStopTimeoutMsOpen Native Crash Dump
Open a local native core/minidump with CodeLLDB, upstream LLVM lldb-dap, or GNU GDB DAP and capture bounded postmortem evidence. Use this when the failure is already recorded and no target process should execute; use debug_run_to_stop or debug_this_crash for a live reproduction instead. The tool starts only the selected local debugger adapter, never launches or resumes the crashed program, treats the dump as read-only, and returns the initial stack/locals/registers plus optional modules and disassembly.
cwdadapterprogramdumpPath必填threadIdsessionIdsourceMapadapterPathmoduleCountstackLevelsincludeModulesrequestTimeoutMs另有 2 个已满足适用检查项的 90%
该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。
请在注册中心条目中声明凭据请求头，或保持端点能够响应探测，以便判定其认证方式。
com.claude.platform官方发布者
远程 MCP 服务器，让助手搜索并阅读 Claude 平台文档与 API 参考。
由 GitHub 账号 faisalkhanzemi 发布
把 Claude Code 连接到 Mac 版 Instagram Edits，同步完整的 274 个工具编辑器，让助手剪辑 Reels。
由 GitHub 账号 daniel-munoz 发布
本地 MCP 服务器，把 Claude Code 会话的工作状态保存为项目内的 JSON 文件，并能还原成简短的续接摘要。
由 GitHub 账号 lemberalla 发布
仅适用于 Claude Code 的本地 AVE 时间线编辑与导出。需要现有 AVE 连接。AI 翻译
由 GitHub 账号 pironjulien 发布
让助手通过 UI Automation 和 Win32 消息在后台操作 Windows 桌面程序，并回读每一次操作的结果。
bash scripts/demo-native-crash.shqwen extensions install @slp-dev1/qwen-dap-mcpqwen extensions install spk-c/Qwen-dap-mcpclaude mcp add --transport stdio --scope user qwen-dap-mcp -- npx -y @slp-dev1/qwen-dap-mcpclaude mcp listcodex mcp add qwen-dap-mcp -- npx -y @slp-dev1/qwen-dap-mcpcodex mcp listnpx -y @slp-dev1/qwen-dap-mcp --helpnpx -y @slp-dev1/qwen-dap-mcp --version{ "mcpServers": { "qwen-dap-mcp": { "command": "npx", "args": ["-y", "@slp-dev1/qwen-dap-mcp"] } }}You: Debug why app.exe crashes with --repro
Coding agent ↓qwen-dap-mcp starts a DAP debugger ↓captures the native failure + project-controlled frame ↓correlates stack + registers + locals + disassembly ↓backtracks runtime evidence toward the likely producer ↓agent applies a minimal source fix ↓builds and repeats the original reproduction ↓verifies whether the original crash fingerprint is gonenpm cinpm run checknpm run check:packgit clone https://github.com/spk-c/Qwen-dap-mcp.gitcd qwen-dap-mcpnpm cinpm run check