GoodMemory MCP Server

Content

GoodMemory is an MIT-licensed memory layer for coding agents and AI applications. Its standalone MCP server gives Claude and other MCP clients a scoped, durable store without requiring GoodMemory's managed Codex or Claude Code installation path.

The default MCP surface is read-only: context, trace, statistics, and artifact inspection. Users can explicitly add --allow-write to register goodmemory_remember, which sends proposed memories through the same governed remember pipeline used by the library API.

Features

• Local SQLite persistence by default, with optional PostgreSQL storage.
• Eight read-only MCP tools for recall, context, traces, statistics, and artifact inspection.
• Opt-in governed writes through goodmemory_remember.
• User, workspace, and optional agent scope controls.
• Companion CLI and library surfaces for audit, export, correction, forget, and deletion workflows.
• Embedding-free lexical retrieval by default, with optional embedding providers.
• Standalone recipes for Claude Desktop, Cursor, Gemini CLI, OpenCode, and other MCP-compatible clients.

Installation

Install the published package globally:

npm install -g goodmemory@0.5.1

Add the standalone server to an MCP client:

{
  "mcpServers": {
    "goodmemory": {
      "command": "goodmemory-mcp",
      "args": ["--standalone", "--user-id", "YOUR_USER_ID"]
    }
  }
}

The equivalent command is:

goodmemory-mcp --standalone --user-id YOUR_USER_ID

Keep the default read-only surface while validating recall. Add --allow-write only after reviewing the storage scope and write policy.

Use Cases

• Recall architecture decisions before continuing a coding task.
• Carry stable project context between Claude sessions.
• Inspect why a memory was selected before using it.
• Keep local memory separated by user, workspace, and agent scope.
• Export or remove incorrect memories through explicit lifecycle operations.
• Share one configured store across multiple MCP-compatible coding hosts.

Safety and Privacy

GoodMemory creates durable state, so stored content can outlive the conversation that produced it. Start with the read-only MCP surface, inspect the resolved storage location, and keep a stable scope. Before enabling goodmemory_remember, decide which information may be retained and how it will be reviewed, corrected, exported, or deleted.

The default standalone path is local SQLite and does not require an embedding or extraction provider. Configuring PostgreSQL, embeddings, assisted extraction, or a hosted model changes the data boundary. Treat recalled memory as prompt context: it will be visible to the model provider used by the host.

Source Review

• https://github.com/hjqcan/GoodMemory
• https://github.com/hjqcan/GoodMemory/blob/main/docs/GoodMemory-Standalone-MCP-Setup-Guide.md
• https://github.com/hjqcan/GoodMemory/blob/main/.well-known/goodmemory.json
• https://www.npmjs.com/package/goodmemory
• https://registry.modelcontextprotocol.io/v0.1/servers/io.github.hjqcan%2Fgoodmemory/versions/latest

These sources were reviewed on 2026-07-13. Prefer the live repository, published package metadata, capability descriptor, and official MCP registry entry for current versions, commands, storage behavior, and tool exposure.

• Source repositorygithub.com 2026-07-13T15:19:32-07:00
• Documentationgithub.com
• Submitted by hjqcan2026-07-13