一款模型上下文协议服务器，连接 AI 模型与 WinDbg，用于崩溃转储分析、用户模式远程调试和内核调试。

[!提示] 想找内置在WinDbg中的AI调试功能？ Microsoft现在官方发布了 WinDbg MCP，从 WinDbg 1.2610.1001.0 开始。你可以在 WinDbg 的 MCP 服务中启用它 设置，然后用 GitHub Copilot 和你正在调试的 VS Code 会话聊天，或者 来自 GitHub Copilot 的 CLI。如果你想要这个，就从这里开始：

• 介绍 WinDbg MCP（公告）
• 设置WinDbg MCP及其概述
• 获取最新的WinDbg

这个项目是一个独立的社区构建替代方案。运行时间为 cdb.exe / kd.exe 无头的，所以当你想用另一个MCP客户端、通过HTTP从另一台机器驱动调试器，或者跨多台脚本进行分流时，它很合适 在不打开WinDbg界面的情况下导出。

概述

该服务器驱动 Windows 调试器——CDB 用于用户模式（转储和 -remote）和 KD 用于内核目标（[-k）——所以你可以用自然语言调试：“给我看调用栈并解释此访问违规” 或 “打开内核会话告诉我哪个驱动被检查了错误。”

MCP Server for WinDbg Crash Analysis

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.