In-depth architectural comparison of the Agent Memory MCP and Mem0 MCP Selfhosted 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
Agent Memory MCP
Knowledge & Memory · Local stdio
Quality: 51/100 (Good) | Auth: No auth required
Mem0 MCP Selfhosted
Knowledge & Memory · Local stdio
Quality: 57/100 (Good) | Auth: other
Verdict Summary: Choose Agent Memory MCP if you need specialized Knowledge & Memory tools running via a local process. Choose Mem0 MCP Selfhosted 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 Agent Memory 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).
Markdown memory for AI agents. Files you can read, edit, grep, and commit. Not a database.
Self-hosted mem0 MCP server for Claude Code with Qdrant vector search, Neo4j knowledge graph, and Ollama embeddings. Zero-config OAT auth, split-model graph routing, session hooks for automatic cross-session memory, and 11 tools. Supports both Anthropic and fully local Ollama setups.
Agent Memory MCP is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Mem0 MCP Selfhosted belongs to Knowledge & Memory using local stdio subprocess. Select Agent Memory MCP when you need capabilities focused on knowledge & memory and Mem0 MCP Selfhosted when you require tools for knowledge & memory.
Receipt-required, target-bound, single-use.** Pass a Compliance Receipt from `check_action({action:'delete memory <name>', action_type:'deletions'})` — bound to that exact memory (via the `action_hash` caveat) and usable once. Soft-deletes to `.trash/<ts>-<name>.md`.
restore_memory
Restore a soft-deleted memory from `.trash/`. Picks the most recent trash entry for the name.
doctor
Storage integrity check. Reports orphans, dangling index entries, unreadable files. Pass `rebuild-index=true` to repair `MEMORY.md` from disk.
stats
Dashboard: counts per type, total size, largest memory, audit-log size, trash count.
log_events
Read recent entries from the audit event log. Optional `tail` (default 20) + `action` filter.
verify_memory
Re-evaluate a memory's claims. Extracts URLs/dates/file refs, flags stale-date signals, returns type-specific verification heuristics. Pairs with the `audit_stale` prompt.
find_backlinks
List memories that link to the given memory via `[[wiki-link]]` syntax in their bodies. Useful for "what references this" views.
+12 more tools listed on main page
Mem0 MCP Selfhosted Tools (11)
add_memory
Store text or conversation history as memories. Supports `enable_graph`, `infer`, `metadata`.
search_memories
Semantic search with optional `filters`, `threshold`, `rerank`, `enable_graph`.
get_memories
List/filter memories (non-search). Supports `limit` and scope filters.
get_memory
Fetch a single memory by UUID.
update_memory
Replace memory text. Re-embeds and re-indexes in Qdrant.
delete_memory
Delete a single memory by UUID.
delete_all_memories
Bulk-delete all memories in a scope.
list_entities
List users/agents/runs with memory counts. Uses Qdrant Facet API.
delete_entities
Cascade-delete an entity and all its memories.
search_graph
Search Neo4j entities by name substring. Returns entities + outgoing relationships.
get_entity
Get all relationships for an entity (bidirectional: incoming + outgoing).