Skip to content
anavem.com

MCP server

Memory MCP Server

Reference MCP server from the Model Context Protocol organization. It keeps a local knowledge graph of entities, relations and observations so an MCP client can remember information between chat sessions.

Maintainer
Model Context Protocol organization (reference server in the modelcontextprotocol/servers repository)
Licence
Repository LICENSE: MIT to Apache-2.0 transition (see limitations)
Last release
2026.8.31, released 2026-08-31 (repository-wide release shown on the modelcontextprotocol/servers releases page; the package.json in src/memory shows version 0.6.3)
Last verified Jump to what it can access ↓

What it can access

An MCP server gives an AI application a set of capabilities, and it can do only what its code and the credentials you give it allow. This is what the listing states, based on the sources below. Anavem does not rate it safe or unsafe: check it against what you plan to use it for.

Permissions it asks for

  • Write tools (per README): create_entities, create_relations, add_observations, delete_entities, delete_observations, delete_relations
  • Read tools (per README): read_graph, search_nodes, open_nodes
  • Reads and writes a local JSONL file

Data it can reach

README states data is stored in a JSONL file, by default memory.jsonl in the server directory, configurable with the MEMORY_FILE_PATH environment variable. The README does not name the transport; its configurations start the server as a command (npx or docker), and per the MCP architecture page (2026-10-03) a server using the STDIO transport is a local process on the same machine as the client. The README describes no network access or cloud storage. Whatever the model stores about you is saved in that file and is returned to the AI application whenever the graph is read or searched.

How it is installed or connected

Steps copied from the official README (https://github.com/modelcontextprotocol/servers/tree/main/src/memory, read 2026-10-03):

  1. NPX: command npx with args ["-y", "@modelcontextprotocol/server-memory"]
  2. Docker: command docker with args ["run", "-i", "-v", "claude-memory:/app/dist", "--rm", "mcp/memory"]

The README places these inside the mcpServers section of the client configuration. To change the storage location, set the MEMORY_FILE_PATH environment variable.

Limitations

  • Licence detail: Repository LICENSE: the project is "undergoing a licensing transition from the MIT License to the Apache License, Version 2.0"; new code is Apache-2.0 and contributions without relicensing consent remain MIT. The src/memory README states MIT; the package.json license field reads "SEE LICENSE IN LICENSE".
  • The repository README describes the servers as reference implementations meant as educational examples, not production-ready solutions.
  • Includes delete tools; the model can remove entities, relations and observations from the stored graph.
  • The docs do not describe encryption of the memory file.
  • Anavem has not audited this software.

Not sure what to look for? Read what to check before installing.

Quick answers

Who maintains this MCP server?
Model Context Protocol organization (reference server in the modelcontextprotocol/servers repository).
What can it access?
It asks for: Write tools (per README): create_entities, create_relations, add_observations, delete_entities, delete_observations, delete_relations, Read tools (per README): read_graph, search_nodes, open_nodes, Reads and writes a local JSONL file. README states data is stored in a JSONL file, by default memory.jsonl in the server directory, configurable with the MEMORY_FILE_PATH environment variable. The README does not name the transport; its configurations start the server as a command (npx or docker), and per the MCP architecture page (2026-10-03) a server using the STDIO transport is a local process on the same machine as the client. The README describes no network access or cloud storage. Whatever the model stores about you is saved in that file and is returned to the AI application whenever the graph is read or searched. We do not label anything safe or unsafe; read the official sources before you install.
What licence does it use?
Repository LICENSE: MIT to Apache-2.0 transition (see limitations). Check the terms if you plan to use it commercially.
What are its limitations?
Licence detail: Repository LICENSE: the project is "undergoing a licensing transition from the MIT License to the Apache License, Version 2.0"; new code is Apache-2.0 and contributions without relicensing consent remain MIT. The src/memory README states MIT; the package.json license field reads "SEE LICENSE IN LICENSE". The repository README describes the servers as reference implementations meant as educational examples, not production-ready solutions. Includes delete tools; the model can remove entities, relations and observations from the stored graph. The docs do not describe encryption of the memory file. Anavem has not audited this software.
When was it last released?
2026.8.31, released 2026-08-31 (repository-wide release shown on the modelcontextprotocol/servers releases page; the package.json in src/memory shows version 0.6.3). Verified Oct 3, 2026.

Sources

Other listings in the same category.

All MCP servers →