Busabase vs Butterbase Oss
A side-by-side look at the Busabase and Butterbase Oss MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Busabase for knowledge & memory work over a hosted endpoint; choose Butterbase Oss for knowledge & memory as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Busabase when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a remote HTTP/SSE transport.
Choose Butterbase Oss when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Knowledge & Memory | Knowledge & Memory |
| Quality signal | 41/100 · Fair | 51/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2 | 3,031 |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Busabase | View Butterbase Oss |
Tools & capabilities
Busabase tools
No tool names declared yet. Check the project README from the listing page.
Butterbase Oss tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Busabase
{
"mcpServers": {
"busabase": {
"url": "https://busabase.com/api/mcp"
}
}
}
Butterbase Oss
{
"mcpServers": {
"mcp-285": {
"command": "npx",
"args": [
"-y",
"@butterbase/mcp"
]
}
}
}