
Busabase
com.busabase由 busabase.com 發布官方發布者v0.1.1更新於 Oct 28, 2026
Database for your AI agent. Turn its output into data, docs, skills, and apps you can actually use.
概覽
Busabase 是為 AI 代理打造的託管資料庫與工作空間,讓助理列出 Base 與紀錄、提出變更請求,並建立工作空間應用程式。
- 可以做什麼
- 列出工作空間中的 Base 與紀錄
- 提出附有說明與差異的變更請求,並合併已核准的請求
- 把代理輸出轉化為資料、文件、技能與應用程式
- 建立含原生資源與可審閱 AirApp 的完整工作空間應用程式
- 透過隨附的技能與外掛以 HTTP 方式操作工作空間
- 適用情境
- 當你希望代理在 Busabase 工作空間中儲存與管理結構化資料,或把輸出變成可審閱的應用程式與文件時使用。適合希望代理每次寫入都經過附差異的變更請求、並可選擇人工審核的團隊。
- 執行需求
- 需要遠端 Streamable HTTP 端點:託管端點為 busabase.com/api/mcp,本機端點為 localhost:15419/api/mcp(無需驗證)。託管端點需要瀏覽器 OAuth 登入,或以 Authorization Bearer 標頭攜帶 Busabase API 金鑰。可選安裝方式包括 npx skills、Claude Code 外掛或 Codex 外掛。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 Busabase,將其新增到工作區。
- 連接 所需的 憑證。它們會被私密儲存,絕不會在公開頁面上展示。
- 為需要使用其工具的對話啟用該服務。
Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。
交給代理程式安裝
把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。
閱讀 https://sourceweft.com/mcp/com.busabase%2Fbusabase/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。其他 MCP 客戶端
把它新增到你客戶端的 mcpServers 設定中。 客戶端會在首次連接時完成 OAuth 登入。
{
"mcpServers": {
"busabase": {
"type": "http",
"url": "https://busabase.com/api/mcp"
}
}
}README
Busabase 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)
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
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
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.
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:
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
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:
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
Bump version in server.json only when publishing an MCP Registry update. Bump the Codex plugin
manifest independently for GitHub marketplace releases.
來源:README.md,提交 dc4e4e5
工具
0版本歷史
1- v0.1.1最新Sep 16, 2026
評分
已滿足適用檢查項的 75%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通必需25 分
- 已宣告認證方式必需10 分
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分
請在儲存庫或註冊中心條目中宣告授權條款。