Busabase for Oh My Pi

Connect Oh My Pi to Busabase

Coding-first Pi fork with built-in subagents, browser tooling, and native HTTP MCP discovery.

Paste this into Oh My Pi

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 Oh My Pi 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

Run the setup prompt in the intended OMP profile. User-level MCP configuration and credentials are isolated per profile.

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.

Oh My Pi MCP documentation

At a glance

Vendor: Can Bölük
How it connects: MCP + API key · Plugin / Skill · MCP + OAuth
Transport: Streamable HTTP
Authentication: API key
Config file: ~/.omp/agent/mcp.json

Add Busabase to ~/.omp/agent/mcp.json (or .omp/mcp.json for one project):

{
  "mcpServers": {
    "busabase": {
      "type": "http",
      "url": "https://busabase.com/api/mcp",
      "headers": { "Authorization": "Bearer ${BUSABASE_API_KEY}" }
    }
  }
}

Export BUSABASE_API_KEY locally, then run /mcp reload and /mcp test busabase inside OMP. Ask it to call auth_verify. Named profiles use ~/.omp/profiles/<name>/agent/mcp.json.

OMP also documents a managed OAuth route for http/sse servers: set "auth": { "type": "oauth" } on the entry (an optional oauth object takes clientId/clientSecret/scope/redirect settings), then sign in or refresh with /mcp reauth busabase. Completed flows are stored per profile under a deterministic id derived from the profile and server URL, so any config pointing at the same URL resolves that profile's credential automatically. Note the docs' caveat: an "apikey" auth type does not inject keys from auth storage — API keys still go in headers, as above.

Known gotchas

Set type to http explicitly in writer/direct configs: those default to stdio when type is omitted and report that command is missing. Discovery is smarter — a URL-only entry discovered from a config file is inferred as http (a command entry as stdio) — but an explicitly stdio entry still needs a command. Named profiles use ~/.omp/profiles/<name>/agent/mcp.json, and OAuth credentials are stored per profile, keyed by server URL.

How it compares

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

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

These stepsFrom official docsLast checked Nov 12, 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 Oh My Pi

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