conversation-handoff-mcp
MCP server for transferring conversation context between AI chats or different projects within the same AI.
Features
Auto-Connect (v0.4.0+): Server automatically starts in the background - no manual setup required
Auto-Reconnection (v0.4.0+): Seamlessly reconnects when server goes down - no manual intervention needed
Memory-Based Storage: Lightweight temporary clipboard design - no files written to disk
Common Format: Human-readable Markdown format
Lightweight API: Returns only summaries when listing to save context
Auto-Generated Keys (v0.4.0+): Key and title are now optional in
handoff_save
Installation
Works with Claude Desktop, Claude Code, Codex CLI, Gemini CLI, and other MCP clients.
Configuration File Locations
Client | Config File |
Claude Desktop (macOS) |
|
Claude Desktop (Windows) |
|
Claude Code |
|
Codex CLI |
|
Gemini CLI |
|
Cursor |
|
ChatGPT Desktop | In-app settings (Developer Mode) |
Via npm (Recommended)
No pre-installation required - runs via npx.
For global installation:
Local Build
MCP configuration:
Note: Codex CLI uses TOML format. See Codex MCP documentation for details.
Tools
handoff_save
Save conversation context. Key and title are auto-generated if omitted (v0.4.0+).
handoff_list
Get list of saved handoffs (summaries only).
handoff_load
Load full content of a specific handoff.
handoff_clear
Delete handoffs.
handoff_stats
Check storage usage and limits.
Auto-Connect Mode (v0.4.0+)
Starting with v0.4.0, the server automatically starts in the background when an MCP client connects. No manual setup required!
How It Works
Operating Modes
Mode | When | Behavior |
Auto-Connect (default) | No | Discovers or auto-starts server |
Explicit Server |
| Connects to specified URL |
Standalone |
| No server, in-memory only |
Memory-Based Storage
Handoff data is stored in memory only:
Data is shared across all connected MCP clients via the HTTP server
Data is lost when the server process stops
No files are written to disk - lightweight and clean
Perfect for temporary context sharing during active sessions
FIFO Auto-Cleanup: When limit is reached, oldest handoff is automatically deleted (no errors)
Auto-Reconnection
When the shared server goes down during operation:
Configurable retry limit via
HANDOFF_RETRY_COUNT(default: 30)On final failure: outputs pending content for manual recovery
Other MCP clients automatically discover the new server on their next request
Server Auto-Shutdown (TTL)
The server automatically shuts down after a period of inactivity:
Default: 24 hours of no requests
Configurable via
HANDOFF_SERVER_TTLenvironment variableSet to
0to disable auto-shutdownNext MCP client request will auto-start a new server
MCP Client Configuration
Standard configuration (recommended) - Just works with auto-connect:
Specify custom server:
Force standalone mode (no server):
For Claude Desktop only. Claude Desktop cannot transfer conversations between projects by default, but since it shares memory space as a single app, this MCP server enables handoffs between projects. Claude Code and CLI tools run as separate processes per tab/session, so handoffs don't work in this mode.
Manual Server Start (Optional)
If you prefer manual control:
HTTP Endpoints
Method | Path | Description |
POST | /handoff | Save a handoff |
GET | /handoff | List all handoffs |
GET | /handoff/:key | Load a specific handoff |
DELETE | /handoff/:key | Delete a specific handoff |
DELETE | /handoff | Delete all handoffs |
GET | /stats | Get storage statistics |
GET | / | Health check |
Workflow Example
Scenario: Design discussion in Claude Desktop → Implementation in Claude Code
In Claude Desktop - Have a design discussion:
User: Let's design an authentication system for my app. Assistant: I recommend using JWT with refresh tokens... [detailed discussion continues]Save the conversation - When ready to hand off:
User: Save this conversation for implementation in Claude Code. Assistant: (calls handoff_save) ✅ Handoff saved with key: "auth-design-20241208"In Claude Code - Load and continue:
User: Load the auth design discussion. Assistant: (calls handoff_load) # Handoff: Authentication System Design [Full conversation context loaded] I see we discussed JWT with refresh tokens. Let me implement that...
Key Points:
The AI automatically formats and saves the conversation
Context is fully preserved including code snippets and decisions
No manual copy-paste needed
Note: The server automatically starts in the background when the first MCP client connects. No manual startup required.
Configuration
Customize behavior via environment variables.
Connection Settings (v0.4.0+)
Variable | Default | Description |
| (auto) |
|
|
| Port range for auto-discovery |
| 30 | Auto-reconnect retry count |
| 10000 | Auto-reconnect interval (ms) |
| 86400000 (24h) | Server auto-shutdown after inactivity (0 = disabled) |
Storage Limits
Variable | Default | Description |
| 100 | Maximum number of handoffs |
| 1048576 (1MB) | Maximum conversation size |
| 10240 (10KB) | Maximum summary size |
| 200 | Maximum title length |
| 100 | Maximum key length |
Configuration Example (Claude Desktop)
Conversation Format
License
MIT
Author
trust-delta