← 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.
  • Storage path configuration, graph read/write and delete handlers, resource notifications and stdio startup.
  • Repository licence transition.

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.

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.

Before you start

  • Node.js and npm/npx.
  • A writable directory for the memory file.

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/d73f99efbfd40c3aa1b61e88728b3d49fb52608f/src/memory/README.md

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

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

    Supports: publisher, upstreamDescription, limitations, review

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

    Supports: license, review

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

    Supports: language, install

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

    Supports: review, limitations, access, transports