Context Travel

Provides time-travel style context management for Claude agents, enabling checkpoints, resets, and clean context lifecycles.

javascript

GitHub Stars

javascript

Language

4 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "simen-mcp-memento": {
      "command": "npx",
      "args": [
        "-y",
        "github:simen/mcp-memento"
      ],
      "env": {
        "CLAUDE_SESSION_ID": "abc123-session",
        "CLAUDE_PROJECTS_DIR": "~/.claude/projects",
        "CLAUDE_CHECKPOINTS_DIR": "~/.claude/checkpoints"
      }
    }
  }
}

Context Travel MCP gives Claude agents conscious control over their context lifecycle by enabling checkpointing and resetting to a saved mental state. This helps you preserve a clear, oriented starting point, work on complex tasks, and resume with full fidelity after exploration or refactoring.

How to use

You interact with the MCP server from an MCP client to checkpoint, inspect, and reset your context. Use a checkpoint when you finish fully understanding a task or codebase, or before starting a large, context-heavy operation. You can reset to that checkpoint later to begin fresh with the same understanding, guided by a handoff message to your future self.

Common usage flow:

How to install

Prerequisites: Node.js and npm must be installed on your system.

Install the MCP server so you can run it locally or via a package manager.

# Run directly with npx
npx -y github:simen/mcp-memento

# Or install globally
npm install -g github:simen/mcp-memento

Additional configuration and notes

Configure your Claude code integration to point to the MCP server. Add the following to your Claude settings to enable the memento server as an MCP source.

{
  "mcpServers": {
    "memento": {
      "command": "npx",
      "args": ["-y", "github:simen/mcp-memento"]
    }
  }
}

Session discovery and environment

The MCP detects the current session by checking, in order: the CLAUDE_SESSION_ID environment variable, the ~/.claude/debug/latest symlink, and the most recent .jsonl file in the current project directory.

Environment variables you may use include CLAUDE_SESSION_ID, CLAUDE_PROJECTS_DIR, and CLAUDE_CHECKPOINTS_DIR. These control session identity, project location, and the location of saved checkpoints.

System prompts and hands-on workflow

In your agent’s system prompt, you’ll see sections describing how to checkpoint context, reset to a checkpoint with a message to your future self, list available checkpoints, and check context health. Use these tools to manage your mental workspace during tasks.

When you reset, you should include a concise handoff message that covers what you accomplished, key decisions, and concrete next steps.

Tools you can use with the MCP server

The MCP server exposes the following tools to manage your context lifecycle.

Available tools

checkpoint_context

Save your current context state as a named checkpoint, enabling you to return to a well-understood baseline later.

reset_to_checkpoint

Reset context to a specified checkpoint and inject a handoff message to your future self, including what was accomplished and next steps.

list_checkpoints

Show available checkpoints for the current session.

get_context_stats

Provide health metrics about your current context window, including turn counts, estimated tokens, and compaction events.

delete_checkpoint

Remove an unneeded checkpoint from the session.

Built by

VeilStrat

AI signals for GTM teams