Facthouse is a local memory engine for AI tools. Most “memory” products index chat logs. Facthouse takes agent activity - messages, tool use, and other MCP traffic - and applies…
facthouse is an MCP project maintained in the gordonkjlee/facthouse repository. The maintainer describes its purpose as “Facthouse is a local memory engine for AI tools. Most “memory” products index chat logs. Facthouse takes agent activity - messages, tool use, and other…”. Read the project documentation for the complete scope.
The documented npm package is @facthouse/mcp. The configuration below comes from the maintainer’s example; adapt its paths and account values to your environment.
The example declares FACTHOUSE_DATA. Secret-looking values have been replaced with placeholders. Required and optional labels are shown only when the documentation states them.
Project documentation · Repository · Discovery listing. This profile records the public documentation checked on 2026-10-08.
Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.
| Tool | What it does |
|---|---|
| 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… |
| get_entity | Everything known about any named subject — person, organisation, project, place, product — and how it connects. When several rows share the name under… |
| 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… |
| consolidate | Integrate pending facts into long-term knowledge. Extracts entities, resolves duplicates, detects contradictions, builds the knowledge graph. |
| get_schemas | Available domains and structure |
| get_stats | Fact count, entity count, domain distribution, extract backlog, intelligence spend |
{
"mcpServers": {
"facthouse-personal": {
"command": "npx",
"args": [
"-y",
"@facthouse/mcp@0.31.0"
],
"env": {
"FACTHOUSE_DATA": "C:\\Users\\alex\\.facthouse-personal"
}
}
}
}From the project documentation. Replace placeholders and example paths before connecting.
| Variable | Description | Required |
|---|---|---|
| FACTHOUSE_DATA | Declared in the maintainer’s client configuration. | Check documentation |
Inspect PostgreSQL schemas and run read-only queries with the archived MCP reference server. Review its maintenance status before choosing it.
Connect the Notion MCP server to search workspace content and work with pages and databases through Notion’s hosted OAuth service.
Use the Supabase MCP server to inspect database schemas, query project data and retrieve docs through a project-scoped connection.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.