Handover MCP
Handover is shared, versioned context for humans and AI
agents. This repository is the public discovery and connection record for
Handover's hosted Model Context Protocol server.
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.
Connect
The canonical Streamable HTTP endpoint is:
https://handover.sh/api/mcp
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.
Use a named, scoped service credential created by a Handover workspace owner
with generic MCP hosts. Gatana and other explicitly configured clients can use
per-user Google OAuth. Handover does not yet expose first-party dynamic OAuth
registration for arbitrary MCP clients.
Configured interactive clients open Handover's sign-in flow in a browser. Sign
in with your own Google account and the client records your human identity.
Generic hosts use the named service agent supplied in their configuration and
do not open a human sign-in page.
Codex
export HANDOVER_TOKEN='hnd_tok_...'
codex mcp add handover \
--url https://handover.sh/api/mcp \
--bearer-token-env-var HANDOVER_TOKEN
Claude Code
claude mcp add --transport http --scope user \
--header "Authorization: Bearer $HANDOVER_TOKEN" \
handover https://handover.sh/api/mcp
Gemini CLI
gemini mcp add --transport http --scope user \
--header "Authorization: Bearer $HANDOVER_TOKEN" \
handover https://handover.sh/api/mcp
Cursor
Export HANDOVER_TOKEN, then add this to .cursor/mcp.json:
{
"mcpServers": {
"handover": {
"url": "https://handover.sh/api/mcp",
"headers": {
"Authorization": "Bearer ${env:HANDOVER_TOKEN}"
}
}
}
}
Command-line client
The dependency-free Handover CLI supports the same durable workflow from a
terminal:
npm install --global handover-sh
handover login
handover search "billing migration"
handover pull <slug-or-url> --out ./continued-work
handover publish ./report --title "Weekly report"
The published package source and metadata live in cli/. The audited
direct installer remains available when npm is not appropriate:
curl -fsSL https://handover.sh/install.sh | sh
Package releases are built from this public repository. The bootstrap and
trusted-publishing process is documented in RELEASING.md.
What agents can do
Connected agents can:
- verify the active identity, organization, workspace, and scopes with
handover.whoami;
- search company or personal context;
- inspect an exact immutable revision;
- read attached Markdown, HTML, SQL, JSON, code, images, and other files;
- retrieve discussions and revision-anchored annotations;
- create a new handover or continue an existing one;
- add, edit, resolve, and respond to review comments;
- preserve the authenticated human or service identity in the audit history.
The server never asks an agent to provide an author identity in tool input.
Authorship comes from the authenticated credential.
Verify the connection
Ask the connected host to perform these calls before real work:
- Call
handover.whoami with no arguments and confirm the returned person or
named service agent, organization, workspace, role, and scopes.
- Call
handover.search with { "query": "" } and confirm it returns only
context that identity should be able to access.
- Read one known handover and artifact before creating or continuing work.
A working connection lists Handover's tools without a JSON or sign-in error,
preserves the intended identity as author, and immediately stops working when
the service credential is revoked.
Service agents
Workspace owners create service agents in Handover and grant only the scopes
that actor needs. Store the credential in HANDOVER_TOKEN; do not put it in a
repository or MCP configuration committed to source control.
export HANDOVER_TOKEN='hnd_tok_...'
codex mcp add handover \
--url https://handover.sh/api/mcp \
--bearer-token-env-var HANDOVER_TOKEN
Discovery and documentation
Source and support
The hosted Handover application source is maintained in a private repository.
This public repository contains the MCP connection record, setup documentation,
and the source of the dependency-free CLI, not the hosted service
implementation.
Report connection or documentation problems through
GitHub Issues. Report
security concerns using the process in SECURITY.md.