I've just released version 0.12.2 of mcp-windbg, bringing some significant enhancements that expand how and where you can perform crash dump analysis.
What's New
This release introduces two major features that address the flexibility and deployment needs many of you have been asking about.
First up is support for the Prompts API, which fundamentally changes how you can interact with crash dump analysis. Rather than being tied to a local setup, you can now trigger triage analysis from anywhere in your environment. The server can be deployed on any machine in your network, whether that's a dedicated analysis box, a build server, or even directly on a file server hosting your crash dumps. This means you can centralize your debugging infrastructure and access it from wherever you're working.
Second, this release adds streamable-http as an alternative transport backend. This gives you more options for how the server communicates, particularly useful in containerized or networked environments where different transport mechanisms might be preferable.
The combination of these features means you can now set up a centralized crash analysis service that developers across your team can leverage without needing to install WinDbg or configure everything locally. Want to analyze dumps directly on the file server where they're stored? Now you can.
Getting Started
If you want to try out the latest version, installation is straightforward:
The project is open source and available on GitHub at https://github.com/svnscha/mcp-windbg. If you find it useful, a star on the repository is always appreciated.
A Real-World Example
No release post would be complete without putting the tool to work on an actual crash dump. Here's an example of the analysis in action:
Even Copilot needs a debugger sometimes.