ResumeState
io.github.UnderGroundDevPublished by GitHub account UnderGroundDevv1.0.0Updated Oct 24, 2026
Session continuity for AI assistants: resume any work lane where the last session stopped.
Overview
ResumeState gives an assistant tools to save and resume work state across sessions, filing structured handoffs under named lanes in a ResumeState account.
- What you can do
- Connect the assistant to a ResumeState account via a device-flow approval code and check connection status
- List lanes and fetch a lane's latest handoff or the account-wide packet
- Record a structured handoff per lane: tried, decided, done, failed, state, pointer
- Browse artifact cards and retrieve full artifact content when needed
- Search and fetch routines that worked from a replay pool
- Log sessions and ingest transcripts for bookkeeping
- When to use it
- Useful when work spans many sessions or models and you want the next session to pick up where the last one stopped, without re-explaining decisions, failures and current state. Suits people already using or willing to pay for a ResumeState membership.
- Requirements
- Runs locally over stdio; needs Python 3.10+ and uv, or the one-click Claude Desktop bundle. A ResumeState account and membership are required, approved through the connect tool's device flow; no API key goes in the config. RESUMESTATE_API_URL defaults to the hosted service and normally needs no change. Network access to the ResumeState API.
Installation
In SourceWeft
- Open ResumeState in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
ResumeState MCP server
Session continuity for AI assistants: resume any work lane where the last session stopped.
ResumeState keeps track of where your work stands: what was tried, what was decided, what's done and what failed. It files that under named lanes, one per line of work, so the next session can pick up where the last one stopped, on any model or vendor. This MCP server gives an assistant the tools to do that.
Tools
Install
You need Python 3.10+ and uv. Nothing to clone.
Claude Desktop (one-click bundle)
Download resumestate-mcp-1.0.0.mcpb from the latest release
and open it in Claude Desktop to install it.
Claude Code
Claude Desktop, Cursor and other MCP clients (claude_desktop_config.json, .cursor/mcp.json, ...)
Then ask your assistant to run connect. It shows you a link and a short code. Approve it in your ResumeState account,
and the assistant gets its own pass.
How the connection works
- No API key in your config.
connectuses the OAuth 2.0 device flow: you approve the assistant on the website, and it gets a pass scoped to your continuity. - The pass stays on your machine. It's kept in
~/.resumestate/mcp-token.json, readable by your user only, and renews itself. It's never printed. - The pass is narrow. It can't reach your keys, billing, password or other AIs. You can see it and switch it off under Connected AIs in your account.
- No configuration needed.
RESUMESTATE_API_URLdefaults tohttps://resumestate.com; you don't need to set it.
Pricing
Connecting an AI is part of a ResumeState membership. Every plan starts with a 7-day free trial (a card is asked at checkout; cancel anytime). Prices are in Canadian dollars:
See the plans and the guide to MCP continuity servers.
Privacy
Your continuity stays private to your account, and to your team on Team. This client talks only to the ResumeState API at the address above. Read the privacy page.
Licence
MIT. See LICENSE.
Source: README.md at commit 1bc1969
Tools
0Version history
1- v1.0.0LatestOct 17, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts