Handover

MCP文档知识

提供方 未标注

文档知识 stdio · 本地进程 未标注 社区 / 第三方 ClaudeCursorVS CodeCline
查看接入方式

共享的、版本化的上下文,人类和AI代理可以查看并继续使用。

一句话选型结论

按资料字段整理

Handover 属于文档知识类 MCP 服务器,stdio · 本地进程,鉴权方式未标注,可直接接入 Claude、Cursor、VS Code 等,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类文档知识 传输方式stdio · 本地进程 鉴权未标注 部署方式本地部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

文档知识
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

记忆

安装与配置

stdio · 本地进程 未标注
客户端在本机拉起子进程,数据不出本机
npx skills add 44-pixels/handover-mcp --list npx skills add 44-pixels/handover-mcp --skill handoff npx skills add 44-pixels/handover-mcp --skill handover-record npx skills add 44-pixels/handover-mcp --skill handover-publish npx skills add 44-pixels/handover-mcp --skill handover-test-continuity

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Node.js 等运行时,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
文档检索问答

在你的文档库里按问题找答案。

知识库读写

把新资料写进知识库,随用随取。

内容整理

把零散资料归纳成结构化笔记。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude、Cursor、VS Code,换客户端不用重新研究配置。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在文档知识场景里让模型直接调用外部能力的人。
  • 已经在用 Claude、Cursor 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Handover当前 未标注 stdio · 本地进程 本地部署 有 未标注
dify 未标注 stdio · 本地进程 本地部署 有 2026-04-11
open-webui 未标注 stdio · 本地进程 本地部署 有 2026-04-11
JeecgBoot 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Cherry Studio 未标注 未标注 未标注 无 2026-05-17
mempalace 未标注 stdio · 本地进程 本地部署 有 2026-04-11

服务器档案

文档知识
字段来自项目仓库与公开索引,中文说明由本站标注
提供方未标注上游标注的维护方 未标注
分类文档知识本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式未标注远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

15.2 KB
来自项目仓库与上游目录的原文,未做删改

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.```bash
    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:```text
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.

Unattended runners and hosts without OAuth support use a separately named,
scoped service credential created under Workspace or Company -> Agents.
Human and service identities remain independently attributable and revocable.

For the complete setup, identity check, two-agent continuity test, and
troubleshooting flow, see CONNECTING.md.

Codex```bash

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


### Claude Code```bash
claude mcp add --transport http --scope user \
  handover https://handover.sh/api/mcp?profile=core

Gemini CLI```bash

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


### Cursor

Add this to `.cursor/mcp.json`. Cursor discovers Handover's authorization
server and prompts for browser sign-in when the connection starts:```json
{
  "mcpServers": {
    "handover": {
      "url": "https://handover.sh/api/mcp?profile=core"
    }
  }
}

Cline

Open Cline's MCP wizard:```bash
cline mcp install handover --transport http https://handover.sh/api/mcp?profile=core


Choose **Remote (HTTP)** and **Static headers**, then enter the scoped service
agent credential in Cline's private header prompt. The agent-readable
`llms-install.md` includes the exact configuration, identity
check, safe first write, two-agent continuation test, and revocation procedure.
Use the first-party Cline setup
page
for the complete Handover flow. Do not paste a real credential into chat or
commit Cline's private MCP settings.

## Command-line client

The dependency-free Handover CLI supports the same durable workflow from a
terminal:```bash
npm install --global handover-sh
handover login
handover doctor
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:```bash
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.

`handover doctor` is a read-only connection check. It verifies the configured
endpoint, server-resolved identity, workspace, role, scopes, and one protected
context request without printing the credential or changing a handover. Use
the complete verification checklist
before an agent's first write.

## Agent Skills

Install reusable Handover workflows into a compatible coding agent with the
open Agent Skills format:```bash
npx skills add 44-pixels/handover-mcp --list
npx skills add 44-pixels/handover-mcp --skill handoff
npx skills add 44-pixels/handover-mcp --skill handover-record
npx skills add 44-pixels/handover-mcp --skill handover-publish
npx skills add 44-pixels/handover-mcp --skill handover-test-continuity

The public collection includes a local-first session handoff, skills for
creating and validating machine-readable records, verifying connections,
publishing context, resuming work,
reviewing revision-anchored feedback, testing complete multi-identity
continuity, and governing agent access. Browse the
catalog at skills.handover.sh or inspect the
source in skills/. The collection is also indexed in the
Skills.sh directory.
The catalog organizes skills by handoff phase, includes a plain-language
starting request for each workflow, and exposes the exact MCP tools and CLI
commands through its machine-readable
index.

The runtime is independently listed as
sh.handover/handover in the official MCP
Registry.

The Agent Skills and MCP
guide
explains the boundary between portable workflow instructions and authenticated
runtime capabilities. Its raw end-to-end
workflow
is designed for direct agent retrieval.

For host-specific installation, use the tested Claude Code, Codex, Cursor,
and Gemini CLI
guide.
Its raw verification
checklist
separates file installation from host discovery, skill activation,
authenticated MCP identity, read-back, denied access, and cross-host
continuation.

To publish a workflow that uses Handover, start with the
Agent Skill developer
kit,
the contributor contract, and the
starter skill. Copy the starter
into a new skills//SKILL.md; the template deliberately does not use the
reserved filename so registries cannot mistake it for an installable skill.
Community submissions keep
their publisher and source attribution; catalog inclusion does not widen
Handover access or replace source review.

Validate the local contract before testing the authenticated workflow:```bash
node templates/handover-skill/validate.mjs skills/<name>/SKILL.md


Passing this validator proves the file contract, not host discovery, MCP
authentication, permissions, read-back, or denied behavior. The developer kit
keeps those runtime checks explicit.

## Open continuity benchmark

The AI Handoff Continuity
Benchmark
tests whether a successor model can recover the objective, current state,
decisions, evidence, constraints, next action, owner, and open questions from
a transcript, compressed memory, or structured handoff.

The first two-system pilot scored structured handoffs at 79.45, conversation
transcripts at 76.67, and compressed memory at 45.00. It is a small authored
pilot rather than a model leaderboard. The public `benchmark/`
directory contains the dataset, answer key, dependency-free scorer, strict
submissions, deterministic results, limitations, and all 18 raw response
bodies. Reuse the published
`CITATION.cff`,
`citation.bib`, or flat
`summary.csv` instead of
transcribing values from the page.```bash
cd benchmark/v1
node run.mjs --validate-scorer
node run.mjs --prompts ./prompts

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:

  1. Call handover.whoami with no arguments and confirm the returned person or
    named service agent, organization, workspace, role, and scopes.
  2. Call handover.search with { &quot;query&quot;: &quot;&quot; } and confirm it returns only
    context that identity should be able to access.
  3. 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 after
the OAuth grant or 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.bash export HANDOVER_TOKEN=&#x27;hnd_tok_...&#x27; codex mcp add handover \ --url https://handover.sh/api/mcp?profile=core \ --bearer-token-env-var HANDOVER_TOKEN

Discovery and documentation

  • No-login continuation demo
  • AI agent handoff checklist
  • Company AI context readiness checklist
  • Shared knowledge base architecture guide
  • End-to-end reviewed MCP handoff
  • Rendered MCP handoff guide
  • Install and host-specific setup
  • MCP memory setup for Claude Code, Cursor, and Codex
  • Raw cross-host setup and continuity test
  • Claude Code to Codex context transfer
  • Rendered Claude Code to Codex guide
  • Connection and verification runbook
  • MCP workflow guide
  • MCP OAuth vs service accounts
  • Preserve context across AI coding agents
  • Migrate static report folders
  • Glama hosted connector
  • Machine-readable host recipes
  • MCP server manifest
  • Agent tool manifest
  • OpenAPI document
  • Agent-readable knowledge corpus
  • Security model

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.

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
Handover 怎么安装?

在客户端按下面的安装命令接入:npx skills add 44-pixels/handover-mcp --list npx skills add 44-pixels/handover-mcp --skill handoff npx skills add 44-pixels/handover-mcp --skill handover-record npx skills add 44-pixels/handover-mcp --skill handover-publish npx skills add 44-pixels/handover-mcp --skill handover-test-continuity。装完在客户端配置里引用同一个包或端点。

Handover 怎么在 Claude、Cursor、VS Code 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Handover 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Handover 需要 API Key 吗?

资料没有标注鉴权方式,是否需要密钥取决于服务本身,接入前按官方文档确认。

Handover 支持哪些客户端?

资料标注支持 Claude、Cursor、VS Code、Cline、Gemini CLI、Codex;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Handover 能提供哪些能力?

资料显示能力标签包括 记忆。具体工具清单以官方文档为准。

Handover 需要什么运行环境?

属于本地进程,需要在本机装好运行环境。

Handover 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。