Crash MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CRASH_SEARCH_PATH | No | The search path for crash dump files | /var/crash |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_crash_dumpsB | Scans for crash dumps in the specified directory (recursive). |
| start_sessionC | Starts analysis session. Requires vmcore and vmlinux paths. Returns session ID. |
| run_crash_commandC | Runs crash utility command (e.g., sys, bt, log, ps, files, vm, kmem). |
| run_drgn_commandC | Runs drgn Python code (e.g., prog.crashed_thread(), prog['variable']). |
| stop_sessionB | Terminates an active session. |
| get_sys_infoB | Convenience tool to get system info (runs 'sys' command). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose with no overlap: get_sys_info retrieves system info, list_crash_dumps scans for dumps, run_crash_command runs crash utility commands, run_drgn_command runs drgn Python code, start_session initiates analysis, and stop_session terminates it. The descriptions make it easy to differentiate between them.
All tool names follow a consistent verb_noun pattern (e.g., get_sys_info, list_crash_dumps, run_crash_command, run_drgn_command, start_session, stop_session). This uniformity makes the tool set predictable and easy to understand.
With 6 tools, the server is well-scoped for crash analysis, covering essential operations like scanning dumps, running commands, managing sessions, and retrieving system info. Each tool earns its place without being excessive or insufficient.
The tool set provides strong coverage for crash analysis, including session management, command execution, and dump scanning. A minor gap exists in lacking tools for more advanced or specific analysis tasks, but core workflows are well-supported.