Remembra Relay MCP server

Remembra Relay

One agent stops. The next one already knows. When an agent's session ends, Remembra Relay saves a handoff built from what git says happened. The next agent, on another machine, from another vendor, or next week, starts from it.

Website • Relay guide • Docs • Changelog • Discord

<!-- mcp-name: io.github.remembra-ai/remembra -->

Install

First get a free key at app.remembra.dev, then run:

pipx install --force 'remembra[mcp]>=0.16'
remembra-install --all
remembra-relay connect --apply

remembra-install asks for the key at a hidden prompt (or reads REMEMBRAAPIKEY) and shows its changes before it writes. connect --apply writes the hooks and keeps a backup of each file; run remembra-relay connect alone first to see every change without writing. Codex runs the hooks only after you trust them: run /hooks in Codex once. Hosting the server yourself? Add --url to remembra-install. remembra-relay ships in remembra 0.16.0.

What the next agent sees

Claude Code finished a session and wrote in its summary that the work was done and pushed. Git disagreed. The next agent's brief starts with:

<!-- readme-brief: generated by remembra.relay.handoff.renderlastsession; tests/testreadmerelay.py keeps it true -->

Last session: claude-code (key-verified), 12m ago, on feat/pdf-export@a41f2c9: done: a41f2c9 Add PDF export for invoices; 77c01aa Embed fonts in exported PDFs; tests passing: pytest tests/test_pdf.py (12 passed); changed 3 file(s): invoices/pdf.py, invoices/fonts.py, tests/test_pdf.py / NOT done: 2 commit(s) not pushed to origin/feat/pdf-export / failing: none / next (derived from the recorded facts): push 2 commit(s) to origin/feat/pdf-export (facts collected by remembra-relay from git and the session transcript) (the agent's summary contradicts these recorded facts)

The done, not done and failing sections come from git and the session's test runs, never from an LLM. The agent's own summary is optional; it is checked against those facts and shown as unverified, or, as here, contradicted.

How it works

1. Close. When a session ends, remembra-relay close reads the branch, commits, changed and uncommitted files and unpushed commits from git, and for Claude Code the test runs and open items in the local transcript. The transcript never leaves your machine; secrets are redacted before anything does.
2. Brief. When the next session starts, in any tool, remembra-relay brief (or the session_brief MCP tool) gives the agent who worked last, what is done, what is failing and the next step, in about 1,500 tokens. Everything another agent recorded is wrapped as untrusted data.
3. Trail. Every handoff stays in order: remembra-relay trail, or the Trail page in the dashboard. A git log for your agents.

Shortened. The full README is on GitHub.