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