Skip to content
MCP server

Claude Checkpoint MCP

Save Claude Code session state locally so a crash or /clear does not lose your place

Runs locallyStatus and history
Install
Pricing
Open source
Platforms
CLI
Runs
Locally
Version
1.0.0
Listing updated
today

Similar MCP servers

About Claude Checkpoint MCP

Claude Checkpoint MCP is an open-source MCP server for ai models and llm tooling. It runs locally on your machine and is started by your AI client.

Long coding sessions build up context that is expensive to rebuild: the goal, which approaches failed, which files matter and which test is still red. This server stores that working state as a small JSON file in the project, then turns it back into a resume brief of roughly 1.2 KB, a few hundred tokens, when a new session starts.

Its most useful trick is drift detection. At save time the server records a content hash for every file with uncommitted changes, together with the git branch and HEAD. On load it compares them with the working tree and flags only the files that changed since the checkpoint, so Claude re-reads those and trusts the rest of the brief. Secrets are redacted when saving, and a backup copy is kept.

Each Claude Code session gets its own checkpoint file named after its session ID, so sessions in a shared directory do not overwrite each other. Loading lists the checkpoints and asks you which to resume rather than choosing for you. Clients without a session ID, such as Claude Desktop, get one per conversation. Everything stays on your machine, and the repository is a fork of an earlier checkpoint project.

Install

Run in a terminal

claude mcp add claude-checkpoint-mcp -- npx -y session-checkpoint-mcp

Add to claude_desktop_config.json

{
  "mcpServers": {
    "claude-checkpoint-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "session-checkpoint-mcp"
      ]
    }
  }
}
Install in CursorOpens Cursor, which asks you to confirm. Or add it by hand:

Add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "claude-checkpoint-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "session-checkpoint-mcp"
      ]
    }
  }
}
Install in VS CodeOpens VS Code, which asks you to confirm. Or add it by hand:

Add to .vscode/mcp.json

{
  "servers": {
    "claude-checkpoint-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "session-checkpoint-mcp"
      ]
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "claude-checkpoint-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "session-checkpoint-mcp"
      ]
    }
  }
}

Add to your client's MCP settings (most use this shape)

{
  "mcpServers": {
    "claude-checkpoint-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "session-checkpoint-mcp"
      ]
    }
  }
}

Using several servers? Build one config file with the MCP config generator.

Configuration

  • CHECKPOINT_PROJECT_ROOTOptional. Absolute path of the default project to checkpoint, used when the client has no current project (e.g. Claude Desktop). A projectRoot argument on a tool call takes precedence.
  • CLAUDE_CODE_SESSION_IDSet automatically by Claude Code; do not set it yourself. Selects the per-session checkpoint file (.claude-checkpoints/<session-id>.json). Without it the server mints a session id per conversation, or uses the shared .claude-checkpoint file with CHECKPOINT_SESSION_IDS=legacy.
  • CHECKPOINT_SESSION_IDSOptional. Unset or mint: clients without a session id get their own checkpoint per conversation (the server mints an id on the first save and the agent passes it back). Set to legacy to have them share one .claude-checkpoint file, as before 1.0. No effect on Claude Code.

Tools this server provides (3)

Taken from the project documentation; the running server may differ.

save_session_checkpoint
Write the session's working state to a small JSON file in the project.
load_session_checkpoint
Turn the checkpoint file back into a compact resume brief.
list_session_checkpoints
List the checkpoints in the project so you can pick which session to resume.

What it does

Per-session checkpoints
Each Claude Code session writes its own file, so shared directories stay clean.
Compact resume brief
Rebuilds goal, tasks, decisions and touched files in a short markdown summary.
Drift detection
Flags only files whose content changed since the checkpoint was saved.
Git facts recorded
Stores branch, HEAD and dirty files with content hashes at save time.
Secret redaction
Redacts secrets when writing the checkpoint.
Optional session-start hook
The Claude Code plugin nudges Claude to offer resuming at the start of a session.
Local only
Nothing is sent anywhere.

Good for

  • Resume work after a terminal crash or SSH drop
  • Continue after running /clear or hitting the context limit
  • Avoid re-reading unchanged files at the start of a session
  • Pick which of several sessions to continue

Pricing

Open source

Claude Checkpoint MCP FAQ

Where are checkpoints stored?

In .claude-checkpoints/<session-id>.json inside the project, on your machine.

Does it send data anywhere?

No. It runs entirely locally.

How does it know what changed?

It records content hashes of uncommitted files at save time and compares them with the working tree on load.

Does it work outside Claude Code?

Yes. Clients such as Claude Desktop get a checkpoint per conversation, using an id the server mints on first save.

Is Claude Checkpoint MCP free?

Yes. Claude Checkpoint MCP is open source, so you can use and self-host it for free.

How do I add Claude Checkpoint MCP to Claude Code?

Run this command in your terminal: claude mcp add claude-checkpoint-mcp -- npx -y session-checkpoint-mcp

What are the best alternatives to Claude Checkpoint MCP?

The closest alternatives to Claude Checkpoint MCP are REA, Context7, Chrome DevTools MCP, Codebase Memory and GitHub.

Where this comes from

  • Description: written from the project's README.
  • Install steps: from the official MCP Registry entry.

How AIPoweredBot checks servers