Agentmem vs Memory Arbiter MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Agentmem vs Memory Arbiter MCP
In-depth architectural comparison of the Agentmem and Memory Arbiter MCP 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.
At a Glance & Executive Verdict
Agentmem
Knowledge & Memory · Local stdio
Quality: 48/100 (Fair) | Auth: No auth required
Memory Arbiter MCP
Knowledge & Memory · Remote HTTP/SSE
Quality: 61/100 (Good) | Auth: No auth required
Verdict Summary: Choose Agentmem if you need specialized Knowledge & Memory tools running via a local process. Choose Memory Arbiter MCP if your workspace requires Knowledge & Memory integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Agentmem 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: SQLite and FTS5 local storage, Trust lifecycle for memory records, Conflict and staleness detection.
Governed memory for coding agents with trust lifecycle (hypothesis → active → validated → deprecated), conflict detection, staleness tracking, and health scoring. SQLite + FTS5, zero infrastructure. pip install quilmem[mcp]
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
Category & Scope
Tools & Capabilities Breakdown
Agentmem Tools (6)
SQLite and FTS5 local storage
Trust lifecycle for memory records
Conflict and staleness detection
Health scoring
Provenance-aware markdown synchronization
Built-in MCP, Python, and CLI interfaces
Memory Arbiter MCP Tools (4)
memory
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).
Agentmem is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Memory Arbiter MCP belongs to Knowledge & Memory using remote streaming HTTP/SSE transport. Select Agentmem when you need capabilities focused on knowledge & memory and Memory Arbiter MCP when you require tools for knowledge & memory.
Explicit user-authorized governance: retire a whole memory, resolve a conflict, confirm a memory, correct a judgment, and govern workspace aliases / pending workspaces. Do not use for ordinary updates.
memory_repair
Maintenance and repair: split, rebuild claims/embeddings, cleanup, vector resync, entity backfill, and pending activation. Prefer dry-run first.