The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Busabase listing page.
Agent Skills + plugins for Busabase — the approval-first knowledge base where AI proposes changes, a human reviews them, and only approved changes get merged.
Two skills, five ways to install them — pick whatever your agent supports.
skills (Claude Code, Cursor, Codex, … — evergreen)The repository root follows the Agent Plugins Specification v1.0.0:
plugin.json is the portable manifest, skills/ contains the Agent Skills, and mcp.json
declares the hosted Streamable HTTP MCP server. Install or load this repository root with any
client that supports the Agent Plugins format.
Agent Plugins v1 leaves OAuth and credentials to the client. Existing Claude Code and Codex
packages keep their dedicated browser-OAuth behavior. See
docs/agent-plugins.md for the compatibility mapping and validation.
The Claude Code plugin connects to https://busabase.com/api/mcp with browser OAuth. Claude
namespaces its bundled server as plugin:busabase:busabase. Start a new conversation after install
and login so the authenticated tool catalog is available. See
docs/claude-code-install.md for the complete verification and
recovery flow.
Maintainers should also read
docs/codex-to-claude-code-port.md for the host-by-host
manifest, MCP, OAuth, skill, and validation differences.
The Codex plugin connects to https://busabase.com/api/mcp, opens the standard browser OAuth
flow, and exposes a focused 22-tool catalog. No API key setup is required.
Plugin installation and MCP authorization are separate states. After the browser says
Authentication complete, verify the saved connection before starting a Busabase task:
The busabase row should show Auth as OAuth. If it still shows Not logged in, run
codex mcp login busabase again and complete the newly opened browser tab while that command is
still running. Start a new Codex task after a successful login so the task loads the authenticated
tool catalog.
Point your agent at your workspace's Streamable-HTTP endpoint:
http://localhost:15419/api/mcp (no auth)https://busabase.com/api/mcp (send Authorization: Bearer $BUSABASE_API_KEY)Codex can use the full Cloud MCP surface directly with standard OAuth:
The portable root mcp.json declares the hosted endpoint using the Agent Plugins v1
format. The legacy root .mcp.json continues to wire the local endpoint for general
MCP clients. The Claude
package uses its own hosted OAuth MCP configuration. The Codex plugin has a
separate remote MCP configuration.
The root busabase skill remains the full CLI/curl guide for local and general-purpose agent
installs. The Claude- and Codex-bundled skills are intentionally MCP-first: they rely on OAuth and
the curated tool catalog instead of reading ~/.busabase/.env.
To set up a workspace from scratch first, paste the onboarding prompt from your Busabase dashboard (Agent Skills button) — it walks your agent through connecting, seeding a first Base, and then running one of the install commands above.
| Skill | What it does |
|---|---|
busabase | Drive a Busabase workspace over HTTP: list Bases/records, propose ChangeRequests, and merge approved ones. |
busabase-app-creator | Turn a product idea into a complete Busabase workspace app with native resources, bounded data access, and a reviewable AirApp. |
Looking for installable templates? Complete apps — tables, an AirApp and the manual an agent reads — live in busabase/templates. They are kept separate so installing these two skills does not pull down every template's source and screenshots.
This one repo serves every install path above:
Why host-specific Busabase skills? The plugin packages use hosted OAuth and MCP tools instead of local shell configuration. Claude Code additionally namespaces the server as
plugin:busabase:busabase, while Codex usesbusabase. The sharedbusabase-app-creatorskill delegates connection, API, and ChangeRequest behavior to the host-specific MCP-first dependency.
The OpenAI Plugin Directory and the MCP Registry are separate release channels. Use
docs/openai-plugin-submission.md for the Platform submission,
domain verification, reviewer access, test prompts, and production smoke checks.
Bump version in server.json only when publishing an MCP Registry update. Bump the Codex plugin
manifest independently for GitHub marketplace releases.