Busabase for Command Code

Connect Command Code to Busabase

Terminal coding agent with project-aware MCP configuration and support for remote HTTP servers.

Paste this into Command Code

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 Command Code documentation

Busabase

Agent Skill

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

Run the setup prompt from the repository where you want project-scoped Busabase skills; review any command before Command Code executes it.

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: Command Code
How it connects: MCP + OAuth · MCP + API key · Plugin / Skill · busabase-cli · REST API
Transport: Streamable HTTP
Authentication: Unknown
Config file: ~/.commandcode/mcp.json or .mcp.json

Run this

npm i -g command-code

Install Command Code, run cmd in a trusted project, and ask: Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Approve the chosen login flow, then ask it to verify the active Busabase account. For a manual remote MCP fallback, its documented command shape is cmd mcp add --transport http <name> <url>.

Known gotchas

Command Code documents OAuth Authorization Code with PKCE, but does not state whether an unknown client can use dynamic registration. MCP tokens are stored in ~/.commandcode/mcp-tokens.json.

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.

Where these steps come from Official site

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 Command Code

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

All agents

Busabase for Command Code

Connect Command Code to Busabase

Terminal coding agent with project-aware MCP configuration and support for remote HTTP servers.

Paste this into Command Code

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 Command Code documentation

Busabase

Agent Skill

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

Run the setup prompt from the repository where you want project-scoped Busabase skills; review any command before Command Code executes it.

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: Command Code
How it connects: MCP + OAuth · MCP + API key · Plugin / Skill · busabase-cli · REST API
Transport: Streamable HTTP
Authentication: Unknown
Config file: ~/.commandcode/mcp.json or .mcp.json

Run this

npm i -g command-code

Known gotchas

Command Code documents OAuth Authorization Code with PKCE, but does not state whether an unknown client can use dynamic registration. MCP tokens are stored in ~/.commandcode/mcp-tokens.json.

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.

Where these steps come from Official site

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 Command Code

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

All agents

Busabase for Command Code

Connect Command Code to Busabase

Terminal coding agent with project-aware MCP configuration and support for remote HTTP servers.

Paste this into Command Code

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 Command Code documentation

Busabase

Agent Skill

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

Run the setup prompt from the repository where you want project-scoped Busabase skills; review any command before Command Code executes it.

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: Command Code
How it connects: MCP + OAuth · MCP + API key · Plugin / Skill · busabase-cli · REST API
Transport: Streamable HTTP
Authentication: Unknown
Config file: ~/.commandcode/mcp.json or .mcp.json

Run this

npm i -g command-code

Known gotchas

Command Code documents OAuth Authorization Code with PKCE, but does not state whether an unknown client can use dynamic registration. MCP tokens are stored in ~/.commandcode/mcp-tokens.json.

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.

Where these steps come from Official site

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 Command Code

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