Mwe Mcp — Memory Wiki Engine vs Butterbase Oss

In-depth architectural comparison of the Mwe Mcp — Memory Wiki Engine and Butterbase Oss MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

Choose Mwe Mcp — Memory Wiki Engine when:

• You need dedicated capabilities in the Knowledge & Memory domain.
• You prefer remote streaming HTTP/SSE transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore Mwe Mcp — Memory Wiki Engine Details

Choose Butterbase Oss when:

• You need dedicated capabilities in the Knowledge & Memory domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore Butterbase Oss Details

Feature & Specification Comparison

Specification	Mwe Mcp — Memory Wiki Engine Knowledge & Memory	Butterbase Oss butterbase-ai Knowledge & Memory
Summary	Self-hosted multi-user memory for AI agents: a human-readable Markdown wiki with per-fragment ACL.	Butterbase MCP server — manage your backend: schemas, auth, functions, storage, RAG, deploys.
Category & Scope	Knowledge & Memory

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "mwe-mcp-memory-wiki-engine": {
      "url": "http://127.0.0.1:8742/mcp"
    }
  }
}

{
  "mcpServers": {
    "mcp-285": {
      "command": "npx",
      "args": [
        "-y",
        "@butterbase/mcp"
      ]
    }
  }
}

Related MCP Server Comparisons