In-depth architectural comparison of the Memory Arbiter Mcp and Statelessagent 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
Memory Arbiter Mcp
Knowledge & Memory · Local stdio
Quality: 44/100 (Fair) | Auth: No auth required
Statelessagent
Knowledge & Memory · Local stdio
Quality: 45/100 (Fair) | Auth: API Key required
Verdict Summary: Choose Memory Arbiter Mcp if you need specialized Knowledge & Memory tools running via a local process. Choose Statelessagent if your workspace requires Knowledge & Memory integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
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.
You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
Primary tools included: Provenance tracking and stale knowledge detection, Dual-layer memory with atomic fact extraction, 19 MCP tools for session handoffs, decisions, and search.
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
Memory with provenance tracking — records where agent knowledge originated and detects when sources change. 17 MCP tools for session handoffs, decisions, semantic search, and knowledge graph. Works across Claude Code, Cursor, Windsurf, Codex CLI, and Gemini CLI. Single Go binary, SQLite + vector search, fully local.
Category & Scope
Tools & Capabilities Breakdown
Memory Arbiter Mcp Tools (6)
Targeted memory retrieval with ranked relevant entries
Fact governance with source type, confidence, and user confirmation
Conflict detection and arbitration with explainable reasons
Versioning, supersede chains, and event time tracking
Local SQLite storage with no cloud or server-side LLM calls
Memory health diagnostics and repair tools
Statelessagent Tools (6)
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).
Memory Arbiter Mcp is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Statelessagent belongs to Knowledge & Memory using local stdio subprocess. Select Memory Arbiter Mcp when you need capabilities focused on knowledge & memory and Statelessagent when you require tools for knowledge & memory.