Busabase for Warp

Connect Warp to Busabase

The agentic terminal; MCP servers are added from settings, with no config file to edit.

Paste this into Warp

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 Warp 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

Warp runs commands natively, so the Skill path needs no setup at all. Paste the prompt into the agent panel.

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: Warp
How it connects: MCP + OAuth · Plugin / Skill
Transport: Streamable HTTP
Authentication: OAuth (dynamic registration)

Go to Settings → Agents → MCP servers, click + Add, and choose Streamable HTTP or SSE Server (URL).

{
  "busabase": {
    "url": "https://busabase.com/api/mcp"
  }
}

Start the server. Warp opens the browser OAuth flow automatically and stores the credentials on your device. Then ask the agent to call auth_verify.

Known gotchas

There is no CLI command for URL-based servers — it is a settings-screen flow only. Warp opens the OAuth window automatically when a server is started without stored 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.

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 Warp

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 Warp

Connect Warp to Busabase

The agentic terminal; MCP servers are added from settings, with no config file to edit.

Paste this into Warp

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 Warp 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

Warp runs commands natively, so the Skill path needs no setup at all. Paste the prompt into the agent panel.

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: Warp
How it connects: MCP + OAuth · Plugin / Skill
Transport: Streamable HTTP
Authentication: OAuth (dynamic registration)

Go to Settings → Agents → MCP servers, click + Add, and choose Streamable HTTP or SSE Server (URL).

{
  "busabase": {
    "url": "https://busabase.com/api/mcp"
  }
}

Start the server. Warp opens the browser OAuth flow automatically and stores the credentials on your device. Then ask the agent to call auth_verify.

Known gotchas

There is no CLI command for URL-based servers — it is a settings-screen flow only. Warp opens the OAuth window automatically when a server is started without stored 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.

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 Warp

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 Warp

Connect Warp to Busabase

The agentic terminal; MCP servers are added from settings, with no config file to edit.

Paste this into Warp

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 Warp 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

Warp runs commands natively, so the Skill path needs no setup at all. Paste the prompt into the agent panel.

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: Warp
How it connects: MCP + OAuth · Plugin / Skill
Transport: Streamable HTTP
Authentication: OAuth (dynamic registration)

Go to Settings → Agents → MCP servers, click + Add, and choose Streamable HTTP or SSE Server (URL).

{
  "busabase": {
    "url": "https://busabase.com/api/mcp"
  }
}

Start the server. Warp opens the browser OAuth flow automatically and stores the credentials on your device. Then ask the agent to call auth_verify.

Known gotchas

There is no CLI command for URL-based servers — it is a settings-screen flow only. Warp opens the OAuth window automatically when a server is started without stored 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.

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 Warp

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