Memory Arbiter Mcp vs Deja Vu

In-depth architectural comparison of the Memory Arbiter Mcp and Deja Vu 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 local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• You have access to required keys: MEMORY_ARBITER_TOOL_PROFILE.
• Primary tools included: Targeted memory retrieval with ranked relevant entries, Fact governance with source type, confidence, and user confirmation, Conflict detection and arbitration with explainable reasons.

Explore Memory Arbiter Mcp Details

Choose Deja Vu 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: Zero-dependency single binary, fully local operation, Search 3.5 GB of session history in ~1.5 ms, Supports multiple coding agents via MCP protocol.

Feature & Specification Comparison

Specification	Memory Arbiter Mcp billy12151 Knowledge & Memory	Deja Vu vshulcz 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	Local memory layer over the session histories coding agents already write (Claude Code, Codex CLI, opencode): lexical search, recall tools, session-start auto-recall, secret redaction at index time, cross-machine sync over SSH.
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": {
      "command": "uvx",
      "args": [
        "memory-arbiter-mcp"
      ],
      "env": {
        "MEMORY_ARBITER_TOOL_PROFILE": "YOUR_MEMORY_ARBITER_TOOL_PROFILE_HERE"
      }
    }
  }
}

{
  "mcpServers": {
    "vshulcz-deja-vu": {
      "command": "npx",
      "args": [
        "-y",
        "@vshulcz/deja-vu"
      ]
    }
  }
}

Related MCP Server Comparisons