Context Travel MCP

Save your current context state as a named checkpoint. Use this when you're well-oriented and want to be able to return to this mental state later.

Good moments to checkpoint:

• After fully understanding a codebase or task

• Before starting a large, context-heavy operation

• When you feel sharp and well-oriented

The checkpoint captures your entire conversation history up to this point.

Reset your context back to a saved checkpoint, injecting a handoff message to your future self.

The message_to_self will appear as if you wrote it just before the reset. Use it to brief your future self on:

• What was accomplished since the checkpoint

• Key findings and decisions

• Clear next steps

• Critical details (file paths, variable names, gotchas)

After calling this, your context will be restored to the checkpoint state plus your handoff message.

List all available checkpoints for the current session. Shows when each was created and any notes attached.

Get statistics about your current context window health.

Returns:

• Number of turns (user and assistant messages)

• Estimated token count

• Number of compaction/summary events

• Context age

Use this to decide when you might want to checkpoint or reset.

Delete a checkpoint you no longer need.