B
busabase/busabase
Local database and workspace where agents store data and skills
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
Install & config
- Copy the command above
- Paste it as one entry under
mcpServersinclaude_desktop_config.json— local servers take command + args (example: clients) - Restart your client
Client config (built from the install command this repo gives)
{
"mcpServers": {
"busabase-busabase": {
"command": "npx",
"args": ["-y", "busabase@latest"]
}
}
}Parsed from the README we fetched on 2026-11-04; we have not executed it.
command/args come from the install command the repository states. When it is ambiguous, the project README wins.
VS Code (.vscode/mcp.json - the key is servers)
{
"servers": {
"busabase-busabase": {
"command": "npx",
"args": ["-y", "busabase@latest"]
}
}
}Same server, but VS Code keeps it under <code>servers</code>.
Claude Code (command line)
claude mcp add --transport stdio busabase-busabase -- npx -y busabase@latest
Claude Code does not read a config file; add the server with this command.
Key names differ by client: Clients & CLI
- Source
- collected from the abordage/awesome-mcp list · type: MCP server
- Harvest history
- first seen 2026-11-05 · last seen 2026-11-14 · seen 10× · listed by 10 sources
- Score
- score 1,003 · 10 sources · mcp
- Install
npx -y busabase@latest
FAQ (answers come from our records)
How do I install it?
The repository provides this install command:
npx -y busabase@latest. It comes from the repository itself; we cannot guarantee it runs as-is in your client.Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
first catalogued 2026-11-05；last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.
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.
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/busabase-busabase/)
- Source
- awesome · https://github.com/busabase/busabase
- Browse by field
- MCP servers
- Listed by
- 10 independent sources
- added
- today
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.