Keep facts in a small local graph the agent reads back
No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.
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. No docs we read state these figures, so they don't count against a listing here.
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 1
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.
| Listing | Why |
|---|---|
| Memory (MCP reference server) B 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. source |
Doesn't do this job 16
Listings in the category that do something else, with the reason.
| Listing | Why |
|---|---|
| Mirage (AgentVFS) B Strukto.AI | No entity or relation store; files only. |
| ClickHouse MCP Server BB ClickHouse, Inc. | No entity or memory store. |
| CoinMarketCap x402 API BB CoinMarketCap | No store the agent writes to. source |
| DBHub BB Bytebase | No entity or memory store; it queries existing databases. |
| Filesystem (MCP reference server) B Model Context Protocol, a Series of LF Projects, LLC | Reads and writes files; no entity, relation or search-by-name store. |
| MCP Toolbox for Databases A Google LLC | No memory store. |
| MongoDB MCP Server A MongoDB, Inc. | No memory or graph store of its own. |
| Nansen x402 API B Nansen | No store the agent writes to. source |
| Neon MCP Server BB Neon, LLC (subsidiary of Databricks, Inc.) | No memory store. |
| ObsessionDB F Kellerkind UG (haftungsbeschränkt) | No memory store. |
| PlanetScale MCP Server BB PlanetScale, Inc. | No memory store. |
| Postgres MCP Pro F Crystal Corp. | No memory store. |
| Redis MCP C Redis Ltd. | Stores keys and JSON in Redis, not entities and relations in a file at a chosen path. source |
| ReqRes MCP server D ReqRes | Generic JSON records, not a local graph file. |
| Snowflake-managed MCP server C Snowflake Inc. | No memory store. |
| Supabase API + MCP BB 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
The same as data: /api/v1/use-cases/data.memory-graph.json, or the MCP tool get_use_case with id data.memory-graph. Other jobs in this category: /api/v1/niches?category=data.
For companies
Do agents find, use and choose your tools?
An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.