Volume 01 · Issue 01 · 2026
A second brain
that survives
model changes.
Self-hosted temporal-knowledge-graph memory for AI agents. Not a flat fact store — entities, relationships, and bi-temporal validity. Your graph remembers when something was true.
Powered by Graphiti on FalkorDB. Remote-MCP from day one.
§ What it remembers
Six fact archetypes,
infinitely composable.
Whatever you put into add_memory, Graphiti extracts entities and relationships under your custom schema.
- 01Person → Companyworks at"Albert works at Krea"
- 02Company → Projectships"Krea ships agent-memory"
- 03Decision → Reasoningbecause"Picked FalkorDB because Cypher + property graphs"
- 04Person → Preferenceprefers"Diego prefers vim over emacs"
- 05Project → Tooluses"agent-memory uses Graphiti"
- 06Goal → Personowned by"Q1 audit log → Albert"
§ Why bi-temporal
Two clocks, not one.
Every fact has a valid window (when it was true in the world) and an ingest time (when you learned it). Update a fact and the previous version isn't deleted — it's invalidated, with the timestamp as the witness.
Result: scrub the timeline and watch your graph reconfigure. No bug-prone "edit then forget what you used to think." History is queryable.
§ Connect
One MCP URL,
any client.
Drop into Claude Desktop, openclaw, Cursor, Claude Code. Same bearer key works everywhere. Tenant-scoped server-side; clients can't set their own group_id.
# Claude Code
$ claude mcp add agent-memory https://your.host/mcp/ \
--transport http --scope user \
--header "Authorization: Bearer ak_..."
# Or cmdline
$ curl -H "Authorization: Bearer ak_..." \
"https://your.host/v1/graph?limit=200"Six tools exposed. Three blocked at the proxy for tenant safety.
Give your agent continuity.
Free while in beta. Open source. Bring your own Supabase + your own keys.