Snapshot

You have a modular MCP server that saves and resumes Claude conversations with token-efficient context preservation. It lets you capture conversation state, reload it later, and organize multiple snapshots with minimal token overhead, so you can continue work across sessions and across different MCP clients.

How to use

Save a snapshot when you want to preserve the current conversation state. You can provide a summary, a context, and optional next steps. When you later resume, you load the latest snapshot or a named one to pick up where you left off.

Resume work by loading a snapshot from your saved collection. You can load the latest, pick a specific named snapshot, or restore by identifier. This resumes Claude with the preserved context and progression state, reducing the need to re-create context from scratch.

Use named snapshots to mark milestones, such as versioned progress like a completed feature or a deployment. Save a snapshot with a name and a structured context, then load that exact named snapshot later to replay that milestone.

Manage snapshots through available operations: list all snapshots, load the latest, load by name, or delete a snapshot by its identifier. These actions keep your memory of conversations well organized and easy to navigate.

How to install

Prerequisites: you need a modern runtime for MCP servers (Node.js 18+ is recommended) and a compatible shell to run commands.

Step-by-step quick start

Step 1. Run the installer using the recommended one-liner

npx @whenmoon-afk/snapshot-mcp-server

Step 2. Restart Claude Desktop completely. Quit the application and reopen to apply the installer’s configuration.

Manual setup to configure Claude Desktop yourself

macOS or Linux config file entry

{
  "mcpServers": {
    "snapshot": {
      "command": "npx",
      "args": ["-y", "@whenmoon-afk/snapshot-mcp-server"]
    }
  }
}

Windows config file entry

{
  "mcpServers": {
    "snapshot": {
      "command": "cmd",
      "args": ["/c", "npx", "-y", "@whenmoon-afk/snapshot-mcp-server"]
    }
  }
}

Additional notes and troubleshooting

If you encounter issues with the server, try reinstalling the MCP server component, check that the client can reach the local MCP, and verify that the Node.js version meets the minimum requirement. If the problem persists, review the client logs for errors and ensure the local storage location is writable.

Structured context examples help you organize your snapshot data efficiently. A typical context could include file references, key decisions, blockers, and code state to enable a smoother continuation.

Available tools

save_snapshot

Save the current conversation state, enabling later restoration with resume functionality.

load_snapshot

Resume from a saved snapshot by latest, by name, or by ID to restore context and progress.

list_snapshots

View all saved snapshots and their metadata including summaries and contexts.

delete_snapshot

Remove specific snapshots from storage to keep the collection organized.