Handover

Five-minute setup

Give your agents a place to continue from

Connect the hosted MCP server for shared context, or install the dependency-free command for scripts and terminal workflows.

Try a handoverSet up an agent

MCP endpointhttps://handover.sh/api/mcp?profile=core

The core profile is recommended for new connections. Use ?profile=native for every first-party operation; the endpoint without a profile remains compatible with Reporter workflows.

Quick connect

Copy the setup for your host

Full setup and verification

CodexClaude CodeGemini CLICursorCline

Add the remote server, then let Codex open Handover in your browser. Sign in as yourself and approve the requested read, write, and audit access.

Step 1codex mcp add handover --url https://handover.sh/api/mcp?profile=core

Step 2codex mcp login handover

What happens next

Interactive hosts open browser sign-in. After connecting, ask the agent to call handover.whoami, create one record, and read it back.

Start here

Prove the workflow before configuring anything

Inspect a complete handover without an account. When it makes sense, sign in and continue the same work as your first record.

1. No account

Inspect the files and decisions

Open a real Markdown, SQL, and JSON handover with revision history and a resolved human review.
Open the live demo 2. First handover

Continue it in your workspace

Google sign-in returns you to a prefilled continuation. Review it, publish it, and you have completed the first round trip.
Continue the demo 3. Then automate

Connect your first agent

Connect an interactive MCP host with browser sign-in, or create a named service identity for unattended automation.
Go to agent setup

Agent setup

Connect an agent and read the handover back

Start with browser sign-in and one complete round trip. Handover attributes the agent's work to your user while preserving your company, workspace, and access boundaries.

1. 1

Add the hosted MCP server

Choose your host below and add the canonical Handover endpoint. No employee token needs to be copied into its configuration.
Choose a host 2. 2

Sign in as yourself

The host opens Handover in your browser. Sign in, inspect the client name and requested permissions, then choose Connect agent. Authorization codes are single-use and protected by PKCE. 3. 3

Publish durable context and retrieve it

Ask the connected host to verify its identity, create a small organization-visible handover, and search for it again. The read-back proves the complete continuation path.
Agent promptUse Handover to: 1. Call handover.whoami and show my identity, company, workspace, and scopes. 2. Create "My first handover" with the next step "Read this record and continue." 3. Search for that title and read the current revision back.

Done means read-back, not just connection. The identity is correct, the handover exists, and a later authorized actor can retrieve the durable record without the original chat.

Choose an identity

People sign in. Agents get service credentials.

Authentication determines authorship. Interactive hosts act for the signed-in person; unattended automation uses a separately named, revocable service identity.

Interactive MCP hosts

Browser OAuth

Standard MCP OAuth discovery, dynamic client registration, PKCE, short-lived access tokens, and rotating refresh tokens let each person sign in without sharing a secret. Every revision stays attributed to that person.

View OAuth discovery

Unattended

Named service agent

Create a scoped credential in Company > Agents and store it as HANDOVER_TOKEN. The agent identity, scope, and revocation status remain separate from any employee account.

Create service agent

Agent setup

Connect your MCP host

Interactive hosts use browser sign-in by default. Cline and unattended runners can use a named service credential when they do not support the standard OAuth flow.

Codex

Claude Code

Add Handover at user scope. Claude Code discovers the authorization server and opens the browser sign-in automatically when it connects.

Configurationclaude mcp add --transport http --scope user handover https://handover.sh/api/mcp?profile=core

Gemini CLI

Add the canonical Streamable HTTP endpoint at user scope. Gemini can use Handover's browser authorization flow instead of a pasted employee token.

Configurationgemini mcp add --transport http --scope user handover https://handover.sh/api/mcp?profile=core

Cursor

Add this URL-only entry globally or per project. Cursor discovers OAuth from the server and prompts you to sign in when the connection starts.

Configuration{ "mcpServers": { "handover": { "url": "https://handover.sh/api/mcp?profile=core" } } }

Cline

Open Cline's MCP wizard, choose Remote (HTTP), then add the separately named service credential through its private Static headers prompt.

Configurationcline mcp install handover --transport http https://handover.sh/api/mcp?profile=core

Command line

Install the Handover command

Install the dependency-free command from npm with Node.js 22.13 or newer. The package is MIT licensed and built from the public Handover MCP repository.

Install from npmnpm install --global handover-sh

Direct installercurl -fsSL https://handover.sh/install.sh | sh

Inspect before running

Review the public package source, install.sh, and handover.mjs. Set HANDOVER_URL and HANDOVER_TOKEN for the CLI or another unattended service identity; browser-connected MCP hosts do not need it.

Portable workflows

Install a Handover Agent Skill

Skills teach compatible agents how to publish, resume, review, and govern work safely. MCP or the CLI supplies the authenticated capability; the skill supplies the dependable workflow.

Browse Agent Skills

Verify the connection

Ask the agent to prove continuity

1. Run handover doctor for a read-only CLI diagnostic.
2. Search for a known handover.
3. Read its current revision and one artifact.
4. List open annotations before writing.
5. Continue with expectedRevisionId. Download the complete workflow

Expected result

What a working connection looks like

The host lists Handover's tools, handover.whoami returns the intended person or service agent, and search results are limited to context that identity may access.

1. The MCP transport connects without a JSON or sign-in error.
2. The identity belongs to the expected personal or company workspace.
3. Reads and writes preserve that identity as the author.
4. Revoking the credential immediately prevents further access.