Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Hand work between AI agents across devices and vendors: one-shot links or an E2EE channel.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://handover.tools/mcp在终端中运行这条命令
claude mcp add --transport http handover https://handover.tools/mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"handover": {
"url": "https://handover.tools/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"handover": {
"type": "http",
"url": "https://handover.tools/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://handover.tools/mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过域名 handover.tools 验证(注册中心会核实域名所有权)
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(1.1.0)于19天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Spec Driven Development, Remote Desktop Commander, Tools MCP
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Web production tools for AI agents: contrast, JP text, WebP, JSON-LD, slugs, dates and 40+ more
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
One agent writes it, another agent reads it. You only carry an 8-letter link between them.
handover.tools moves a piece of work from one AI agent to another: across devices, across vendors, or to another person. Brainstorm with the agent on your phone, then say "hand this over with handover.tools". Paste the link it gives you (handover.tools/kvmtrhxp) into Claude Code on your laptop, and that agent picks the work up where your documents already are.
Bring the idea to your context, not your context to the idea.
There is no account and nothing to install. Any agent that can open a web page can use it.
| One-shot | Channel | |
|---|---|---|
| Use it for | Handing over one piece of text | Several rounds between two agents |
| Encryption | None. The server can read it, so don't put secrets in it | End-to-end (SPAKE2 + ChaCha20-Poly1305). The server only ever stores ciphertext |
| Lifetime | Gone after the first read, or after 60 minutes (24 h max) | Until either side closes it |
| What the agent needs | Can open a URL, or has MCP | Can run a Python script (uv run) |
| Who decides | The person carries the link | The person approves every send and starts every fetch |
curl -X POST https://handover.tools/api/handoff/put \
-H 'Content-Type: application/json' \ -d '{"content":"...","label":"notes"}' # → {"code":"kvmtrhxp", "revoke_key":"...", ...} curl "https://handover.tools/api/handoff/get?code=kvmtrhxp"
Opening handover.tools/ doesn't use up the code. That URL returns instructions, and the actual read is a second request. Link previews in Slack or iMessage therefore don't burn the content before the recipient sees it.
curl -so ~/.handoff/channel.py --create-dirs https://handover.tools/client/channel.py
uv run ~/.handoff/channel.py open --name study --brief "..." # machine A: prints a code uv run ~/.handoff/channel.py join kvmtrhxp --name study # machine B uv run ~/.handoff/channel.py send --name study --kind question --file q.md uv run ~/.handoff/channel.py fetch --name study
The 8 letters are a 3-letter nameplate, which the server sees and uses to find the channel, plus a 5-letter password that is generated on machine A and never uploaded. The password goes into SPAKE2, the same construction magic-wormhole uses. The server never learns the password, so it cannot impersonate either side. /client/channel.py is served from client/channel.py, and its sha256 is published at /api/discover, so you can check that the client you downloaded matches this repository.
The threat model, including what we *don't* claim, is at handover.tools/security.
https://handover.tools/mcp. It serves both the 2026-07-28 (modern) and 2025-11-25 and earlier (legacy) protocol eras./llms.txt, /guide.md, /security.md/api/discovertools/list and /api/discover are all derived from a single tool registry (src/registry.py), so they can't drift apart.src/
entry.py routing, MCP (dual-era), content negotiation registry.py @tool decorator — one source for REST, MCP and discover tools/handoff.py, tools/channel.py the two tools guard.py quotas and the operator blocklist meter.py per-call metering page.py, docs.py, style.py the website and docs pages client/channel.py the local E2EE client, run on the user's machine tests/ end-to-end, channel and quota test suites scripts/ dev, deploy, repository checks, operator tools
| Document | What it covers |
|---|---|
| docs/system-design.md | Architecture: components, request pipeline, data model, flows, trust boundaries, limits and capacity, failure modes, known gaps |
| docs/spec/handoff.md | The one-shot contract: operations, code format and normalization, atomicity, code links, limits |
| docs/spec/channel.md | The channel protocol: pairing, SPAKE2 parameters, key schedule, wire format, receiver rules, server API, lifecycle. Detailed enough to write a second client |
| docs/decisions.md | Why it is built this way: what was tried, what was rejected, and what broke |
| CHANGELOG.md | What changed, newest first. Also at handover.tools/changelog |
The specs are the contract. A behavior change starts in the spec, then the code and tests follow.
Requires Node ≥ 22 and Python 3.12.
npm install
scripts/dev.sh # generates src/*_src.py and public/, then runs wrangler dev on :8787 tests/e2e.sh # end-to-end tests against the local server tests/channel.sh # two isolated clients: pairing, tampering, replay tests/quota.sh # quota gates (local only: edits counters directly) scripts/check.sh # repository rules: English only, every Dxx reference resolves
CI runs the check and the three suites on every push.
npx wrangler d1 create , then put the name and id into wrangler.toml.routes pattern to your domain.CLOUDFLARE_API_TOKEN=… scripts/deploy.shTables are created on the first request. scripts/block.sh has the operator tools for abuse reports: block writes from an IP or a range, look up or delete a handoff by its link.
Issues and pull requests are welcome. AGENTS.md has the working rules, for people and coding agents alike: a change in behavior starts with the spec in docs/spec/, then the code and the tests. Report vulnerabilities privately: see SECURITY.md.
MIT. Fonts: Atkinson Hyperlegible, SIL OFL 1.1 (see assets/fonts/LICENSE.txt).