Handoff MCP server
io.github.kirill-sviridov/handoff-mcp·v0.4.0·2 starsCross-session memory for Claude over MCP — prioritised briefs, supersession, cross-project recall.
2 stars138 downloads/wk
Reviews
Write oneNobody has reviewed Handoff yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Handoff tools (7)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
checkpointClose out the current session and produce its hand-off brief.
consolidateCompress old finished sessions into durable entity notes ('sleep').
get_briefLoad the prioritised hand-off brief for a project.
log_eventnote_entityRecord durable, long-lived project knowledge on an entity note.
search_memorySearch memory across sessions and projects.
syncSync this device's memory vault with its private git remote.
Public scan report
scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it
- Code scan25 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 3 days ago15/15
- Maintainer identityregistry namespace matches repository owner6/10
How Handoff compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 89/100
- higher than 80% of 48,255 servers
- Tools
- 7
- the typical server has 7
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- GitHub stars
- 2
- more than 75% of 28,688 servers
- Downloads a week
- 138
- more than 70% of 12,191 servers with a package
What its tools let an agent do: 6 read · 1 change
Install Handoff in Claude Code, Cursor or VS Code
claude mcp add handoff-mcp -- uvx handoff-mcp
What the publisher says
From the Handoff repository's README, as published. We do not edit it. Read it on GitHub
handoff-mcp
<!-- mcp-name: io.github.kirill-sviridov/handoff-mcp -->
Your agent's memory between sessions. Persistent, cross-project hand-off for
Claude over the Model Context Protocol — it remembers the goal, the decisions,
the dead-ends, and what's next, so the next session never starts from zero.
Claude forgets everything between sessions. handoff-mcp gives it a memory that survives the context window: it tracks the progress of your work — goals, decisions and their rationale, dead-ends, open questions, the next step — and at the boundary of a session produces a prioritised, token-budgeted brief so the next session resumes already knowing where you left off.
It is not a context dump. Two things make it different from similarity-based memory stores (mem0 / OpenMemory style):
decisions never appear in a future brief. Memory reflects the current state of the world, not a flat pile of contradictory facts.
- Temporal supersession. A new decision retracts an old one; retracted
(recency + importance + supersession), not by an LLM — so it is reproducible and stays within a token budget (a soft cap on event content; see Limitations).
- Deterministic brief. The brief is assembled by an explainable ranker
hosted service — so memory can follow you across machines (pull-on-start, push-on-checkpoint, conflict-free entity merges) with zero vendor lock. See Multi-device sync.
- Your store, multi-device. The vault is your own private git repo, not a
Status: v0.4, early. The core (vault, brief, supersession, keyword search,
cross-project recall) is tested and stable; the semantic, consolidation,
importer, and multi-device sync layers are optional and newer. It leans on the agent calling the tools
at the right moments — see Limitations for the honest edges.
It is also cross-project: one vault, namespaced per project. The brief is project-scoped (where did I leave off here), but searchmemory recalls across all projects — so when you say "in one of my projects we did X"*, Claude can find and pull that decision out of another project.
Contents
- Demo: two sessions
- Benchmarks
- How it works
- MCP tools
- Cost & API keys
- Semantic recall (optional)
- Memory consolidation (optional)
- Import existing history
- Quickstart
- Connect your MCP client — Claude, Cursor, Codex, Kilo Code, …
- Where your memory lives
- Multi-device sync (optional)
Demo: two sessions
python examples/twosessionsdemo.py — session 1 works and stops; session 2 is a fresh process that resumes from the brief alone.
Session 1 logs its progress (and changes its mind once):
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Handoff: common questions
- Is Handoff MCP server safe?
- Yes, by our scan: it is graded A (89/100). Read the Handoff safety report
- How do I install Handoff?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Handoff need an API key?
- No secret keys are declared. It reads 2 settings from the environment.
- Is Handoff maintained?
- The last commit was 42 days ago (2026-09-23). The latest release is v0.4.0.
- What can I use instead of Handoff?
- Servers from other publishers that do the same job: Deja Vu MCP server, e2e MCP server and Memorix MCP server. Compare all Handoff alternatives.
- How does Handoff compare with other MCP servers?
- safety score 89/100 (higher than 80% of 48,255 servers); tools 7 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.
Alternatives to Handoff
Same job from other publishers: the closest match first, then the best rated.
- Deja Vudeja-vu: local memory over the session histories of forty-three coding agents.not reviewedEstablishedA
- e2eOpen live web and mobile app sessions from an e2e project to inspect the app and try locators.not reviewedWidely usedA
MemorixLocal-first project memory with legacy MCP and 2026 discovery compatibility.not reviewedEstablishedB
