Busabase for LobeHub

Connect LobeHub to Busabase

Open-source agent collaboration platform (formerly LobeChat; web, desktop and mobile) where agents with persistent memory take on tasks, work in team chats and run code locally or in a cloud sandbox. Skills use the open SKILL.md format and MCP servers are added under Settings → Connectors.

Paste this into LobeHub

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

For this agent

LobeHub imports skills into its own Skill Store from GitHub, a direct SKILL.md URL, or a ZIP, and its skills follow the open `SKILL.md` format. Its project discovery of `.agents/skills`, `.claude/skills`, `AGENTS.md` and `CLAUDE.md` applies to server-run agents in a bound directory, so for a regular LobeHub agent import the skill through the Skill Store rather than relying on `npx skills add`.

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: LobeHub, LLC
How it connects: MCP + API key · Plugin / Skill · busabase-cli
Transport: Unknown
Authentication: API key
Config file: Settings → Connectors (HTTP Server)

LobeHub agents can run shell commands (on your desktop app's device, a connected remote device, or the cloud sandbox) and import Agent Skills (SKILL.md), so the Skill path applies. In the LobeHub desktop app, open the agent you want to use, check that its execution device in the chat input is This device, and ask it: Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Approve the commands it proposes (LobeHub tool permissions can run a tool directly, ask first, or keep it off) and the sign-in link in your browser.

To add the Busabase skill to an agent yourself: on the Agent page click + in the chat input → Skills → Add Skill…, click Add (upper right) → Import from GitHub, enter https://github.com/busabase/skills/tree/main/skills/busabase, confirm the parsed skill, then set it to Auto or Pinned. Importing does not install dependencies or give the skill unrestricted execution, so the agent still needs a shell to run busabase-cli.

Prefer a connector?

Open Settings → Connectors and add an MCP server manually, choosing HTTP Server.
Enter the server URL https://busabase.com/api/mcp. LobeHub's docs say to add authentication or headers when the service uses them but do not describe OAuth for manually added servers, so use an API key: create one in Busabase Settings → API Keys (smallest permission, finite expiry) and add the header Authorization: Bearer <key>.
Open Agent Settings → Connectors, select the Busabase server, set the tool permissions (Allow, Ask or Deny) and save.
Ask the agent to call auth_verify on Busabase.

LobeHub: Skills Marketplace · Add an MCP manually

Known gotchas

LobeHub's docs describe adding an HTTP MCP server with a URL plus authentication or headers, but do not state its transport (streamable HTTP or SSE) or whether OAuth and dynamic client registration work for manually added servers, so Busabase is documented here with an API key. Where an agent runs shell commands depends on the execution device: the desktop app (This device), a remote device connected with `lh connect`, or the cloud sandbox, whose runtimes, installation permissions and network access depend on the provider, so check that Node and network access are available before the Skill flow. The web app cannot reach localhost; per LobeHub, only the desktop app can connect to local or network addresses. Not tried end to end by us.

How it compares

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

Capability	LobeHub	Claude Code	Cursor
Type	Agent platforms	Terminal agents	AI editors
Recommended path	Agent Skill	Agent Skill	Agent Skill
How it connects	MCP + API key · Plugin / Skill · busabase-cli	MCP + OAuth · Plugin / Skill	MCP + OAuth · Plugin / Skill
Transport	Unknown	Streamable HTTP	Streamable HTTP
Authentication	API key	OAuth (dynamic registration)	OAuth (dynamic registration)

These stepsFrom official docsLast checked Nov 6, 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 LobeHub

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