Busabase

What busabase MCP server does

The busabase MCP server gives an agent an MCP connection to a Busabase workspace. Through that connection, the agent can inspect available Bases and records, submit proposed changes as ChangeRequests, and merge changes after approval. This makes the integration suitable for workflows where an agent can prepare knowledge updates but should not publish them without human review.

The repository contains two related skills. The busabase skill documents workspace operations over HTTP. The busabase-app-creator skill guides an agent in turning a product idea into a Busabase workspace app with native resources, bounded data access, and a reviewable AirApp. App templates are maintained in a separate repository and are not installed by these skills.

How it works

The MCP endpoint is exposed over Streamable HTTP. A local workspace uses http://localhost:15419/api/mcp and does not require authentication. The hosted service uses https://busabase.com/api/mcp; direct API access can authenticate with a bearer token sourced from BUSABASE_API_KEY.

The repository provides several installation paths around the same Busabase capability. A general MCP-capable agent can use the endpoint directly, while the repository also supplies Agent Plugins v1 metadata, a Claude Code plugin, and a Codex plugin. The Claude Code and Codex packages use browser-based OAuth for their hosted connections. Codex exposes a focused catalog of 22 tools through its plugin.

Setup and configuration

For a local or general-purpose installation, configure the agent with the local endpoint for a desktop workspace or the hosted endpoint for a cloud workspace. For hosted direct access, send Authorization: Bearer $BUSABASE_API_KEY with requests. OAuth-based plugin installations do not require API key setup.

Claude Code can install the marketplace plugin, then authenticate the namespaced MCP connection with claude mcp login plugin:busabase:busabase. Codex can install its plugin and run codex mcp login busabase. Installation and authorization are separate steps; after login, verify the Codex connection with codex mcp list and start a new task so the authenticated catalog loads.

A workspace can also be initialized from the onboarding prompt available through the Busabase dashboard's Agent Skills button. That flow helps connect the agent, seed an initial Base, and select an installation method.

Tools and capabilities

The documented capabilities include:

• Listing Busabase Bases.
• Reading workspace records.
• Creating proposed changes as ChangeRequests.
• Merging approved ChangeRequests.
• Guiding creation of a Busabase app and reviewable AirApp through the companion skill.

The Codex plugin advertises a 22-tool catalog, while the general MCP surface is described separately from that curated package.

Limitations and notes

The busabase MCP server follows an approval-first model: agents propose changes, and a human must review them before approved changes are merged. It is therefore not described as an unrestricted write interface.

Authentication depends on the installation path. Local access is unauthenticated, hosted direct MCP access uses a bearer API key, and the Claude Code and Codex plugins use browser OAuth. Host-specific packages may expose different catalogs and connection guidance. The repository documents Claude Code and Codex integrations explicitly; other clients must support the relevant MCP or Agent Plugins format.