crash-mcp
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@crash-mcpanalyze and optimize my database query step-by-step"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Installation
npm install crash-mcpOr use directly with npx:
npx crash-mcpQuick Setup
Most MCP clients use this JSON configuration:
{
"mcpServers": {
"crash": {
"command": "npx",
"args": ["-y", "crash-mcp"]
}
}
}Configuration by Client
Client | Setup Method |
Claude Code |
|
Cursor | Add to |
VS Code | Add to settings JSON under |
Claude Desktop | Add to |
Windsurf | Add to MCP config file |
JetBrains | Settings > Tools > AI Assistant > MCP |
Others | Use standard MCP JSON config above |
Use the cmd wrapper:
{
"mcpServers": {
"crash": {
"command": "cmd",
"args": ["/c", "npx", "-y", "crash-mcp"]
}
}
}{
"mcpServers": {
"crash": {
"command": "npx",
"args": ["-y", "crash-mcp"],
"env": {
"CRASH_STRICT_MODE": "false",
"MAX_HISTORY_SIZE": "100",
"CRASH_OUTPUT_FORMAT": "console",
"CRASH_SESSION_TIMEOUT": "60",
"CRASH_MAX_BRANCH_DEPTH": "5"
}
}
}
}FROM node:18-alpine
WORKDIR /app
RUN npm install -g crash-mcp
CMD ["crash-mcp"]{
"mcpServers": {
"crash": {
"command": "docker",
"args": ["run", "-i", "--rm", "crash-mcp"]
}
}
}Bun:
{ "command": "bunx", "args": ["-y", "crash-mcp"] }Deno:
{
"command": "deno",
"args": ["run", "--allow-env", "--allow-net", "npm:crash-mcp"]
}Related MCP server: Sequential Thinking MCP Server
Configuration
Variable | Default | Description |
|
| Enable strict validation (requires specific prefixes) |
|
| Maximum steps to retain in history |
|
| Output format: |
|
| Disable colored console output |
|
| Session timeout in minutes |
|
| Maximum branch nesting depth |
|
| Enable session management |
Usage
Required Parameters
Parameter | Type | Description |
| integer | Sequential step number (starts at 1) |
| integer | Estimated total steps (adjustable) |
| string | Step category: analysis, action, validation, exploration, hypothesis, correction, planning, or custom |
| string | What's already known to avoid redundancy |
| string | Current reasoning process |
| string | Expected or actual result |
| string/object | Next action (simple string or structured with tool details) |
| string | Why this next action was chosen |
Optional Parameters
Parameter | Type | Description |
| boolean | Mark as final step to complete reasoning |
| number | Confidence level 0-1 (warnings below 0.5) |
| string | Describe doubts or assumptions |
| integer | Step number being corrected |
| string | Why revision is needed |
| integer | Step to branch from |
| string | Unique branch identifier |
| string | Human-readable branch name |
| integer[] | Step numbers this depends on |
| string | Group related reasoning chains |
| string[] | Tools used in this step |
| object | External data relevant to step |
Examples
Basic Usage
{
"step_number": 1,
"estimated_total": 3,
"purpose": "analysis",
"context": "User requested optimization of database queries",
"thought": "I need to first understand the current query patterns before proposing changes",
"outcome": "Identified slow queries for optimization",
"next_action": "analyze query execution plans",
"rationale": "Understanding execution plans will reveal bottlenecks"
}With Confidence and Final Step
{
"step_number": 3,
"estimated_total": 3,
"purpose": "summary",
"context": "Analyzed queries and tested index optimizations",
"thought": "The index on user_id reduced query time from 2s to 50ms",
"outcome": "Performance issue resolved with new index",
"next_action": "document the change",
"rationale": "Team should know about the optimization",
"confidence": 0.9,
"is_final_step": true
}Revision Example
{
"step_number": 4,
"estimated_total": 5,
"purpose": "correction",
"context": "Previous analysis missed a critical join condition",
"thought": "The join was causing a cartesian product, not the index",
"outcome": "Corrected root cause identification",
"next_action": "fix the join condition",
"rationale": "This is the actual performance issue",
"revises_step": 2,
"revision_reason": "Overlooked critical join in initial analysis"
}Branching Example
{
"step_number": 3,
"estimated_total": 6,
"purpose": "exploration",
"context": "Two optimization approaches identified",
"thought": "Exploring the indexing approach first as it's lower risk",
"outcome": "Branch created for index optimization testing",
"next_action": "test index performance",
"rationale": "This approach has lower risk than query rewrite",
"branch_from": 2,
"branch_id": "index-optimization",
"branch_name": "Index-based optimization"
}When to Use CRASH
Good fit:
Complex multi-step problem solving
Code analysis and optimization
System design with multiple considerations
Debugging requiring systematic investigation
Exploring multiple solution paths
Tasks where you need to track confidence
Not needed:
Simple, single-step tasks
Pure information retrieval
Deterministic procedures with no uncertainty
Development
npm install # Install dependencies
npm run build # Build TypeScript
npm run dev # Run with MCP inspector
npm start # Start built serverTroubleshooting
Try using bunx instead of npx:
{ "command": "bunx", "args": ["-y", "crash-mcp"] }Try the experimental VM modules flag:
{ "args": ["-y", "--node-options=--experimental-vm-modules", "crash-mcp"] }Credits
MCP Sequential Thinking Server - Primary inspiration
Author
Nikko Gonzales - nikkoxgonzales
License
MIT
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/AbdulAziz001/mcp-local'
If you have feedback or need assistance with the MCP directory API, please join our Discord server