In-depth architectural comparison of the Agentkits Memory 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
Agentkits Memory
Knowledge & Memory · Local stdio
Quality: 55/100 (Good) | Auth: No auth required
Memory Arbiter MCP
Knowledge & Memory · Remote HTTP/SSE
Quality: 61/100 (Good) | Auth: No auth required
Verdict Summary: Choose Agentkits Memory 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 Agentkits Memory 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-backed local persistence, FTS5 and vector semantic search, Automatic session and tool-usage capture.
Persistent memory for AI coding assistants with hybrid search (FTS5 + vector embeddings), session tracking, automatic context hooks, and web viewer. SQLite-based with no daemon process — works with Claude Code, Cursor, Windsurf, and any MCP client.
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
Agentkits Memory Tools (6)
SQLite-backed local persistence
FTS5 and vector semantic search
Automatic session and tool-usage capture
Nine MCP memory-management tools
Local multilingual embeddings
Web viewer for memory administration
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).
Agentkits Memory 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 Agentkits Memory 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.