‹ Guides

Guide · MCP

An MCP server for session continuity, not just memory

The Model Context Protocol (MCP) lets an assistant call tools on a server: read a file, query a database, or remember something. A "memory server" is one of the first things people add. Most of them store facts. For long builds with coding agents, the thing worth storing is where the work stopped.

Two kinds of memory

• Facts: preferences, names, conventions, things that stay true for months. A notes store or a vector index is good at these: you search, it finds the closest notes.
• State: what was just decided, what failed an hour ago, what comes next. State goes stale fast, and searching for the "closest" note is the wrong question. You want the latest handoff for this exact line of work, every time.

A continuity server is built around the second kind.

What a continuity server should give an assistant

• Resume: fetch the latest handoff for one line of work, short enough to read at the start of every session.
• Hand off: write a structured entry (tried, decided, done, failed, state, pointer) at natural pauses, not a free-form blob.
• Lines of work with names: a list of lanes, so two projects never blur into one memory.
• A freshness signal, so an assistant knows when the picture is stale.
• A credential the person can switch off: scoped to memory, revocable, and never a long-lived key pasted into a config file.
• The same memory from any client: desktop app, terminal agent, editor or chat, from any vendor.

How ResumeState fits

ResumeState is that kind of server. Its MCP server exposes these tools:

• connect: link this assistant to your account with a short approval code
• resume and list_lanes: fetch a lane's latest handoff, or the account-wide packet and its lanes
• handoff: record one structured handoff under a lane
• list_artifacts and get_artifact: cards first, full content only when needed
• replay_search and replay_get: routines that worked, from the replay pool
• log_session, ingest and status

Connecting uses the OAuth 2.0 device flow (RFC 8628): the assistant gets its own pass for your memory, which you can see and switch off on your account's Connected AIs page. It can't reach keys, billing, your password or other AIs. Your continuity is private to your account (and your team, on Team).

How to connect today

The MCP package isn't published for a one-line install yet. Until it is, the fastest way in works with any assistant that can run a command or send a web request:

1. In your account, press Copy the text for my AI.
2. Paste the two lines into Claude Code, Codex, Cursor's agent, Gemini CLI or a chat assistant. They hold a link to a public recipe and a one-time code that works once, for ten minutes.
3. The assistant connects itself, sets up your lanes and adds a start-and-end routine, then tells you in one sentence what it set up.

Questions

Related guides

• Why your AI forgets everything between sessions: Each new chat starts empty, and what to save so the next session starts where you stopped.
• Hand a session to a cheaper or different model: Let the strong model reason, let a cheaper one do the volume, and keep the thread between them.
• Claude Code session handoff: Carry Claude Code's work across /clear, compaction, new sessions, other machines and other models.