memry MCP server

memry

memry gives your AI coding agents a persistent memory that carries over between sessions and projects. Decisions, bug fixes and discoveries saved in one session are available in the next one, so you do not have to explain the same context again.

Requirements

your PATH.

• macOS, Linux or Windows (amd64 or arm64)
• At least one supported agent. For Claude Code, its CLI (claude) must be on

Install

With Homebrew:

brew install mrtheroi/tap/memry
memry setup

Other ways to install memry, a single binary with no other dependency:

$(go env GOPATH)/bin, which must be on your PATH.

• With Go: go install github.com/mrtheroi/memry-cli/cmd/memry@latest. The binary lands in

memry___.tar.gz archive for your system, check it against checksums.txt, and put the memry binary from it on your PATH, for example:

• From a release: download the

tar -xzf memry_1.0.0_darwin_arm64.tar.gz memry
  sudo install -m 0755 memry /usr/local/bin/memry

On Windows, see Windows.

Your agents run memry from the path it is installed at, so outside Homebrew keep the binary where it is, or run memry setup again after you move it.

memry setup asks for your email, sends you a 6-digit login code, then asks which agents you use and connects memry to each one you select (the ones found on your machine are preselected; press space to select, enter to confirm). Start a new session in your agent afterwards to use it.

To choose the agents without the prompt, for example in a script, pass their keys:

memry setup --agents=claude-code,codex

Run memry setup again to change the selection; memry is removed from agents you deselect.

Claude Code plugin

This repository is also a Claude Code plugin marketplace. Its memry plugin adds a /memry:setup skill that walks you through installing the CLI and running memry setup.

From your terminal:

claude plugin marketplace add mrtheroi/memry-cli
claude plugin install memry@memry

Or inside a Claude Code session:

/plugin marketplace add mrtheroi/memry-cli
/plugin install memry@memry

On Claude Code 2.1.275 or later, one in-session command does both: /plugin install memry --marketplace mrtheroi/memry-cli.

The plugin does not register the MCP server itself; memry setup does, so memry is never connected twice.

Self-hosted

On a self-hosted memry server, your admin creates a token for you instead of the email login. Connect with:

memry setup --url https://memry.company.internal --token

--url is required with --token, so the token is never sent to the public server. Setup asks for the token without showing it, checks it with the server before saving it, then asks which agents you use as usual. For scripts, set the MEMRYTOKEN environment variable: with --token and no value, setup uses it instead of the prompt, also with --no-interaction, and the token stays out of the process list. --token= also skips the prompt (and wins over MEMRYTOKEN), but the token then lands in your shell history and the process list.

MEMRY_TOKEN="$token" memry setup --url https://memry.company.internal --token --no-interaction

MEMRY_TOKEN is only read together with --token, so it never changes the email login.

Shortened. The full README is on GitHub.