# Keep facts in a small local graph the agent reads back

> Keep facts in a small local graph the agent reads back: 0 companies fully do it, 1 with a limit, 17 carry the tag. Every listing in Databases & files with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/data.memory-graph/
- Markdown: https://www.anchorterminal.com/niches/data.memory-graph/index.md (~1,000 tokens)
- Slim: https://www.anchorterminal.com/niches/data.memory-graph/index.min.md (~230 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/data.memory-graph/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 0 | 1 | 17 | 7 | 4 |

## What counts as done

Entities, relations and observations are written to a file at a path the person chose, survive a reinstall, come back by name or search in a later session, and no write from another process is lost.

Measured, for our own tests: a search on a 1,000-entity graph returns under 5,000 tokens.

How agents ask for it: remember that Alice owns the billing service; what do we know about project X; note this decision for next time

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **Memory (MCP reference server) (Model Context Protocol, a Series of LF Projects, LLC)**: MEMORY_FILE_PATH sets the file, saves are atomic, a lock file serialises writers across processes (fixing #4797), and search_nodes takes limit and observationLimit. The default path still sits in node_modules, which a reinstall can delete.

- not this job: Mirage (AgentVFS) (Strukto.AI): No entity or relation store; files only.
- not this job: ClickHouse MCP Server (ClickHouse, Inc.): No entity or memory store.
- not this job: CoinMarketCap x402 API (CoinMarketCap): No store the agent writes to.
- not this job: DBHub (Bytebase): No entity or memory store; it queries existing databases.
- not this job: Filesystem (MCP reference server) (Model Context Protocol, a Series of LF Projects, LLC): Reads and writes files; no entity, relation or search-by-name store.
- not this job: MCP Toolbox for Databases (Google LLC): No memory store.
- not this job: MongoDB MCP Server (MongoDB, Inc.): No memory or graph store of its own.
- not this job: Nansen x402 API (Nansen): No store the agent writes to.
- not this job: Neon MCP Server (Neon, LLC (subsidiary of Databricks, Inc.)): No memory store.
- not this job: ObsessionDB (Kellerkind UG (haftungsbeschränkt)): No memory store.
- not this job: PlanetScale MCP Server (PlanetScale, Inc.): No memory store.
- not this job: Postgres MCP Pro (Crystal Corp.): No memory store.
- not this job: Redis MCP (Redis Ltd.): Stores keys and JSON in Redis, not entities and relations in a file at a chosen path.
- not this job: ReqRes MCP server (ReqRes): Generic JSON records, not a local graph file.
- not this job: Snowflake-managed MCP server (Snowflake Inc.): No memory store.
- not this job: Supabase API + MCP (Supabase Pte. Ltd.): No memory graph store.

## What stops agents finishing

- default file location inside a package cache that a reinstall removes
- two processes overwrite each other's writes

## Around it

Before: agent-memory.store-and-confirm. After: agent-memory.user-facts-recall.

## Where this comes from

Weight 7 of 100 in Databases & files: 4 of 52 accounts on the memory reference server; agent-memory has its own map, so kept small here

As data: https://www.anchorterminal.com/api/v1/use-cases/data.memory-graph.json, or the MCP tool get_use_case with id data.memory-graph. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
