Butterbase Oss vs Project MCP
A side-by-side look at the Butterbase Oss and Project MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Butterbase Oss for knowledge & memory work as a local process; choose Project MCP 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 Butterbase Oss when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
Choose Project MCP when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
search_project, search_docs, get_doc.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Knowledge & Memory | Knowledge & Memory |
| Quality signal | 51/100 · Good | 64/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 3,031 | 9 |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 42 |
| Full listing | View Butterbase Oss | View Project MCP |
Tools & capabilities
Butterbase Oss tools
No tool names declared yet. Check the project README from the listing page.
Project MCP tools 42
search_projectSearch across project sources with smart intent detection. IMPORTANT: "project docs" means APPLICATION documentation (docs/ + DECISIONS.md), NOT project management. Use intent "project_docs" when user says "project docs/documents/documentation" to search application documentation. Use intent "plan" for project management (status, todos, roadmap, backlog).search_docsSearch only the docs/ directory for reference documentation. Use this when the user specifically asks for "docs" or "documentation". Returns relevant documentation chunks with file paths and content snippets.get_docGet the full content of a specific file. Supports files from .project/, root-level, or docs/. Use the path as returned from search results.list_docsList all available documentation files organized by category. Use this to discover what documentation is available or to get an overview of the documentation structure.get_doc_structureGet the complete documentation directory structure with file paths and descriptions. Useful for understanding the organization of documentation.manage_project_fileSmart tool that automatically determines which project file to create or update based on context. Use this when making changes to the project - it will check project state and determine if index.md, ROADMAP.md, TODO.md, STATUS.md, or DECISIONS.md should be created/updated. This is the primary tool for managing project documentation during development.check_project_stateChecks the current state of project management files. Returns which files exist (.project/index.md, ROADMAP.md, TODO.md, STATUS.md, DECISIONS.md) and provides a summary of project state. Use this before making changes to understand what exists.create_or_update_roadmapCreates or updates the ROADMAP.md file in .project/ directory. Use this when planning future work, milestones, or phases. If the file exists, intelligently merges new content with existing roadmap.create_or_update_todoCreates or updates the TODO.md file in .project/ directory. Use this when adding tasks, marking items complete, or updating task status. Intelligently organizes tasks into sections (In Progress, Next Up, Blocked, Completed).create_or_update_statusCreates or updates the STATUS.md file in .project/ directory. Use this when updating project health, recent changes, metrics, or current phase. Automatically updates the "Last Updated" timestamp.create_or_update_indexCreates or updates the index.md file in .project/ directory. This is the contract file that defines how agents should interpret sources. Use this when setting up project structure or updating source mappings.create_or_update_decisionsCreates or updates the DECISIONS.md file in .project/ directory. Use this when documenting architecture decisions, trade-offs, or rationale. Helps maintain a decision log for the project.- +30 more on 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.
Butterbase Oss
{
"mcpServers": {
"mcp-285": {
"command": "npx",
"args": [
"-y",
"@butterbase/mcp"
]
}
}
}
Project MCP
{
"mcpServers": {
"project-mcp": {
"command": "npx",
"args": [
"-y",
"project-mcp"
]
}
}
}
Frequently asked questions
Butterbase Oss is categorized under Knowledge & Memory and uses a local stdio subprocess. Project MCP belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Butterbase Oss for knowledge & memory work and Project MCP for knowledge & memory.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Butterbase Oss has no declared pricing — check the project's own site. Project MCP is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add mcp-285 and project-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Butterbase Oss has a quality signal of 51/100 (Good) with 2 views, 0 installs and 3,031 GitHub stars. Project MCP has 64/100 (Good) with 0 views, 0 installs and 9 GitHub stars.