← Explore all mcp servers

WORKSPACE KNOWLEDGE / Model Context Protocol steering group

Knowledge Graph Memory reference server

Persist named entities, observations and relations in a local JSONL graph between client sessions.

“A basic implementation of persistent memory using a local knowledge graph.”

01 / THE REASONING

Why this made the selection.

  • Keeps a small, inspectable local graph without requiring a vector database or service account.
  • Explicit entity, observation and relation tools make memory writes and deletions visible.

02 / THE REVIEW RECORD

What we actually inspected.

Source review has boundaries.
A clear record is more useful than a “safe” badge.

Material inspected

  • src/memory/README.md, package.json and index.ts at bbb701e7ac1e57f3edd1c2836b94c5457eaf7b9c.
  • Storage path configuration, file locking, graph read/write and delete handlers, resource notifications and stdio startup.
  • Root README.md and LICENSE (licence transition) at the same commit.

Our findings

  • Writes use a same-directory temporary file and rename, which reduces partial-file replacement risk on POSIX systems.
  • The server can remove entities and their relations. Persistence does not verify the truth of a saved observation.
  • index.ts registers nine tools: create_entities, create_relations, add_observations, delete_entities, delete_observations, delete_relations, read_graph, search_nodes and open_nodes, plus one subscribable graph resource.
  • Changed since the 2026-09-21 review (d73f99ef): every write tool now takes an exclusive <memory file>.lock, so separate client processes writing one file take turns. A stale lock is broken after 30 seconds, and a write that cannot get the lock within 60 seconds fails instead of overwriting the file. The earlier limitation "cross-process coordination was not established" no longer holds and was removed.
  • configExample is the README's "NPX with custom setting" Claude Desktop block at bbb701e7.
  • package.json at bbb701e7: name @modelcontextprotocol/server-memory, version 1.0.0, licence "SEE LICENSE IN LICENSE".

Not established by this review

  • Server launch, authenticated tool calls, and release-to-source parity were not tested.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

Connect a server deliberately.

Upstream setup instructions ↗

DOCUMENTED COMMAND

npx -y @modelcontextprotocol/server-memory

Copying does not execute this command. It may retrieve a newer version than the reviewed source.

  1. Configure the documented npx command in a stdio client.
  2. Set MEMORY_FILE_PATH to a persistent file location under your control rather than relying on the package-directory default.
  3. Review the client’s memory instructions, stored content, backup policy and access permissions.
  4. The repository README gives the command above as its example that starts the Memory server. It was not run.

Before you start

  • Node.js and npm/npx.
  • A writable directory for the memory file; the lock file is created next to it during each write.

Documented configuration example

Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.

{
  "mcpServers": {
    "memory": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-memory"
      ],
      "env": {
        "MEMORY_FILE_PATH": "/path/to/custom/memory.jsonl"
      }
    }
  }
}

04 / FOLLOW THE EVIDENCE

The source trail.

Our notes are separate from the original resource.
Check upstream before adopting a new version.

  1. https://raw.githubusercontent.com/modelcontextprotocol/servers/bbb701e7ac1e57f3edd1c2836b94c5457eaf7b9c/src/memory/README.md

    Supports: summary, upstreamDescription, whySelected, bestFor, limitations, install, access, compatibility, transports, review, configExample

  2. https://raw.githubusercontent.com/modelcontextprotocol/servers/bbb701e7ac1e57f3edd1c2836b94c5457eaf7b9c/README.md

    Supports: publisher, upstreamDescription, limitations, review, install

  3. https://raw.githubusercontent.com/modelcontextprotocol/servers/bbb701e7ac1e57f3edd1c2836b94c5457eaf7b9c/LICENSE

    Supports: license, review

  4. https://raw.githubusercontent.com/modelcontextprotocol/servers/bbb701e7ac1e57f3edd1c2836b94c5457eaf7b9c/src/memory/package.json

    Supports: language, install

  5. https://raw.githubusercontent.com/modelcontextprotocol/servers/bbb701e7ac1e57f3edd1c2836b94c5457eaf7b9c/src/memory/index.ts

    Supports: review, limitations, access, transports

Evidence & Ask