Busabase Skills & Plugins
English · 简体中文 · 繁體中文 · 日本語
Agent Skills + plugins for Busabase — the open-source database and workspace
for AI agents. Every write is a change request with a message and a diff: it lands at once with
write access and waits for a person's review otherwise.
Seven skills, five ways to install them — pick whatever your agent supports.
Install
skills (Claude Code, Cursor, Codex, … — evergreen)```bash
npx skills add busabase/skills
### Agent Plugins v1 (portable package)
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.
### Claude Code plugin```bash
claude plugin marketplace add https://github.com/busabase/skills.git
claude plugin install busabase@busabase
claude mcp login plugin:busabase:busabase
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.
Codex plugin```bash
codex plugin marketplace add busabase/skills
codex plugin add busabase@busabase
codex mcp login busabase
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:```bash
codex mcp list
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.
WorkBuddy connector
Install Busabase from the WorkBuddy Connector marketplace (WorkBuddy 4.24.0 or later) and
authorize it in the browser. WorkBuddy runs the OAuth flow in its cloud and keeps the token, so
there is nothing to configure locally. The package source lives in workbuddy/;
it is submitted to WorkBuddy for review rather than installed from this repo.
Doubao Work native plugin
The doubao/ package bundles the Busabase MCP connection and the shared
busabase skill. It uses standard MCP OAuth: install through the plugin entry available
in your Doubao Work account and complete browser consent. Installation and authorization
are separate steps. See the package guide for the ZIP layout and
acceptance checklist. Package validation is complete; native-client installation and
platform approval must be recorded separately.
More native platforms
Each package has its own installation and update instructions. Installing a
package does not complete OAuth or submit it to a marketplace.
| Platform | Package / instructions | Distribution note |
|---|---|---|
| Gemini CLI | gemini/ | Code Assist enterprise/API audiences; root extension archive or dedicated repository |
| Antigravity CLI | antigravity/ | Separate native manifest and MCP configuration |
| Cursor | cursor/ | Native Agent Plugin; public Marketplace review is separate |
| Grok Build | grok/ | Native Grok plugin; external marketplace contribution |
| Kimi Code / Work | kimi/ | One native plugin format; Work import needs account verification |
| Kiro | kiro/ | Agent Plugins format; registry review is separate |
| Copilot CLI | copilot/ | Use the included marketplace for durable updates |
| Perplexity Computer | perplexity/ | Custom plugin ZIP/GitHub import; paid-plan permissions may apply |
| MiniMax Code | minimax/ | Full CLI Skill; authenticated MCP requires provider onboarding |
| Base44 | base44/ | Not a marketplace package: a kit you copy into your Base44 project (custom-integration OpenAPI, two-way sync functions and workflows, MCP guide). No Base44 catalog exists; live-app verification is still pending |
Existing integrations also cover Junie, Pi, Paseo
and portions of Hermes. See OpenHands and
Agent Zero for catalog drafts and remaining requirements.
MCP (any MCP-capable agent)
Point your agent at your workspace's Streamable-HTTP endpoint:
- Desktop / local:
http://localhost:15419/api/mcp(no auth) - Cloud:
https://busabase.com/api/mcp— sign in with OAuth in the browser; there is no API
key to paste. Any client that supports OAuth for remote MCP servers (Claude Code, Codex and
a growing list of others) can connect this way. For headless automation, a Bearer API key
(Authorization: Bearer $BUSABASE_API_KEY) works on the same endpoint.
Generic OAuth example (Codex shown; the flow is the same for any OAuth-capable client):```bash
codex mcp add busabase --url https://busabase.com/api/mcp
codex mcp login busabase
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.
## Skills
| Skill | What it does |
| --- | --- |
| `busabase` | Drive a Busabase workspace over HTTP: list Bases/records, propose ChangeRequests, and merge approved ones. The full CLI / API / MCP reference. |
| `busabase-ops` | Operate a workspace day to day — dedupe-before-create, schema-first writes, attach-and-make-searchable filing, audits and clean-ups — with read-before-write discipline, checking what actually landed. A full copy of `busabase` under the operator's name. |
| `busabase-app-creator` | Turn a product idea into a complete Busabase workspace app with native resources, bounded data access, and a reviewable AirApp. |
| `busabase-template-creator` | Author and publish templates to the public `busabase/templates` catalog, layered on the app-creator contract. |
| `busabase-app-package-creator` | Alias of `busabase-app-creator` for packaging an existing AirApp into an installable package. |
| `busabase-package-creator` | Alias of `busabase-app-creator` for authoring a Busabase package (manifest, contents, versioning). |
| `busabase-skill-creator` | Alias of `busabase-app-creator` for creating a Busabase Skill and packaging it for installation. |
> **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.
## Repo layout
This one repo serves every install path above:```
plugin.json Agent Plugins v1 portable manifest
mcp.json Agent Plugins v1 hosted MCP profile
skills/busabase/SKILL.md canonical local/general-purpose skill
skills/busabase-ops/SKILL.md day-to-day workspace operator entry point
skills/busabase-app-creator/SKILL.md guided Busabase workspace and AirApp creator
skills/busabase-*-creator/SKILL.md template creator + three alias entries: full copies
of busabase-app-creator under task names (real files,
not symlinks — the skills CLI does not follow symlinks)
.claude-plugin/marketplace.json Claude Code marketplace listing
claude/.claude-plugin/plugin.json Claude Code plugin manifest
claude/.mcp.json hosted OAuth MCP profile for Claude Code
claude/skills/busabase/SKILL.md Claude-specific MCP-first connection guidance
claude/skills/busabase-app-creator/ symlink to the shared app creator skill
.agents/plugins/marketplace.json Codex marketplace listing
plugins/busabase/.codex-plugin/plugin.json Codex plugin manifest
plugins/busabase/.mcp.json hosted OAuth MCP profile for Codex
plugins/busabase/skills/busabase/SKILL.md Codex needs the skill INSIDE the plugin dir
(MCP-first guidance for the curated profile)
plugins/busabase/skills/busabase-app-creator/SKILL.md
app creator bundled beside its Busabase dependency
plugins/busabase/assets/ icons and light/dark logos bundled with Codex
workbuddy/connector-meta.json WorkBuddy connector metadata + server-side OAuth declaration
workbuddy/mcp.json hosted MCP server for WorkBuddy
workbuddy/skills/busabase/SKILL.md WorkBuddy-specific MCP-first guidance (same shared body)
.mcp.json legacy/general-client local MCP profile
server.json official MCP Registry entry (remote → busabase.com/api/mcp)
scripts/validate-agent-plugin.mjs portable and client-package conformance guard
> 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 uses busabase. The shared busabase-app-creator skill
> delegates connection, API, and ChangeRequest behavior to the host-specific MCP-first dependency.
Validate release metadata
Maintainer validation uses Node.js 22+ and Python 3:```bash
node --test scripts/strict-json.test.mjs
node scripts/validate-agent-plugin.mjs
The release guard checks original JSON text for duplicate object keys, including escaped and
nested names that `JSON.parse` would silently overwrite. Missing Python fails validation closed.
Python is needed only by these publishing checks; it is not bundled into a plugin or required
to run one.
## Publish to the OpenAI Plugin Directory
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.
## Publish to the official MCP Registry```bash
brew install mcp-publisher # or grab the binary from the registry releases
mcp-publisher login dns --domain busabase.com --private-key <KEY> # verifies the com.busabase/* namespace
mcp-publisher publish # publishes server.json — live immediately, no review
Bump version in server.json only when publishing an MCP Registry update. Bump the Codex plugin
manifest independently for GitHub marketplace releases.
Privacy and support
The hosted MCP service processes the Busabase workspace data that the connected user authorizes.
See the Busabase Privacy Policy for its data practices.
The plugin does not bundle credentials; the host manages the OAuth connection.
For installation, package or connection problems, open a support issue.
Do not include credentials or private workspace data in a public issue.
