Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Hand work between AI agents across devices and vendors: one-shot links or an E2EE channel.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://handover.tools/mcpRun this in your terminal
claude mcp add --transport http handover https://handover.tools/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"handover": {
"url": "https://handover.tools/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"handover": {
"type": "http",
"url": "https://handover.tools/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://handover.tools/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified against the domain handover.tools (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.1.0) reached the registry 19 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, EmbeddedCI BenchPod
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
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.
Drive a BenchPod hardware-in-the-loop bench: power, flash, UART, I2C, CAN, analog and logic.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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).