Skip to main content
Glama
crash-mcp

crash-mcp

by AbdulAziz001

Installation

npm install crash-mcp

Or use directly with npx:

npx crash-mcp

Quick Setup

Most MCP clients use this JSON configuration:

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

Configuration by Client

Client

Setup Method

Claude Code

claude mcp add crash -- npx -y crash-mcp

Cursor

Add to ~/.cursor/mcp.json

VS Code

Add to settings JSON under mcp.servers

Claude Desktop

Add to claude_desktop_config.json

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

Configuration

Variable

Default

Description

CRASH_STRICT_MODE

false

Enable strict validation (requires specific prefixes)

MAX_HISTORY_SIZE

100

Maximum steps to retain in history

CRASH_OUTPUT_FORMAT

console

Output format: console, json, markdown

CRASH_NO_COLOR

false

Disable colored console output

CRASH_SESSION_TIMEOUT

60

Session timeout in minutes

CRASH_MAX_BRANCH_DEPTH

5

Maximum branch nesting depth

CRASH_ENABLE_SESSIONS

false

Enable session management


Usage

Required Parameters

Parameter

Type

Description

step_number

integer

Sequential step number (starts at 1)

estimated_total

integer

Estimated total steps (adjustable)

purpose

string

Step category: analysis, action, validation, exploration, hypothesis, correction, planning, or custom

context

string

What's already known to avoid redundancy

thought

string

Current reasoning process

outcome

string

Expected or actual result

next_action

string/object

Next action (simple string or structured with tool details)

rationale

string

Why this next action was chosen

Optional Parameters

Parameter

Type

Description

is_final_step

boolean

Mark as final step to complete reasoning

confidence

number

Confidence level 0-1 (warnings below 0.5)

uncertainty_notes

string

Describe doubts or assumptions

revises_step

integer

Step number being corrected

revision_reason

string

Why revision is needed

branch_from

integer

Step to branch from

branch_id

string

Unique branch identifier

branch_name

string

Human-readable branch name

dependencies

integer[]

Step numbers this depends on

session_id

string

Group related reasoning chains

tools_used

string[]

Tools used in this step

external_context

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 server

Troubleshooting

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

Author

Nikko Gonzales - nikkoxgonzales

License

MIT

Available Tools

1 tool
crashA

Record a structured reasoning step for complex problem-solving.

Use this tool to break down multi-step problems into trackable reasoning steps. Each step captures your current thinking, expected outcome, and planned next action.

WHEN TO USE:

  • Multi-step analysis, debugging, or planning tasks

  • Tasks requiring systematic exploration of options

  • Problems where you need to track confidence or revise earlier thinking

  • Exploring multiple solution paths via branching

WORKFLOW:

  1. Start with step_number=1, estimate your total steps

  2. Describe your thought process, expected outcome, and next action

  3. Continue calling for each reasoning step, adjusting estimated_total as needed

  4. Use confidence (0-1) when uncertain about conclusions

  5. Use revises_step to correct earlier reasoning when you find errors

  6. Use branch_from to explore alternative approaches

  7. Set is_final_step=true when reasoning is complete

Returns JSON summary with step count, completion status, and next action.

Inputs: context (required), outcome (required), purpose (required), thought (required), +16 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.3/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of confusion or overlap. The tool's purpose of recording structured reasoning steps is clearly distinct and unambiguous.

    Naming Consistency5/5

    Since there is only one tool, there are no naming inconsistencies to evaluate. The name 'crash' is somewhat unconventional but does not conflict with any other tools.

    Tool Count3/5

    A single tool feels thin for a server, especially one named 'crash-mcp' which hints at broader scope. However, for the narrow purpose of logging reasoning steps, one tool could be sufficient, making it borderline.

    Completeness4/5

    The tool covers the full lifecycle of recording a reasoning step, including parameters for branching, revising, confidence, and final-step indication. It lacks explicit retrieval or management capabilities, but the domain is narrow enough that the tool is effectively complete.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      A MCP server that implements sequential thinking protocols, provides structured problem-solving methods, decomposes complex problems into manageable steps, and supports iterative optimization and alternative reasoning paths.
      1
      2
      Apache 2.0
    • A
      license
      A
      quality
      D
      maintenance
      A Python-based MCP server that facilitates structured problem-solving through sequential thinking, branching, and confidence scoring. It allows users to track assumptions and manage multiple concurrent reasoning sessions to break down complex tasks.
      1
      21
      MIT