Hosted memory for coding agents: decisions and fixes saved in one session load automatically in the next.
Every new coding session starts from zero unless something remembers on the agent's behalf. Memry is a small Go binary that registers its own MCP server in your coding agents, so they can save what they learned and search it later. The Memry MCP server stores those memories on a memry server tied to your account, and each new session loads the recent ones for the project you are in.
Developers who switch between agents, or who keep losing context on long-running projects. It supports five agents today:
| Agent | Setup key | What gets added |
|---|---|---|
| Claude Code | claude-code |
MCP server at user scope, plus a SessionStart hook |
| Codex | codex |
MCP entry and instructions in AGENTS.md |
| OpenCode | opencode |
MCP entry and AGENTS.md instructions |
| Antigravity | antigravity |
MCP entry and GEMINI.md instructions |
| Windsurf | windsurf |
MCP entry and global rules |
Claude Code loads memories through the hook, including on resumed and compacted sessions. The others are told to load them as their first step.
Homebrew (brew install mrtheroi/tap/memry), go install, WinGet on Windows, or a release archive all give you one binary. Then memry setup asks for your email, sends a six-digit login code, and lets you choose which agents to connect. There is no password. Setup edits only its own entries in each agent's config, and it never writes your login token into those files. Keep the binary where you installed it, or rerun setup after moving it.
Teams can run a self-hosted memry server instead. An admin issues a token, you pass --url with --token, and setup refuses plain http:// for anything other than this machine unless you add --insecure.
A project defaults to the name of the codebase's directory. Drop a .memry.json file with a project key into the root of several codebases, a backend and a frontend for instance, and they share one memory pool.
Memories live on a server, not on your disk, so this is a hosted service with an account. Optional usage metrics are off by default and only cover Claude Code token and cost data when you enable them. memry uninstall revokes the local token; memry delete-account erases the account and its memories permanently. The individual MCP tool names are not published, so we have not listed them. Compare it with the Memory server or browse more knowledge and memory servers and general developer tools.
memry setup --agents=claude-codeInstall the memry binary first (for example brew install mrtheroi/tap/memry). Setup signs you in by email code and registers the MCP server and session hook.
| Variable | Description | Required |
|---|---|---|
| MEMRY_TOKEN | Token for a self-hosted memry server, read only when setup runs with --token and no value. | Optional |
| MEMRY_CONFIG | Path to an alternative config file instead of ~/.config/memry/config.json. | Optional |
Read, search and edit files inside allowed directories with the Model Context Protocol reference Filesystem server.
Retrieve version-aware library documentation and code examples with Context7 MCP, using resolve-library-id and query-docs.
Web3 founder diligence: code audit, jurisdiction, fund matching, portfolio, scoring.
Ephemeral data sandbox for AI workflows with guardrails and security
Huly MCP: feature-complete MCP server for Huly integration
# JobNimbus MCP Server This project provides a [Model Context Protocol (MCP)](https://docs.cursor.com/context/model-context-protocol) server for