Weasley DeepMind vs Butterbase Oss

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

Weasley DeepMind logoWeasley DeepMindKnowledge & Memory · Local subprocess (stdio)Secure, fragment-based long-term memory for MCP-compatible AI agents.43FairAuth: 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 Weasley DeepMind for knowledge & memory work as a local process; 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?

Weasley DeepMind logoChoose Weasley DeepMind when

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

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.

SpecWeasley DeepMind logoWeasley DeepMindButterbase Oss logoButterbase Oss
CategoryKnowledge & MemoryKnowledge & Memory
Quality signal43/100 · Fair51/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars43,031
Directory activity 2 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Weasley DeepMind 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.

Weasley DeepMind

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "weasley-deepmind": {
      "command": "npx",
      "args": [
        "-y",
        "weasley-deepmind"
      ]
    }
  }
}

Butterbase Oss

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

Frequently asked questions

Weasley DeepMind is categorized under Knowledge & Memory and uses a local stdio subprocess. Butterbase Oss belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Weasley DeepMind 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.

Weasley DeepMind 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 weasley-deepmind and mcp-285 as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Weasley DeepMind has a quality signal of 43/100 (Fair) with 2 views, 0 installs and 4 GitHub stars. Butterbase Oss has 51/100 (Good) with 2 views, 0 installs and 3,031 GitHub stars.