GoodMemory MCP Server

Durable user/project memory for MCP clients: recall context and remember selected facts.

Remote serverstreamable-httpPython

What is the GoodMemory MCP server?

If you already use GoodMemory, the goodmemory mcp server is the piece that lets your assistant work with it directly. Durable user/project memory for MCP clients: recall context and remember selected facts.

What the server does

GoodMemory is a memory layer for AI products and coding agents.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • Local — first storage: Bun gets durable SQLite by default; explicit Postgres,
  • host — codex, claude, or both detected hosts
  • activation — global, current workspace, or manual opt-in
  • Benchmark — Primary metric

Installation

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

Credentials and setup notes

Configuration is passed through the environment: YOUR_USER_ID, GOODMEMORY_USER_ID. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Where it fits

Plenty of database access servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. GoodMemory's toolset — Local, host, activation and 1 more — is a fair guide to whether it matches your workflow. It is maintained by hjqcan; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Worth knowing first

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
Localfirst storage: Bun gets durable SQLite by default; explicit Postgres,
hostcodex, claude, or both detected hosts
activationglobal, current workspace, or manual opt-in
BenchmarkPrimary metric

How to install the GoodMemory MCP server

{
  "mcpServers": {
    "goodmemory": {
      "command": "npx",
      "args": ["-y", "goodmemory"],
      "env": {
        "YOUR_USER_ID": "your-value",
        "GOODMEMORY_USER_ID": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
YOUR_USER_IDConfiguration value read at startup.Optional
GOODMEMORY_USER_IDConfiguration value read at startup.Optional

Example prompts to try

  • Use GoodMemory to Local.
  • Use GoodMemory to host.
  • Use GoodMemory to activation.

Frequently asked questions

It connects GoodMemory to MCP-compatible AI assistants such as Claude and Cursor, exposing 4 tools (Local, host, activation, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with GoodMemory directly.