All servers / Memory / Session Checkpoint MCP server
Session Checkpoint MCP server
MCP server that checkpoints Claude Code session context to survive crashes and token limits
Tested by ConnectATDScore 86 out of 100. Tested 2026-11-19 on package version 1.0.0. Package: session-checkpoint-mcp · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 20 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 8 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (2.4 seconds including download)
- Tools offered: 3
- Last published: 2026-11-11
- Weekly downloads (npm): 778
- License: MIT · Direct dependencies: 2
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
save_session_checkpoint11 of 11 parameters describedSave the current session's goal, progress, touched files and recent commands to this session's checkpoint in the project (.claude-checkpoints/<session-id>.json; a client without a session id gets one on its first save, returned as session), so a new session can resume after a crash, /clear, or context limit without re-exploring. Call after finishing a milestone, before risky operations, and when the conversation is getting long. Git branch, HEAD and uncommitted files are captured automatically. Subagents must not call this: they share the parent session's checkpoint. Report progress to the parent instead.
load_session_checkpoint4 of 4 parameters describedLoad this session's checkpoint and return a compact brief of its goal, progress, next steps, touched files and recent commands, plus which files changed since it was saved. Call at the start of a session or when the user asks to resume. If this session has no checkpoint but others exist in the project, it returns a list instead: show it to the user, ask which one to resume, and call again with `checkpoint` set to its selector. After loading another session's checkpoint, pass that selector as `resumedFrom` on the next save_session_checkpoint call.
list_session_checkpoints3 of 3 parameters describedList the checkpoints saved in the project (one per Claude Code session, plus a legacy .claude-checkpoint if present), newest first, with each one's goal, last-saved time, branch and whether all its tasks are done. Use it when the user wants to resume a different or older session; load one with load_session_checkpoint's `checkpoint`.
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.