Busabase for Crush

Connect Crush to Busabase

Open-source terminal coding agent from Charm with skills and built-in stdio, HTTP, and SSE MCP support.

Paste this into Crush

Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Follow it through to the end, then confirm the connection works.

Read the Crush documentation
Busabase
Agent Skill
The Busabase review inbox, showing proposed changes waiting for approval

Give your agent this one instruction

You end up with more than a connector: the busabase skill carries the whole approval-first workflow, the CLI, and the full API — available in every future session without re-pasting anything.

Asks first

Busabase Cloud or Personal Desktop — your call, before anything happens.

Connects

Signs you in and stores the credential itself. No API key to copy by hand.

Seeds a Base

Creates and fills your first Base, so the workspace is not an empty screen.

Installs the skills

busabase and busabase-app-creator become permanent, for every session after this.

For this agent

Crush discovers skills and can run shell commands. Use a trusted project and review the setup commands before approval.

Prefer a connector?

If you would rather wire Busabase in as MCP tools than let the agent install a skill, use the server URL below.

At a glance

Vendor
Charm
How it connects
MCP + OAuth · MCP + API key · Plugin / Skill · busabase-cli · REST API
Transport
Streamable HTTP
Authentication
OAuth (dynamic registration)
Config file
$HOME/.config/crush/crush.json or .crush.json
Run this
brew install charmbracelet/tap/crush

Install Crush using an official package method, open a trusted repository, and ask: Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Review the commands, complete authentication, then ask Crush to verify the account and installed skills. Its native remote MCP path is also compatible with Streamable HTTP and OAuth dynamic registration.

Known gotchas

For OAuth HTTP servers, set oauth to true. When no client ID is provided Crush attempts RFC 7591 dynamic client registration; a server that rejects registration needs explicit client credentials.

These stepsFrom official docsNo check date recorded

Written from this agent's own documentation. We have not re-run every step on a real machine, so check the linked docs if a command has changed.

Let your agent do the setup

One instruction, reviewed access, and every change it makes afterwards arrives as a proposal you approve.

Browse every agent

Paste this into Crush

Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Follow it through to the end, then confirm the connection works.