Busabase

com.busabasePublished by busabase.comOfficial publisherv0.1.1Updated Oct 28, 2026

Database for your AI agent. Turn its output into data, docs, skills, and apps you can actually use.

VerifiedStreamable HTTPWeb executableDatabasesProductivity & WorkflowDeveloper Tools

Overview

AI-generated overview

Busabase is a hosted database and workspace for AI agents, letting an assistant list Bases and records, propose change requests, and build workspace apps.

What you can do
  • List Bases and records in a Busabase workspace
  • Propose change requests with a message and a diff, and merge approved ones
  • Turn agent output into data, docs, skills and apps
  • Create a complete workspace app with native resources and a reviewable AirApp
  • Drive a workspace over HTTP through the bundled skills and plugins
When to use it
Use it when you want an agent to store and manage structured data in a Busabase workspace, or to turn its output into a reviewable app or document set. It suits teams that want every agent write to go through a change request with a diff and optional human review.
Requirements
A remote Streamable HTTP endpoint: the hosted one at busabase.com/api/mcp, or a local one at localhost:15419/api/mcp with no auth. The hosted endpoint requires OAuth browser login or an Authorization Bearer header with a Busabase API key. Optional installs use npx skills, the Claude Code plugin, or the Codex plugin.
Before you install
The hosted endpoint requires OAuth or an API key, so treat the key as a secret. Writes are change requests: with write access they land immediately, otherwise they wait for a person's review, so check which mode a workspace uses before letting an agent write. The local endpoint at localhost:15419 runs without authentication.

Installation

In SourceWeft

  1. Open Busabase in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.busabase%2Fbusabase/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "busabase": {
      "type": "http",
      "url": "https://busabase.com/api/mcp"
    }
  }
}

README

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.

Two 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.gitclaude plugin install busabase@busabaseclaude 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/skillscodex plugin add busabase@busabasecodex 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.

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 (send Authorization: Bearer $BUSABASE_API_KEY)

Codex can use the full Cloud MCP surface directly with standard OAuth:

bash
codex mcp add busabase --url https://busabase.com/api/mcpcodex 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

SkillWhat it does
busabaseDrive a Busabase workspace over HTTP: list Bases/records, propose ChangeRequests, and merge approved ones.
busabase-app-creatorTurn 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 manifestmcp.json                              Agent Plugins v1 hosted MCP profileskills/busabase/SKILL.md              canonical local/general-purpose skillskills/busabase-app-creator/SKILL.md  guided Busabase workspace and AirApp creator.claude-plugin/marketplace.json       Claude Code marketplace listingclaude/.claude-plugin/plugin.json     Claude Code plugin manifestclaude/.mcp.json                      hosted OAuth MCP profile for Claude Codeclaude/skills/busabase/SKILL.md       Claude-specific MCP-first connection guidanceclaude/skills/busabase-app-creator/   symlink to the shared app creator skill.agents/plugins/marketplace.json      Codex marketplace listingplugins/busabase/.codex-plugin/plugin.json   Codex plugin manifestplugins/busabase/.mcp.json                   hosted OAuth MCP profile for Codexplugins/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 dependencyplugins/busabase/assets/                     icons and light/dark logos bundled with Codex.mcp.json                             legacy/general-client local MCP profileserver.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.

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 releasesmcp-publisher login dns --domain busabase.com --private-key <KEY>   # verifies the com.busabase/* namespacemcp-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.

Source: README.md at commit dc4e4e5

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.