Handover MCP

Move active work between Claude Code, Codex, Cursor, Gemini CLI, people, and service agents without losing decisions, files, history, or authorship.

Handover provides shared, versioned context for humans and AI agents through a hosted Model Context Protocol server, a dependency-free CLI, and eight open Agent Skills. This repository is the public source, discovery, installation, and connection record for those interfaces.

Research and evidence

The Handover research and evidence index collects the open continuity benchmark, Reporter migration field report, Handoff Continuity Record, and runnable continuation demo. Findings stay beside their methods, source artifacts, first-party relationship, and material limitations.

The versioned research/v1/ package gives agents and researchers a stable JSON index, JSON Schema, citation metadata, and a bounded Markdown summary. The package is a first-party publication by Handover and 44pixels; it is designed for inspection and reuse, not presented as independent validation.

• Human research index
• Agent-readable production index
• Versioned repository index
• Citation metadata
• Run and submit an independent benchmark result

See a complete handoff

The public continuation demo shows the same workflow from both sides: an interactive human view and an agent-readable record. It includes Markdown, SQL, JSON, a visual artifact, three attributable revisions, a human review note, and the next agent's resolution. No account is required.

• Interactive demo
• Continue the demo in your workspace
• Demo workflow and verification notes
• Agent-readable manifest
• Raw Markdown
• Raw SQL
• Evidence JSON

Build a private handoff prompt

The AI handoff prompt generator turns unfinished work into separate capture and receiver prompts without requiring an account. Draft fields stay inside the browser tab and are not sent to analytics or stored as a server-side draft.

The receiver prompt requires the next actor to inspect the evidence, separate verified and unverified state, identify blockers, and state one bounded next action before continuing. Copy or download the Markdown record, or carry the same private draft into a prefilled first handover.

• Open the private prompt generator
• Inspect the raw Markdown example
• Decide when HANDOFF.md is enough

Move from Claude Code to Codex

Codex's built-in import is the right first choice for a one-time move of supported Claude Code setup, projects, memories, and recent chats. Use Handover when Claude Code and Codex will alternate on unfinished work and need shared artifacts, separate identities, review, and revision history.

The Claude Code to Codex transfer recipe contains the exact sender checkpoint, two-host service-credential setup, receiver verification, optimistic-concurrency continuation, revocation test, and pass criteria. The rendered guide explains when to use native import and when to use a durable handoff.

Run the reviewed MCP handoff

The demo shows the finished record. The end-to-end MCP handoff procedure tests the workflow itself across separate authenticated identities:

1. verify the publisher;
2. publish Markdown, SQL, and JSON;
3. read every artifact back;
4. review exact evidence from another identity;
5. publish a correction with optimistic concurrency;
6. resolve the finding against the correcting revision; and
7. prove a fresh successor can continue without the original chat.

It also exercises denied, read-only, stale-revision, and revoked-credential paths. Use the rendered guide for the rationale, or connect an agent through the install flow before running the repository procedure.

Use the AI agent handoff checklist

For a smaller local handoff, start with the Markdown checklist. It captures the objective, current state, decisions, evidence, constraints, next action, and ownership, then requires the receiving actor to read the current revision, open the evidence, reproduce one meaningful result, and mark the handoff as passed or blocked.

The rendered checklist and FAQ explains each verification step. The raw template works without Handover; use the hosted service when multiple actors need authenticated access, immutable revisions, search, annotations, or auditable ownership.

Test company AI context readiness

Before connecting company knowledge to several people and agents, use the company AI context readiness checklist. It separates approved source knowledge from changing continuation records, inventories human and service identities, declares company and workspace boundaries, and finishes with a two-person, two-agent pilot.

The pilot is intentionally stricter than an import count: it verifies authorized retrieval, attributable revisions, human review, denied searches, agent revocation, and fresh-session continuation. The source-linked architecture guide explains why a search index, private model memory, and canonical company records have different responsibilities.

Use the open handoff format

The Handoff Continuity Record is a platform-neutral JSON format for the state another human or AI agent needs to verify and continue work. It records the objective, verified and unverified state, decisions, evidence, constraints, next action, ownership, and open review without prescribing transport, routing, authentication, or storage.

The protocol/v1/ directory contains:

• a JSON Schema Draft 2020-12 contract;
• a valid inventory-reporting example;
• a dependency-free Node.js conformance checker; and
• producer, receiver, scope, and security requirements.

node protocol/v1/validate.mjs protocol/v1/example.json

MCP can expose the tools used to read and write the record. A2A or an orchestration framework can route it. Git or Handover can store it.

Connect

The canonical Streamable HTTP endpoint is:

https://handover.sh/api/mcp?profile=core

The recommended core profile exposes 17 tools for everyday identity, search, retrieval, review, continuation, publishing, and portability workflows. Use https://handover.sh/api/mcp?profile=native for all 27 first-party Handover operations. The unparameterized https://handover.sh/api/mcp endpoint retains all 55 tools and Reporter aliases for existing integrations.

The endpoint exposes its MCP handshake and tool schemas without an account so clients and directories can verify compatibility before connecting. Tool calls remain protected and return Handover's OAuth resource challenge when no valid human or service credential is present.

Interactive MCP hosts use Handover's first-party OAuth flow: standard discovery, dynamic client registration, PKCE, short-lived access tokens, and rotating refresh tokens. The host opens Handover in a browser; sign in as yourself, review the requested permissions, and approve the connection. Handover records your human identity on every attributable action.