← MCP server and skill grades

@modelcontextprotocol/server-memory

npm @modelcontextprotocol/server-memory

A
Type
MCP server
Scanned
Nov 12, 2026
Version
2.1.1
Files read
4

This MCP server gives an AI assistant persistent memory across chats by storing entities, relationships, and facts in a local JSONL file. It runs locally over standard input/output with no network or shell access, and its only notable weakness is that newly created memory files default to standard system permissions that may allow other user accounts on a shared computer to read stored memories.

What it can reach

Files
Reads and writes the knowledge graph JSONL file (memory.jsonl in the package directory by default, or the path configured in MEMORY_FILE_PATH), migrates a legacy memory.json file in the default directory if present, creates temporary save and lock files beside the memory file, and reads its own package.json for version information.

Findings

1 low
  1. LowNewly created memory file uses default umask permissions instead of owner-only access

    dist/index.js:483

    When saveGraph creates the memory file for the first time, mode is undefined and fs.writeFile uses Node's default 0666 mode masked by the process umask (typically producing 0644, readable by all local users). Subsequent saves preserve the existing file mode, keeping it world-readable unless the user manually runs chmod 600. Because the graph holds persistent personal details and notes across conversations (commonly at ~/memory.jsonl), other local accounts on a shared machine could read the file.

    Fix: Default to mode 0o600 when the memory file does not exist yet (for example, const effectiveMode = mode ?? 0o600) so newly created memory files are accessible only to the owner unless explicitly changed.