B
busabase/busabase
Local database and workspace where agents store data and skills
在 GitHub 查看 ↗链接已于 2026-11-12 核查 · HTTP 200 · 打开的是厂商自己的官网
安装与配置
- 复制上面的命令
- 粘成
claude_desktop_config.json里mcpServers的一项（本地服务器用 command + args，示例见 客户端接法） - 重启客户端
客户端配置（取自该仓库的安装命令）
{
"mcpServers": {
"busabase-busabase": {
"command": "npx",
"args": ["-y", "busabase@latest"]
}
}
}解析自我们于 2026-11-04 抓取的该仓库 README；我们未执行过。
command/args 来自仓库写明的安装命令；不确定时请以该项目 README 为准。
VS Code（.vscode/mcp.json —— 键名是 servers）
{
"servers": {
"busabase-busabase": {
"command": "npx",
"args": ["-y", "busabase@latest"]
}
}
}VS Code 顶层键是 <code>servers</code>，其余与上面那份相同。
Claude Code（命令行）
claude mcp add --transport stdio busabase-busabase -- npx -y busabase@latest
Claude Code 不收 JSON 文件，用这条命令直接加。
配置项的键名以你的客户端为准：客户端与 CLI
- 来源明细
- 收录自 abordage/awesome-mcp 榜单（我们从中收集的条目之一） · 条目类型：MCP 服务
- 收录与活跃
- 收录于 2026-11-05 · 最近见到 2026-11-14 · 共见到 10 次 · 被 10 个来源列出
- 评分构成
- 综合分 1,003 · 10 个来源 · mcp
- 安装
npx -y busabase@latest
常见问题（答案都来自我们的记录）
怎么安装？
该仓库给出的安装命令是
npx -y busabase@latest。我们的记录里它是仓库自己提供的；不保证在你的客户端上直接可用。它适合谁 / 用来做什么？
我们把它归在这些标签下: MCP 服务。标签来自条目自身，不是我们强加的分类。
谁维护它、还在更新吗？
我们收录于 2026-11-05；最近见到 2026-11-14。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。
Busabase
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
Suggested pronunciation: /ˈbuː.sə.beɪs/
The System of Record for AI Agents
Different agents. One shared base.
The open-source database & workspace where Claude Code, Codex, Cursor, and your own agents keep the records, docs, skills, and apps the next task builds on.
中文 ·
日本語 ·
한국어
Quick Start ·
Features ·
Connect an Agent ·
Use Cases ·
Docs ·
Community
> Busabase is an open-source database and workspace for AI agents — agents and people share the same structured data, docs, skills, and apps, and writes that matter become reviewed, trusted records.
Every agent session starts from zero. Your CLAUDE.md lives in one repo, the best output dies in a chat, and switching tools means explaining the project all over again.
Busabase keeps the agents stateless and the work durable: connect any agent, and it reads the same records, docs, skills, and apps your team and other agents already left behind — then writes its own work back, with a diff and a history.
## Quick Start
bash
npx -y busabase@latest server
Open http://localhost:15419/dashboard/local — no database, account, or config. It starts with embedded PGlite, local file storage, and a demo workspace.
Then point your agent at it. Paste into Claude Code, Codex, Cursor, Gemini CLI, or any agent that can read a URL:
text
Read and follow the Busabase Agent Skill — it is the single source of truth:
http://localhost:15419/SETUPSKILL.md
Follow its onboarding to connect to this workspace. Don't choose a merge policy yourself unless I ask for one — submit the change and let Busabase apply my permissions to decide whether it merges now or waits for review. Reply to me in English.
Try this: have one agent record a project's updates and conventions, then open a different agent and ask "What changed on this project this week?" It answers from the workspace, not from your clipboard.
Docker · Desktop · global install · from source
bash
# Docker (Docker Hub: busabase/busabase · GHCR: ghcr.io/busabase/busabase)
docker run --rm -p 15419:15419 -v ~/.busabase/data:/data busabase/busabase
# Global install
npm i -g busabase # then: busabase server
npx busabase-cli --help # API client for any Busabase server
# From source
pnpm install
cp apps/busabase/.env.example apps/busabase/.env
pnpm --filter busabase dev
Desktop for macOS, Windows, and Linux: busabase.com/download — runs locally and works offline.
Local data lives in ~/.busabase/data/ (pgdata/ for the embedded PGlite database, storage/ for files). Set BUSABASEDATADIR, PGDATABASEURL, or STORAGEURL to use another location, external Postgres, or S3-compatible storage. Only one process can hold the same PGlite database at a time.
## Features
One workspace for every kind of agent output — Bases (typed records, relations, views, forms), Docs, Files, Drives, Skills, AirApps, Whiteboards, and Workflows as first-class nodes in one tree. Node types →
Shared skills across agents — keep SKILL.md playbooks and custom prompts in the workspace. Playbooks collects them into one catalog every connected agent can look up before it acts.
Every write accounted for — agent writes travel as Change Requests with a message, a field-level diff, an author, and history. Permissions decide whether a change merges on the spot or waits for review.
The System of Record for AI Agents
Different agents. One shared base.
The open-source database & workspace where Claude Code, Codex, Cursor, and your own agents keep the records, docs, skills, and apps the next task builds on.
中文 ·
日本語 ·
한국어
Quick Start ·
Features ·
Connect an Agent ·
Use Cases ·
Docs ·
Community
> Busabase is an open-source database and workspace for AI agents — agents and people share the same structured data, docs, skills, and apps, and writes that matter become reviewed, trusted records.
Every agent session starts from zero. Your CLAUDE.md lives in one repo, the best output dies in a chat, and switching tools means explaining the project all over again.
Busabase keeps the agents stateless and the work durable: connect any agent, and it reads the same records, docs, skills, and apps your team and other agents already left behind — then writes its own work back, with a diff and a history.
## Quick Start
bash
npx -y busabase@latest server
Open http://localhost:15419/dashboard/local — no database, account, or config. It starts with embedded PGlite, local file storage, and a demo workspace.
Then point your agent at it. Paste into Claude Code, Codex, Cursor, Gemini CLI, or any agent that can read a URL:
text
Read and follow the Busabase Agent Skill — it is the single source of truth:
http://localhost:15419/SETUPSKILL.md
Follow its onboarding to connect to this workspace. Don't choose a merge policy yourself unless I ask for one — submit the change and let Busabase apply my permissions to decide whether it merges now or waits for review. Reply to me in English.
Try this: have one agent record a project's updates and conventions, then open a different agent and ask "What changed on this project this week?" It answers from the workspace, not from your clipboard.
Docker · Desktop · global install · from source
bash
# Docker (Docker Hub: busabase/busabase · GHCR: ghcr.io/busabase/busabase)
docker run --rm -p 15419:15419 -v ~/.busabase/data:/data busabase/busabase
# Global install
npm i -g busabase # then: busabase server
npx busabase-cli --help # API client for any Busabase server
# From source
pnpm install
cp apps/busabase/.env.example apps/busabase/.env
pnpm --filter busabase dev
Desktop for macOS, Windows, and Linux: busabase.com/download — runs locally and works offline.
Local data lives in ~/.busabase/data/ (pgdata/ for the embedded PGlite database, storage/ for files). Set BUSABASEDATADIR, PGDATABASEURL, or STORAGEURL to use another location, external Postgres, or S3-compatible storage. Only one process can hold the same PGlite database at a time.
## Features
One workspace for every kind of agent output — Bases (typed records, relations, views, forms), Docs, Files, Drives, Skills, AirApps, Whiteboards, and Workflows as first-class nodes in one tree. Node types →
Shared skills across agents — keep SKILL.md playbooks and custom prompts in the workspace. Playbooks collects them into one catalog every connected agent can look up before it acts.
Every write accounted for — agent writes travel as Change Requests with a message, a field-level diff, an author, and history. Permissions decide whether a change merges on the spot or waits for review.
收录徽章（可选）
想把收录标记放进 README 就复制这行，可选，不影响收录。
[](https://anclum.com/zh/s/busabase-busabase/)
- 来源
- awesome · https://github.com/busabase/busabase
- 按领域浏览
- MCP 服务
- 收录来源
- 10 个独立来源
- 收录于
- 今天
同类推荐
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。