Run Memory

Checkpoint and resume for AI agent runs, so crashed runs pick up where they left off.

Should I use this

Quality & Safety

A
Description quality
96%
Schema completeness
70%
Naming quality
92%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~530Tokens (tool definitions)
~589 BTypical response size
Minimal attention impact (0.41% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "memory": {
      "url": "https://memory.cloudforbots.com/mcp"
    }
  }
}

Remote endpoints

https://memory.cloudforbots.com/mcpstreamable-http

What it can do

Tool inventory

Tools (5)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟡save_checkpoint(run_id, step, state, done)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "run_id": {
      "type": "string",
      "description": "A stable id for this job that survives a crash, e.g. \"invoice-import-oct\". Use the same id when you restart."
    },
    "step": {
      "type": "string",
      "description": "The step you just finished, e.g. \"imported page 3 of 10\"."
    },
    "state": {
      "type": "object",
      "description": "JSON state needed to resume."
    },
    "done": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Optional list of completed item ids, so a resume skips them."
    }
  },
  "required": [
    "run_id",
    "step",
    "state"
  ]
}
⚪resume(run_id)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "run_id": {
      "type": "string",
      "description": "A stable id for this job that survives a crash, e.g. \"invoice-import-oct\". Use the same id when you restart."
    }
  },
  "required": [
    "run_id"
  ]
}
🟢list_checkpoints(run_id)

List recent checkpoints (step, size, time) for one run or all runs on your key.

Input Schema

{
  "type": "object",
  "properties": {
    "run_id": {
      "type": "string",
      "description": "A stable id for this job that survives a crash, e.g. \"invoice-import-oct\". Use the same id when you restart."
    }
  }
}
🟢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.

Input Schema

{
  "type": "object",
  "properties": {}
}
🟢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.

Input Schema

{
  "type": "object",
  "properties": {}
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded5 tools