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 Skills documentation

Busabase

Agent Skill

Give your agent this one instruction

You end up with more than a connector: the busabase skill carries the whole change-request 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.

Install the Busabase skills

npx skills add busabase/skills

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.

Warp MCP documentation

At a glance

Vendor: Warp
How it connects: MCP + OAuth · Plugin / Skill
Transport: Streamable HTTP
Authentication: OAuth (dynamic registration)
Config file: ~/.warp/.mcp.json (project: .warp/.mcp.json)

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.

Warp also reads file-based MCP servers from ~/.warp/.mcp.json (global) or .warp/.mcp.json at the project root, and the built-in /agent-add-mcp skill can create or update those definitions for you. Editing an MCP config file requires your explicit approval, and project-scoped servers never auto-spawn — toggle them on per session.

Known gotchas

There is still no shell CLI command for adding URL-based servers, but Warp now also reads file-based definitions (~/.warp/.mcp.json global, .warp/.mcp.json in a project) and ships a built-in /agent-add-mcp skill that writes them; config edits require explicit approval. OAuth is per machine: re-authentication is required when opening Warp on a new machine (reset with `rm -rf ~/.mcp-auth`), and Warp's cloud agents cannot complete an interactive browser login, so authorization must be completed ahead of time.

How it compares

Connection capabilities side by side with other agents already in this directory.

Capability	Warp	Claude Code	Cursor
Type	Terminal agents	Terminal agents	AI editors
Recommended path	Agent Skill	Agent Skill	Agent Skill
How it connects	MCP + OAuth · Plugin / Skill	MCP + OAuth · Plugin / Skill	MCP + OAuth · Plugin / Skill
Transport	Streamable HTTP	Streamable HTTP	Streamable HTTP
Authentication	OAuth (dynamic registration)	OAuth (dynamic registration)	OAuth (dynamic registration)

These stepsFrom official docsLast checked Nov 10, 2026

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, one authorization, and every change it makes afterwards carries a message and a diff you can check or revert.

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.