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

At a glance

Vendor: Can Bölük
How it connects: MCP + API key · Plugin / Skill
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.

Known gotchas

Set type to http explicitly. If omitted, OMP treats the entry as stdio and reports that command is missing. Named profiles use ~/.omp/profiles/<name>/agent/mcp.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 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.

All agents

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

At a glance

Vendor: Can Bölük
How it connects: MCP + API key · Plugin / Skill
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.

Known gotchas

Set type to http explicitly. If omitted, OMP treats the entry as stdio and reports that command is missing. Named profiles use ~/.omp/profiles/<name>/agent/mcp.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 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.

All agents

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

At a glance

Vendor: Can Bölük
How it connects: MCP + API key · Plugin / Skill
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.

Known gotchas

Set type to http explicitly. If omitted, OMP treats the entry as stdio and reports that command is missing. Named profiles use ~/.omp/profiles/<name>/agent/mcp.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 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.