This MCP server enables Claude agents to manage their conversation context through "time travel" operations, allowing them to save, restore, and monitor their mental state during complex tasks.
Core Capabilities:
Checkpoint Context: Save the current conversation state as a named checkpoint with optional notes, capturing the entire history at that point
Reset to Checkpoint: Restore to a saved checkpoint while injecting a handoff message to brief your future self on accomplishments and next steps
List Checkpoints: View all available checkpoints for the current session with creation times and notes
Get Context Statistics: Monitor context window health including turn counts, estimated tokens, compaction events, and context age
Delete Checkpoint: Remove checkpoints that are no longer needed
Key Use Cases:
Preserve the "golden window" of understanding after orientation before context gets fragmented by summaries
Work on complex tasks then reset back to a clean state with a summary note
Avoid confusion from multiple context compactions by returning to fresh, high-fidelity states
Hand off progress between "versions" of yourself with structured briefing messages
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Context Travel MCPsave my current understanding of the authentication system as 'auth-understood'"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Context Travel MCP
An MCP server that gives Claude agents conscious control over their context lifecycle through "time travel"—the ability to checkpoint their mental state and later reset back to it with a message to their future self.
Why?
After multiple compactions, agents become confused by fragmented summaries. The "golden window" is right after orientation when understanding is complete and context is clean. This MCP lets agents:
Checkpoint that golden state
Work on complex tasks
Reset back to the checkpoint with a handoff note
Continue fresh, with full fidelity
Installation
Claude Code Configuration
Add to your MCP settings (~/.claude/settings.json or project settings):
Tools
checkpoint_context
Save your current context state as a named checkpoint.
When to use:
After fully understanding a codebase or task
Before starting a large, context-heavy operation
When you feel sharp and well-oriented
reset_to_checkpoint
Reset context to a checkpoint, injecting a handoff message to your future self.
The message_to_self should include:
What was accomplished since the checkpoint
Key findings and decisions
Clear next steps
Critical details (file paths, variable names, gotchas)
list_checkpoints
Show available checkpoints for the current session.
get_context_stats
Get statistics about your current context window health:
Turn counts
Estimated tokens
Compaction events
Health indicator
delete_checkpoint
Remove a checkpoint you no longer need.
System Prompt Integration
Add to your agent's system prompt:
Session Discovery
The MCP discovers the current session via (in order):
CLAUDE_SESSION_IDenvironment variable~/.claude/debug/latestsymlinkMost recent
.jsonlin the PWD-based project directory
Environment Variables
Variable | Description |
| Explicit session ID |
| Override projects directory (default: |
| Override checkpoints directory (default: |
How It Works
Claude Code stores sessions as JSONL files at ~/.claude/projects/<escaped-cwd>/<session-id>.jsonl. Each line is a JSON object representing a message, tool use, or summary.
Checkpoint = copy the session file Reset = restore the file + append handoff message Handoff = synthetic user message injected after restore
License
MIT