In-depth architectural comparison of the Mem0 MCP Selfhosted and Facthouse 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
Facthouse
Knowledge & Memory · Local stdio
Quality: 52/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 Facthouse 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).
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.
A local memory engine any AI tool can use. Not Mem0's hosted OpenMemory MCP.
Mem0 MCP Selfhosted is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Facthouse belongs to Knowledge & Memory using local stdio subprocess. Select Mem0 MCP Selfhosted when you need capabilities focused on knowledge & memory and Facthouse 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).
Facthouse Tools (10)
log_event
Log conversation events (messages, artifacts).
get_events
Retrieve events from current or previous session.
get_session_context
Working briefing (the same markdown as `memory://briefing`) plus facts captured in this session. Call at the start of every conversation if the client does not load resources.
get_entity
Everything known about any named subject — person, organisation, project, place, product — and how it connects. When several rows share the name under different types, facts from all of them come back. Hyphens, underscores, and stray punctuation count as the same letters only when that does not joi…
get_context
Everything relevant to a topic (search + entity traversal)
search_knowledge
Hybrid search across integrated knowledge
capture_fact
Store a fact. On a copy store this is a correction for something extraction missed; on a store with empty `sources` it is how facts get in. The description the assistant sees is generated from that same rule.
consolidate
Integrate pending facts into long-term knowledge. Extracts entities, resolves duplicates, detects contradictions, builds the knowledge graph.