In-depth architectural comparison of the Mem0 MCP Selfhosted and Memograph 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
Mem0 MCP Selfhosted
Knowledge & Memory · Local stdio
Quality: 57/100 (Good) | Auth: other
Memograph
Knowledge & Memory · Local stdio
Quality: 57/100 (Good) | Auth: No auth required
Verdict Summary: Choose Mem0 MCP Selfhosted if you need specialized Knowledge & Memory tools running via a local process. Choose Memograph 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 Mem0 MCP Selfhosted when:
You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: other (Free / Open Source).
Mem0 MCP Selfhosted is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Memograph belongs to Knowledge & Memory using local stdio subprocess. Select Mem0 MCP Selfhosted when you need capabilities focused on knowledge & memory and Memograph when you require tools for knowledge & memory.
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).
Memograph Tools (39)
search_vault
Search memories in the MemoGraph vault using semantic or keyword search
create_memory
Create a new memory in the MemoGraph vault
query_with_context
Retrieve relevant context from the vault for a question. If LLM provider is configured, can optionally generate an answer. Otherwise, returns context for the client's LLM to use.
get_vault_info
Get information about the currently configured MemoGraph vault (path, name, configuration). Use this when you need to know which vault is being used.
get_vault_stats
Get statistics about the currently configured MemoGraph vault (memory counts, types, tags)
list_memories
List memories with optional filters
get_memory
Get full content of a specific memory by ID
import_document
Import a document (TXT, PDF, DOCX) into the vault
delete_memory
Delete a memory from the vault by ID
update_memory
Update an existing memory's title, content, tags, or salience
batch_update
Update multiple memories in one efficient operation. Much faster than calling update_memory multiple times.
batch_delete
Delete multiple memories in one efficient operation. Much faster than calling delete_memory multiple times.
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.
Graph-based memory system for LLMs with knowledge graphs and semantic search