Atlas Mind vs Butterbase Oss

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

Atlas Mind logoAtlas MindKnowledge & Memory · Local subprocess (stdio)Self-hosted git-native knowledge base with an MCP endpoint your AI reads, writes and rewinds37FairAuth: 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 Atlas Mind 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?

Atlas Mind logoChoose Atlas Mind when

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

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.

SpecAtlas Mind logoAtlas MindButterbase Oss logoButterbase Oss
CategoryKnowledge & MemoryKnowledge & Memory
Quality signal37/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 stars33,031
Directory activity 0 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Atlas Mind 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.

Atlas Mind

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "atlas-mind": {
      "command": "uvx",
      "args": [
        "atlas-mind"
      ]
    }
  }
}

Butterbase Oss

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

Frequently asked questions

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

Atlas Mind 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 atlas-mind and mcp-285 as separate keys in the same mcpServers object, and your assistant will call tools from either one.

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