I asked Claude for its own project history — from AI memory over MCP only
Claude is given a persistent memory substrate over MCP and asked to recall the history of its own project using memory alone — no context, no RAG. It reports what it does not know and cites a tombstoned atom to prove it.
About this video
An agent is connected to a Parametric Memory substrate over MCP and then asked, using memory alone, to recount the history of the project it has been working on. No documents are supplied, no retrieval-augmented pipeline is involved, and nothing is pasted into the context window.
What comes back at 3:55 is the part worth watching. The agent reports not only what it remembers but what it cannot know — the substrate's record begins on a specific date, and an atom that had claimed an earlier launch was tombstoned. It cites the tombstone as evidence. An agent that can distinguish 'I do not know' from 'this did not happen' is behaving very differently from one that confabulates to fill a gap.
The second half walks through what the same substrate does day to day: re-establishing context in a fresh coding session, backing operational work, and holding a knowledge store whose value compounds as it grows.
What you’ll see
- ▸Recall performed entirely over MCP tool calls, with no context priming and no RAG pipeline
- ▸Tombstoned atoms let the agent state what it does not know, and show why
- ▸Knowledge stored as atoms with typed edges, committed to a SHA-256 Merkle tree so every read carries a proof
- ▸Three worked use cases: re-contexting a coding session, an operations substrate, and a compounding knowledge store
- ▸Ingest once, query from every project — the marginal cost of the next check approaches zero
Chapters
- 0:00Intro
- 0:07The premise: AI memory over MCP, nothing else
- 1:55The prompt — give me the history of the substrate
- 2:30Claude searches its own memory (MCP tool calls)
- 3:55What it remembers — and what it cannot (tombstoned atoms)
- 6:40Use case 1: an L2 cache for coding, re-contexting a new session
- 9:40Use case 2: an operations substrate
- 11:10Use case 3: a knowledge store that compounds