S
svnscha/mcp-windbg
Model Context Protocol for WinDbg
在 GitHub 查看 ↗链接已于 2026-11-12 核查 · HTTP 200 · 打开的是厂商自己的官网
安装与配置
客户端配置（取自该仓库的安装命令）
{
"mcpServers": {
"svnscha-mcp-windbg": {
"command": "uvx",
"args": ["plugin"]
}
}
}解析自我们于 2026-11-07 抓取的该仓库 README；我们未执行过。
command/args 来自仓库写明的安装命令；不确定时请以该项目 README 为准。
VS Code（.vscode/mcp.json —— 键名是 servers）
{
"servers": {
"svnscha-mcp-windbg": {
"command": "uvx",
"args": ["plugin"]
}
}
}VS Code 顶层键是 <code>servers</code>，其余与上面那份相同。
Claude Code（命令行）
claude mcp add --transport stdio svnscha-mcp-windbg -- uvx plugin
Claude Code 不收 JSON 文件，用这条命令直接加。
配置项的键名以你的客户端为准：客户端与 CLI
- 来源明细
- 收录自 abordage/awesome-mcp 榜单（我们从中收集的条目之一） · 条目类型：MCP 服务
- 收录与活跃
- 收录于 2026-11-05 · 最近见到 2026-11-14 · 共见到 10 次 · 被 10 个来源列出
- 评分构成
- 综合分 1,003 · 10 个来源 · mcp
- 安装
uvx plugin
常见问题（答案都来自我们的记录）
怎么安装？
该仓库给出的安装命令是
uvx plugin。我们的记录里它是仓库自己提供的；不保证在你的客户端上直接可用。它适合谁 / 用来做什么？
我们把它归在这些标签下: MCP 服务。标签来自条目自身，不是我们强加的分类。
谁维护它、还在更新吗？
我们收录于 2026-11-05；最近见到 2026-11-14。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。
# MCP Server for WinDbg Crash Analysis
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
A Model Context Protocol server that bridges AI models with WinDbg for crash dump analysis, user-mode remote debugging, and kernel debugging.
> [!TIP]
> Looking for AI debugging built into WinDbg itself? Microsoft now ships an official
> WinDbg MCP, starting with WinDbg 1.2610.1001.0. You enable it in WinDbg's MCP service
> settings, and chat with your active debugging session from VS Code with GitHub Copilot or
> from the GitHub Copilot CLI. If that is what you want, start there:
> - Introducing WinDbg MCP (announcement)
> - Set up WinDbg MCP and the overview
> - Get the latest WinDbg
> This project is an independent, community-built alternative. It runs cdb.exe / kd.exe
> headless, so it fits when you want to use another MCP client, drive a debugger from another machine over HTTP, or script triage across many
> dumps without opening the WinDbg UI.
## Overview
This server drives the Windows debuggers - CDB for user mode (dumps and -remote) and KD for kernel targets (-k) - so you can debug in natural language: "Show me the call stack and explain this access violation" or "Open a kernel session and tell me which driver bugchecked."
It is not a magical auto-fix. It is a Python wrapper around cdb.exe / kd.exe that lets an LLM run real debugger commands and reason about the output.
## Features
Crash dump analysis - open a .dmp/.mdmp/.hdmp and get automated triage (!analyze -v, stacks, modules, threads) in a single call.
User-mode remote debugging - attach to a live cdb/WinDbg debug server (-remote) over TCP, a named pipe, or COM, and break in on demand.
Kernel debugging - attach to a kernel target (-k, driven by kd.exe) over KDNET, a named pipe, or serial; the server waits for the target and breaks in for you.
Run any WinDbg/KD command - drive an open session with arbitrary commands (kb, !process 0 0, !heap, lm, ...) described in natural language.
Session ids - every open returns a session id; several sessions (dumps, remote, kernel) can be open at once and are addressed independently.
Resilient live sessions - per-call timeouts, and a slow live command that outruns its timeout is broken into with CTRL+BREAK and the session resynchronized instead of wedging.
Multi-dump triage - discover and compare many dumps across a directory.
Text filter hooks - a --filter-script can redact PII/secrets from tool arguments and output before they leave the machine.
stdio or HTTP - run locally over stdio, or as a streamable-HTTP service you drive from another machine.
## Use cases
| You have | You want to | Guide |
| A .dmp from a crash or a blue screen | Root-cause it: exception or bugcheck, faulting frame, why it happened | Analyze a crash dump |
| A live user-mode process (via cdb -server) | Break in and inspect a hang or live state | Debug a remote target |
| A KD-enabled machine or VM | Debug drivers, bugchecks, and boot-time issues | Debug a kernel target |
| A folder full of dumps | Triage the batch and find the common signature | Triage multiple dumps |
| A debugging host, but you work elsewhere | Drive it over HTTP from another machine | Debug from another machine |
| Dumps with secrets or PII | Scrub tool output before it leaves the box | Redact sensitive data |
> [!TIP]
> Looking for AI debugging built into WinDbg itself? Microsoft now ships an official
> WinDbg MCP, starting with WinDbg 1.2610.1001.0. You enable it in WinDbg's MCP service
> settings, and chat with your active debugging session from VS Code with GitHub Copilot or
> from the GitHub Copilot CLI. If that is what you want, start there:
> - Introducing WinDbg MCP (announcement)
> - Set up WinDbg MCP and the overview
> - Get the latest WinDbg
> This project is an independent, community-built alternative. It runs cdb.exe / kd.exe
> headless, so it fits when you want to use another MCP client, drive a debugger from another machine over HTTP, or script triage across many
> dumps without opening the WinDbg UI.
## Overview
This server drives the Windows debuggers - CDB for user mode (dumps and -remote) and KD for kernel targets (-k) - so you can debug in natural language: "Show me the call stack and explain this access violation" or "Open a kernel session and tell me which driver bugchecked."
It is not a magical auto-fix. It is a Python wrapper around cdb.exe / kd.exe that lets an LLM run real debugger commands and reason about the output.
## Features
Crash dump analysis - open a .dmp/.mdmp/.hdmp and get automated triage (!analyze -v, stacks, modules, threads) in a single call.
User-mode remote debugging - attach to a live cdb/WinDbg debug server (-remote) over TCP, a named pipe, or COM, and break in on demand.
Kernel debugging - attach to a kernel target (-k, driven by kd.exe) over KDNET, a named pipe, or serial; the server waits for the target and breaks in for you.
Run any WinDbg/KD command - drive an open session with arbitrary commands (kb, !process 0 0, !heap, lm, ...) described in natural language.
Session ids - every open returns a session id; several sessions (dumps, remote, kernel) can be open at once and are addressed independently.
Resilient live sessions - per-call timeouts, and a slow live command that outruns its timeout is broken into with CTRL+BREAK and the session resynchronized instead of wedging.
Multi-dump triage - discover and compare many dumps across a directory.
Text filter hooks - a --filter-script can redact PII/secrets from tool arguments and output before they leave the machine.
stdio or HTTP - run locally over stdio, or as a streamable-HTTP service you drive from another machine.
## Use cases
| You have | You want to | Guide |
| A .dmp from a crash or a blue screen | Root-cause it: exception or bugcheck, faulting frame, why it happened | Analyze a crash dump |
| A live user-mode process (via cdb -server) | Break in and inspect a hang or live state | Debug a remote target |
| A KD-enabled machine or VM | Debug drivers, bugchecks, and boot-time issues | Debug a kernel target |
| A folder full of dumps | Triage the batch and find the common signature | Triage multiple dumps |
| A debugging host, but you work elsewhere | Drive it over HTTP from another machine | Debug from another machine |
| Dumps with secrets or PII | Scrub tool output before it leaves the box | Redact sensitive data |
收录徽章（可选）
想把收录标记放进 README 就复制这行，可选，不影响收录。
[](https://anclum.com/zh/s/svnscha-mcp-windbg/)
- 来源
- awesome · https://github.com/svnscha/mcp-windbg
- 按领域浏览
- MCP 服务
- 收录来源
- 10 个独立来源
- 收录于
- 今天
同类推荐
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。