Agentmem vs Agentkits Memory — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Agentmem vs Agentkits Memory
In-depth architectural comparison of the Agentmem and Agentkits Memory 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
Agentkits Memory
Knowledge & Memory · Local stdio
Quality: 55/100 (Good) | Auth: No auth required
Verdict Summary: Choose Agentmem if you need specialized Knowledge & Memory tools running via a local process. Choose Agentkits Memory 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 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]
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.
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
Agentkits Memory Tools (6)
SQLite-backed local persistence
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, Agentkits Memory belongs to Knowledge & Memory using local stdio subprocess. Select Agentmem when you need capabilities focused on knowledge & memory and Agentkits Memory when you require tools for knowledge & memory.