← Back to directory
C

CRASH

Community
An MCP server for structured, iterative reasoning with step tracking, branching, and revisions.
GitHub source repository ↗
★ 72 Stars Category · Dev Tools Popular Source revision b74f5ce91e21
60FMRS · C
Reliability
10/20
Security and permissions
8/20
Maintenance
14/20
Documentation
15/20
Setup experience
13/20

CRASH provides a valuable tool for structured reasoning, especially for complex problems. It is more concise than sequential thinking but may not be needed for simple tasks.

Read the FMRS scoring method →

CRASH (Cascaded Reasoning with Adaptive Step Handling) is an MCP server for structured, iterative reasoning. It helps AI assistants break down complex problems into trackable steps with confidence tracking, revision support, and branching for exploring alternatives. Inspired by the MCP Sequential Thinking Server, it is more token-efficient and streamlined.

Tools

handle_step
Processes a single reasoning step with parameters like step number, purpose, thought, outcome, next action, and rationale, plus optional confidence, revision, branching, and dependencies.

Setup

Install via npm: npm install crash-mcp. Or run directly with npx: npx crash-mcp. For most MCP clients, add the JSON config: {"mcpServers":{"crash":{"command":"npx","args":["-y","crash-mcp"]}}}. See README for client-specific setup.

claude_desktop_config.json
{
  "mcpServers": {
    "crash": {
      "command": "npx",
      "args": [
        "-y",
        "crash-mcp"
      ]
    }
  }
}

Fit and risk

Best for

  • Complex tasks that require structured reasoning
  • Scenarios needing step validation and revisions
  • Exploring multiple solution paths

Not for

  • Simple single-step tasks
  • Pure information retrieval
  • Deterministic procedures with no uncertainty

Required permissions

  • Network access to fetch package via npx
  • File system access for config files (client-dependent)

Risks and side effects

  • Package may be unvetted (community project)
  • Misconfiguration can cause startup failures
  • Environment variables not set correctly may lead to unexpected behavior

Troubleshooting

  1. Module not found errors: try using bunx instead of npx
  2. ESM resolution issues: try --node-options=--experimental-vm-modules flag
  3. Check environment variables like CRASH_STRICT_MODE and CRASH_OUTPUT_FORMAT are set correctly

Use cases

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

Supported clients

Claude DesktopFull support
Claude CodeFull support
CursorFull support
VS CodeFull support
WindsurfFull support
JetBrainsFull support