Busabase for OpenHands

Connect OpenHands to Busabase

Open-source software development agent platform with a local CLI, cloud runtime, shell tools, and configurable MCP servers.

Paste this into OpenHands

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

Use the local CLI in a trusted workspace for the Skill path and review filesystem and shell permissions before approval.

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

Run this

curl -fsSL https://install.openhands.dev/install.sh | sh

Install the OpenHands CLI, start it in a trusted repository, and ask: Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Review and approve the setup, complete authentication, then ask OpenHands to verify the active account. Its CLI also supports openhands mcp add with http, sse, or stdio transport.

Known gotchas

OpenHands requires `--auth oauth` when adding an OAuth MCP server, but its docs do not identify dynamic versus static client registration. API-key headers are also supported.

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 OpenHands

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 OpenHands

Connect OpenHands to Busabase

Open-source software development agent platform with a local CLI, cloud runtime, shell tools, and configurable MCP servers.

Paste this into OpenHands

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

Use the local CLI in a trusted workspace for the Skill path and review filesystem and shell permissions before approval.

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

Run this

curl -fsSL https://install.openhands.dev/install.sh | sh

Known gotchas

OpenHands requires `--auth oauth` when adding an OAuth MCP server, but its docs do not identify dynamic versus static client registration. API-key headers are also supported.

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 OpenHands

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 OpenHands

Connect OpenHands to Busabase

Open-source software development agent platform with a local CLI, cloud runtime, shell tools, and configurable MCP servers.

Paste this into OpenHands

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

Use the local CLI in a trusted workspace for the Skill path and review filesystem and shell permissions before approval.

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

Run this

curl -fsSL https://install.openhands.dev/install.sh | sh

Known gotchas

OpenHands requires `--auth oauth` when adding an OAuth MCP server, but its docs do not identify dynamic versus static client registration. API-key headers are also supported.

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 OpenHands

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