crash-mcp
Related Servers
Alternatives to crash-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to analyze Windows crash dumps by providing structured data on exceptions, threads, modules, and source context, with safe patch, build, and test execution.5MIT
- AlicenseBqualityDmaintenanceEnables AI assistants to analyze Linux system crash dumps by automatically discovering dump files, matching kernels, and executing interactive crash analysis commands through the MCP protocol.67MIT
- AlicenseNot gradedqualityDmaintenanceAnalyzes application crash dumps and extracts debug symbols, transforming Windows minidump files into readable stack traces and providing AI-powered crash analysis to help identify root causes and fix critical issues.8MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding assistants to drive live WinDbg/WinDbgX debugging sessions, including crash dump triage, live process attach, kernel debugging, multi-session management, and unrestricted debugger command execution with advanced reverse-engineering analysis tools.1MIT
- AlicenseNot gradedqualityNot gradedmaintenanceBridges AI models with WinDbg to analyze Windows crash dumps and perform remote debugging through natural language queries, enabling execution of debugger commands and automated crash analysis.MIT
- AlicenseNot gradedqualityAmaintenanceBridges AI models with WinDbg for crash dump analysis and remote debugging.435 PyPI1,669MIT
TDQS
Scored across 6 tools
Each tool maps to a distinct action in a clear pipeline: load the dump, summarize it, enumerate threads, unwind a stack, disassemble at an address, and compare two dumps. Descriptions explicitly sequence the tools (load first, stack after threads), so there is no realistic misselection between them.
All six tools use the same crash_ prefix followed by a short lowercase noun/verb token (load, summary, threads, stack, disassemble, compare). The pattern is uniform and predictable, making the set easy to scan.
Six tools is a tight, well-scoped surface for crash dump triage; every tool has a distinct job and none appear redundant. Nothing feels padded or arbitrarily split.
The core workflow (load → summary → threads → stack → disassemble → compare) is fully covered, including pagination and graceful error reporting. However, there is no register inspection, module listing, or memory/string search tool, which are common needs in crash analysis and would force workarounds.