Codeledger vs Butterbase Oss

A side-by-side look at the Codeledger and Butterbase Oss MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Codeledger logoCodeledgerKnowledge & MemoryDeterministic context selection for AI coding agents. Local memory that compounds across sessions.36FairAuth: not declaredButterbase Oss logoButterbase OssKnowledge & Memory · Local subprocess (stdio)Butterbase MCP server — manage your backend: schemas, auth, functions, storage, RAG, deploys.51GoodAuth: not declared

Verdict: choose Codeledger for knowledge & memory work; 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?

Codeledger logoChoose Codeledger when

  • You need dedicated capabilities in the Knowledge & Memory domain.
Explore Codeledger

Butterbase Oss logoChoose Butterbase Oss when

  • You need dedicated capabilities in the Knowledge & Memory domain.
  • You prefer a local stdio subprocess transport.
Explore Butterbase Oss

Feature & specification comparison

Rows where the two servers differ are marked.

SpecCodeledger logoCodeledgerButterbase Oss logoButterbase Oss
CategoryKnowledge & MemoryKnowledge & Memory
Quality signal36/100 · Fair51/100 · Good
Install commandNot confirmed yetConfirmed
Transport—Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars83,030
Directory activity 1 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Codeledger 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.

Codeledger

No confirmed install command for Codeledger yet — follow the setup steps linked from its listing page rather than a guessed package name.

Butterbase Oss

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "mcp-285": {
      "command": "npx",
      "args": [
        "-y",
        "@butterbase/mcp"
      ]
    }
  }
}

Frequently asked questions

Codeledger is categorized under Knowledge & Memory and uses an install path we have not confirmed yet. Butterbase Oss belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Codeledger for knowledge & memory work and Butterbase Oss 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. Codeledger has no confirmed install command yet — follow its own setup instructions.

Codeledger has no declared pricing — check the project's own site. Butterbase Oss has no declared pricing — check the project's own site. 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 codeledger and mcp-285 as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Codeledger has a quality signal of 36/100 (Fair) with 1 views, 0 installs and 8 GitHub stars. Butterbase Oss has 51/100 (Good) with 2 views, 0 installs and 3,030 GitHub stars.