Busabase MCP server
Commit Nov 14, 2026Lets an AI agent manage a workspace database, propose data changes for review, and turn product ideas into complete workspace applications.
Also known as busabase/skills, skills
- Stars
- 3
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 0.1.2
- Last commit
- Nov 14, 2026
- License
- MIT
What is Busabase MCP?
Busabase lets an AI agent manage a workspace database, propose data changes for review, and turn product ideas into complete workspace applications.
Summary generated from the project's README
About Busabase MCP server
Busabase provides an interface for AI agents to interact with an open-source database and workspace environment. It allows agents to manage records, propose data changes through change requests, and transform product concepts into functional workspace applications. The system is designed so that every write operation includes a message and a diff, ensuring that changes can be reviewed by a human before they are finalized.
Developers can integrate these capabilities using several methods depending on their client. For Claude Code and Codex, specialized plugins handle authentication via browser-based OAuth, removing the need for manual API key management. General MCP-capable agents can connect to a local endpoint at localhost:15419 or use the cloud service at busabase.com/api/mcp by providing a Bearer token. The server offers two primary skills: a core skill for driving workspace operations and an app creator skill for building complete applications with native resources and reviewable AirApps.
What you can do with it
- 1Propose database modificationsAn agent can suggest specific data updates that require human approval through a diff and message system.
- 2Generate complete workspace applicationsYou can instruct an AI to build a full application from a product idea including data access and a user interface.
- 3Manage workspace records via HTTPAn AI agent can list bases and records or drive a workspace using the core busabase skill.
Written from the project's README. Every use case is checked against a quote from it.
How to install Busabase MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Busabase MCP in Claude Code
$ claude mcp add --transport http skills https://busabase.com/api/mcpInstall Busabase MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"skills": {
"url": "https://busabase.com/api/mcp"
}
}
}Install Busabase MCP in VS Code
.vscode/mcp.json
{
"servers": {
"skills": {
"type": "http",
"url": "https://busabase.com/api/mcp"
}
}
}Install Busabase MCP in VS Code CLI
$ code --add-mcp '{"name":"skills","type":"http","url":"https://busabase.com/api/mcp"}'Install Busabase MCP in Codex
$ codex mcp add skills --url https://busabase.com/api/mcpInstall Busabase MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.skills] url = "https://busabase.com/api/mcp"
Install Busabase MCP in Gemini CLI
$ gemini mcp add -s user --transport http skills https://busabase.com/api/mcpInstall Busabase MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"skills": {
"url": "https://busabase.com/api/mcp",
"type": "http"
}
}
}Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablebusabase/skills is public and reachablegithub.com/busabase/skills ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-13github.com/busabase/skills ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeHTTPS endpoint answered 401 (sign-in required)Pass
README
View on GitHubBusabase Skills & Plugins
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.
Two skills, five ways to install them — pick whatever your agent supports.
Install
skills (Claude Code, Cursor, Codex, … — evergreen)
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
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
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:
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.
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(sendAuthorization: Bearer $BUSABASE_API_KEY)
Codex can use the full Cloud MCP surface directly with standard OAuth:
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. |
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.
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-app-creator/SKILL.md guided Busabase workspace and AirApp creator
.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
.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 usesbusabase. The sharedbusabase-app-creatorskill delegates connection, API, and ChangeRequest behavior to the host-specific MCP-first dependency.
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
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.
Busabase MCP questions
How do I add Busabase MCP to Claude Code?
Run claude mcp add --transport http skills https://busabase.com/api/mcp in your terminal. Add --scope user to make it available in every project.
How do I add Busabase MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
How does Busabase handle data writes?
Every write is treated as a change request with a message and a diff, which lands immediately with write access or waits for human review.
Can I use Busabase with any MCP-capable agent?
Yes, you can point any MCP-capable agent to your workspace's Streamable-HTTP endpoint, either locally or via the cloud.
What is the busabase-app-creator skill?
It is a skill that transforms a product idea into a full Busabase workspace app featuring native resources and bounded data access.