crush is a Doramagic Project Pack for MCP setup guidance, host configuration checks, tool permission boundaries, recovery steps, and acceptance checks. It links the upstream repository, source-backed manual, prompt preview, AI context, and risk boundaries so users can evaluate the project before installation.

What should I verify first?

Verify the MCP server command, permission scope, and rollback path in a non-primary host configuration first.. Keep credentials out of the first run, record expected output, define cleanup, and use public sample data before real workloads.

What is the main risk?

Developers may fail before the first successful local run: Status line obscured by onboarding dialog. Use upstream documentation and a sandbox validation path before adoption.

MCP Tool Integration · Public

crush

MCP tool integration project for safely connecting external tools, services, or data sources to an AI host.

MCPTool callingHost configurationPermission boundariesAcceptance checks

Best fitDevelopers who need Claude, Cursor, Codex, or another MCP-capable AI host to call external tools safely.

Check whether this project matches your task before installing it.

What it can doMCP setup guidance, host configuration checks, tool permission boundaries, recovery steps, and acceptance checks

Review the portable capability path.

Before continuingVerify in a sandbox

Do not treat a preview pack as a proven local install.

GitHub snapshot25k stars

1.8k forks · 120 contributors

Doramagic.ai Last verification date: 2026-06-01 Verification method: source evidence, semantic profile, public page gate, and static build acceptance.

Official first step Read manual preview Source repository

Publication status · 2026-06-01

What is crush?

crush helps connect external tools, services, or data sources to AI hosts that support MCP.
Best fit: Developers who need Claude, Cursor, Codex, or another MCP-capable AI host to call external tools safely.
Not for: Not for users who cannot change host configuration, grant tool permissions, or isolate network, file, and credential access.
Capability added to an AI workflow: MCP setup guidance, host configuration checks, tool permission boundaries, recovery steps, and acceptance checks
First safe verification step: Verify the MCP server command, permission scope, and rollback path in a non-primary host configuration first.
Verification state: source, Quick Start, and sandbox install checks are recorded as passed.
Top risk: Developers may fail before the first successful local run: Status line obscured by onboarding dialog
Evidence base: https://github.com/charmbracelet/crush, https://github.com/charmbracelet/crush#readme, Human Manual, Pitfall Log

Quick decision

Use this section to decide whether the project is worth a deeper read.

Best forDevelopers who need Claude, Cursor, Codex, or another MCP-capable AI host to call external tools safely.

Match the project to your task before installing it.

CapabilityMCP setup guidance, host configuration checks, tool permission boundaries, recovery steps, and acceptance checks

MCP tool integration project for safely connecting external tools, services, or data sources to an AI host.

Repositorycharmbracelet/crush

25k stars · 1.8k forks

What it can do

Translate the upstream project into concrete capabilities the user can judge before installing.

Getting Started with Crush

Related topics: Configuration Guide, LLM Provider Setup

Source: https://github.com/charmbracelet/crush / Human Manual

Project Structure

Related topics: Getting Started with Crush

Source: https://github.com/charmbracelet/crush / Human Manual

Configuration Guide

Related topics: Getting Started with Crush, LLM Provider Setup, Permission System

Source: https://github.com/charmbracelet/crush / Human Manual

LLM Provider Setup

Related topics: Getting Started with Crush, Configuration Guide

Source: https://github.com/charmbracelet/crush / Human Manual

Built-in Tools

Related topics: Permission System, MCP Integration

Source: https://github.com/charmbracelet/crush / Human Manual

Sources: https://github.com/charmbracelet/crush, Human Manual, Project Pack evidence, and downstream validation signals.

Community Discussion Evidence

Project-level external discussion stays visible on the detail page, not only inside the manual.

Stars25k stars

Forks1.8k forks

Contributors120 contributors

Licenseunknown

Community Discussion Evidence

11 source-linked items

Review these external discussions before using crush with real data or production workflows. They are review inputs, not standalone proof that the project is production-ready.

01
Disabled models still appear in the TUI model picker
github / github_issue
02
Custom provider models are invisible in the TUI
github / github_issue
03
Status line obscured by onboarding dialog
github / github_issue
04
I hope to enable support for glm, qwen, kimi and minimax in the eastopen
github / github_issue
05
Qwen 3.7 Max on OpenCode Go Unauthorized Error
github / github_issue
06
rate limited api requests (429) are not retried
github / github_issue
07
Configuration risk requires verification
GitHub / issue
08
Configuration risk requires verification
GitHub / issue
09
Configuration risk requires verification
GitHub / issue
10
Configuration risk requires verification
GitHub / issue
11
Capability evidence risk requires verification
GitHub / issue

How to start

Only source-backed commands are shown here. Verify them in an isolated environment first.

Try the prompt first

Test the workflow without installing the upstream project.

preview

Read the Human Manual

Understand inputs, outputs, limits, and failure modes.

manual

Take context to your AI host

Use the compiled assets in your preferred AI environment.

context

Run sandbox verification

Confirm install commands and rollback before using a primary environment.

verify

npm install -g @charmland/crush

Official start command · https://github.com/charmbracelet/crush#readme · verified: yes

Human Manual

The English page must expose the real manual, not a short placeholder.

8+ sections · Human Manual

crush Manual

| Component | Purpose | Location | |-----------|---------|----------| | App | Main application state and coordination | internal/app/app.go | | Backend | Workspace and session management |...

Open the full manual

https://github.com/charmbracelet/crush Project Manual
Table of Contents
Getting Started with Crush
Related Pages
What is Crush?
Installation
macOS
Homebrew

Getting Started with Crush

Related topics: Configuration Guide, LLM Provider Setup

Source: https://github.com/charmbracelet/crush / Human Manual

Project Structure

Related topics: Getting Started with Crush

Source: https://github.com/charmbracelet/crush / Human Manual

Configuration Guide

Related topics: Getting Started with Crush, LLM Provider Setup, Permission System

Source: https://github.com/charmbracelet/crush / Human Manual

LLM Provider Setup

Related topics: Getting Started with Crush, Configuration Guide

Source: https://github.com/charmbracelet/crush / Human Manual

Built-in Tools

Related topics: Permission System, MCP Integration

Source: https://github.com/charmbracelet/crush / Human Manual

AI Context Pack and portable assets

After deciding to continue, take the project context into your own AI host.

Complete pack plus user-owned assets

These files are planning and verification assets for Claude Code, Codex, Gemini, Cursor, ChatGPT, and other AI hosts.

Download complete pack Read Human Manual

BundleComplete Project Pack AssetAI Context Pack AssetBoundary & Risk Card AssetHuman Manual AssetPitfall Log AssetPrompt Preview AssetQuick Start EvidenceREPO_INSPECTION.json

Preflight checks

Treat this page as a planning asset, not proof that your local environment is ready.

The manual is generated from source-linked project files and Doramagic validation signals.
Community evidence warnings stay visible instead of being converted into marketing claims.
This English page is indexable because the locale quality gate passed and explicit English index approval is enabled.
Use the upstream repository as the final authority for installation commands, license, and version-specific behavior.

Pitfall Log and verification risks

Doramagic surfaces high-risk items before users treat a candidate capability as verified.

medium

Installation risk requires verification

Developers may fail before the first successful local run: Status line obscured by onboarding dialog

medium

Installation risk requires verification

May increase setup, validation, or first-run risk for the user.

medium

Configuration risk requires verification

Developers may misconfigure credentials, environment, or host setup: Qwen 3.7 Max on OpenCode Go Unauthorized Error

medium

Configuration risk requires verification

Upgrade or migration may change expected behavior: v0.68.0

medium

Configuration risk requires verification

Upgrade or migration may change expected behavior: v0.70.0

medium

Configuration risk requires verification

Upgrade or migration may change expected behavior: v0.71.0

medium

Configuration risk requires verification

Upgrade or migration may change expected behavior: v0.74.0

medium

Configuration risk requires verification

May increase setup, validation, or first-run risk for the user.