A remote MCP endpoint that lets an assistant checkpoint and resume AI agent runs so interrupted runs continue where they left off.
What you can do
Run Memory is a hosted MCP server reached over streamable HTTP at a fixed remote endpoint. According to its registry description, it provides checkpoint and resume behavior for AI agent runs, so a run that crashes can pick up from its last saved state instead of starting over. No tools, packages, environment variables, or headers are declared in the supplied manifest, so the exact operations it exposes are not documented here.
When to use it
Consider it when you run long or multi-step agent workflows and want them to survive crashes or interruptions without losing progress. It is aimed at agent-run continuity rather than general data storage or search.
Requirements
A remote MCP client that supports streamable HTTP and network access to the provider's endpoint. The manifest declares no authentication, no environment variables, no headers, and no local packages, so no local runtime or credentials are documented.
Before you install
The manifest declares no authentication, so it is unclear who can read or write the stored run state; treat checkpoint contents as potentially sensitive. The server is remote, so run data is sent to a third party. No tools are listed, so what it writes, changes, or deletes cannot be verified from the supplied material.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.botrecipe%2Fmemory/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
Call after each completed step with the state you would need to continue (cursor, ids done, partial results; up to 256 KB JSON). Pro saves it (last 20 per run, kept 30 days). Free watch-only saves nothing and returns would_save: exactly what would have been stored. Never put passwords or API keys in state.
Call FIRST when a run starts. If a checkpoint exists for run_id (Pro), returns the last step, state and done list: continue from there and skip finished work. If none, start fresh.
Parametersrun_idrequired
list_checkpoints
List recent checkpoints (step, size, time) for one run or all runs on your key.
Parametersrun_id
weekly_report
Draft a plain-English report of the last 7 days: runs, checkpoints saved (Pro) or that would have been saved (free). Read-only; sends nothing.
Takes no parameters.
usage_and_upgrade
Show today's usage for your key or IP and the $49/month All Access upgrade link (cloudforbots.com/offer). Free tier: 500 calls/day. Not metered.
Takes no parameters.
Version history
1
v1.0.0LatestOct 15, 2026
Score
72%
72% 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 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Publish an icon in the registry entry.
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.