Memory Arbiter MCP vs Mnemos

In-depth architectural comparison of the Memory Arbiter MCP and Mnemos 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 Memory Arbiter MCP 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).
• You have access to required keys: MEMORY_ARBITER_CLIENT, MEMORY_ARBITER_AGENT_ID, MEMORY_ARBITER_MCP_TRANSPORT.
• Primary tools included: memory, memory_review, memory_govern.

Explore Memory Arbiter MCP Details

Choose Mnemos 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).
• Primary tools included: mnemos_store, mnemos_search, mnemos_context.

Feature & Specification Comparison

Specification	Memory Arbiter MCP billy12151 Knowledge & Memory	Mnemos s60yucca Knowledge & Memory
Summary	AI enhancement middleware: precise retrieval replaces full-memory loading (80%+ token cut), rule-based conflict arbitration with explainable reasons, and one local SQLite shared across Claude Code/Codex/Cursor/ZCode. Local-first, zero cloud, MIT. pip install memory-arbiter-mcp	Persistent memory engine for AI coding agents. Stores architecture decisions, bug root causes, and project conventions across sessions. Single Go binary with embedded SQLite, FTS5 search, context assembly within token budgets, and autopilot setup for Claude Code, Kiro, and Cursor.
Category & Scope

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": {
    "billy12151-memory-arbiter-mcp": {
      "url": "http://127.0.0.1:8000/mcp"
    }
  }
}

{
  "mcpServers": {
    "s60yucca-mnemos": {
      "command": "npx",
      "args": [
        "-y",
        "@s60yucca/mnemos"
      ]
    }
  }
}

Related MCP Server Comparisons