Several unrelated projects use the name Memory MCP. This page covers the Knowledge Graph Memory Server in modelcontextprotocol/servers, published as @modelcontextprotocol/server-memory. Version 2.1.1 persisted synthetic entities and a relation to a chosen file and returned them after restart. That does not establish automatic or correct memory use by an AI host.
For recording a problem's decomposition, see Sequential Thinking MCP's input fields. For ordinary file access boundaries, see Filesystem MCP's directory limits.
Choose the persistence file explicitly
Use Node.js 24 and set MEMORY_FILE_PATH to an absolute test path. The lab file lived in container tmpfs: it survived a server-process restart but disappeared when the container ended. That tests a restart readback without mixing synthetic records into working data.
Write two entities and a directed relation
Call create_entities through an MCP client to add Dispatch31, a dispatch with the observation Cutoff 08:30, and DepotA, a depot. Then create a Dispatch31 → DepotA relation with relationType leaves_from. Direction matters; reversing the endpoints changes the meaning.
These commands use a POSIX shell. The test ran in Linux; Windows shell behavior was not tested.
npm install --ignore-scripts --save-exact @modelcontextprotocol/server-memory@2.1.1
# POSIX shell; choose a disposable absolute path
MEMORY_FILE_PATH=/tmp/test-memory.jsonl node node_modules/@modelcontextprotocol/server-memory/dist/index.js
Restart and verify the stored graph
Close the first server process and start another with the same MEMORY_FILE_PATH. read_graph returned the original cutoff observation and leaves_from relation. Creating a relation from a nonexistent Missing entity returned a tool error. Handle that error rather than assuming that an earlier entity creation succeeded.
Persistence is not automatic recall
The test covers explicit create/read calls and a process restart. Updates, deletion, cross-host storage, concurrent writers, backup recovery, and model retrieval strategies were not locally tested. Any supported capabilities mentioned here come from official v2.1.1 documentation; undocumented behavior remains unknown. The server stores observations supplied to it, so decide what belongs in the graph and how records will be removed.
Official sources and test scope
Codex ran this synthetic-data test in a credential-free, non-root, network-disabled container. It is not a claim that the site owner tested it. Package version: 2.1.1; documentation snapshot: e1dc4b18dbb9.