What is the main functional difference between Handover.tools and Next Devtools MCP?

Handover.tools is categorized under Developer Tools and uses an install path we have not confirmed yet. Next Devtools MCP belongs to Developer Tools and uses a local stdio subprocess. Pick Handover.tools for developer tools work and Next Devtools MCP for developer tools.

How do I install Handover.tools or Next Devtools MCP in Claude Desktop, Cursor, or Windsurf?

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Handover.tools has no confirmed install command yet — follow its own setup instructions.

Are Handover.tools and Next Devtools MCP free to use, or do they require API keys?

Handover.tools is listed as free. Auth: no auth required. Next Devtools MCP is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Can I run both Handover.tools and Next Devtools MCP at the same time in my AI client?

Yes. MCP clients support multiple servers: add handover-tools and vercel-next-devtools-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

Which MCP server has higher directory engagement and quality ratings?

On AllMCPs, Handover.tools has a quality signal of 53/100 (Good) with 0 views, 0 installs and 0 GitHub stars. Next Devtools MCP has 86/100 (Excellent) with 7 views, 0 installs and 828 GitHub stars.

Handover.tools vs Next Devtools MCP

Handover.tools vs Next Devtools MCP | AllMCPs

Feature & specification comparison

Rows where the two servers differ are marked.

Spec	H Handover.tools	Next Devtools MCP
Category	Developer Tools	Developer Tools
Quality signal	53/100 · Good	86/100 · Excellent
Install command	Not confirmed yet	Confirmed
Transport	—	Local subprocess (stdio)
Auth	No auth required	No auth required
Pricing	Free	Free
Required env vars	None listed	None listed
Verified owner	Community listing	Verified
GitHub stars	0	828
Directory activity	0 views 0 installs 0 upvotes	7 views 0 installs 1 upvotes
Tools	8	4
Full listing	View Handover.tools	View Next Devtools MCP

Tools & capabilities

Handover.tools tools 8

handoff_putStore a piece of context and get back a short code. The person gives the link handover.tools/<code> to an agent on another device and it can fetch the content — no copy-paste of long text. The code is 8 letters, easy to type on a phone. NOT ENCRYPTED: the server can read what you store, so never put credentials, tokens, or private data in it. Content becomes unreadable after the TTL expires, and by default it can only be fetched once. The response also returns a revoke_key — keep it for the rest of this session so you can destroy the content immediately with handoff_revoke if the person changes their mind. Writes are limited to a small number per day; reads are not.
handoff_getFetch content stored by handoff_put using its 8-character code. The code is case-insensitive and hyphens are ignored, so 'kvmtrhxp' and 'KVMT-RHXP' are the same; the person may give it as a link like handover.tools/kvmtrhxp, and passing that is fine too. Return the content to the person verbatim and complete: it can be fetched only once. If the code is unknown, already fetched, or expired, content is null with a reason — these cases are deliberately indistinguishable.
handoff_revokeDestroy content stored by handoff_put right now, before its TTL runs out and whether or not it has been fetched. Requires the revoke_key returned by handoff_put — the person fetching with the short code cannot revoke, only the writer can. Use this the moment someone says they sent the wrong thing, or changed their mind. Revoking an already gone item is not an error: the outcome is reported as 'already_gone'.
channel_openStart pairing two agents on different machines for a multi-round exchange (e.g. one explores, the other studies and asks follow-up questions). Use the local client at https://handover.tools/client/channel.py — do not call this by hand. The client generates a secret password locally, and this call returns only a 3-character nameplate; the person gives nameplate + password (8 letters) to the other machine. The server never sees the password, so it cannot impersonate either side (SPAKE2). The person stays in the loop: send only after they approve, fetch only when they ask. Counts as one write against the daily write quota.
channel_joinSecond half of pairing, run by the local client at https://handover.tools/client/channel.py. Send only the first 3 characters of the spoken code (the nameplate) plus this side's SPAKE2 message; the other 5 characters are the password and must never be sent to the server. The nameplate is consumed on success. Returns this side's key and the peer's SPAKE2 message. Unknown, used, or expired nameplates are deliberately indistinguishable.
channel_sendRelay one ciphertext to the other side of a paired channel. The ciphertext must come from the local client at https://handover.tools/client/channel.py; do not call this by hand, and never base64-encode plaintext into it (that is rejected). Only send after the person has seen and approved the draft — the server cannot enforce this, the calling agent must. Returns the message's sequence number and how far the peer has read.
channel_fetchUse the local client at https://handover.tools/client/channel.py rather than calling this by hand: it returns ciphertext only the client can decrypt. Returns the peer's messages this side has not fetched yet, and marks them read so the peer can see they arrived. Call only when the person asks. peek=true reads without marking; after=N re-reads from sequence N (recovery). Side A also receives the peer's SPAKE2 message here to finish pairing. Large backlogs are paged: more=true means fetch again.
channel_closeEither side can close. Deletes the channel, both keys, and every stored message immediately. The other side's next fetch reports not_found_or_closed.

Next Devtools MCP tools 4

nextjs_indexDiscover running Next.js dev servers and list each one's runtime MCP tools.
nextjs_callCall a runtime tool on a discovered server (errors, routes, logs, Server Actions).
nextjs_docsGateway.** Point the agent at version-accurate docs in `node_modules/next/dist/docs/`.
browser_evalGateway.** Point the agent at the [`agent-browser`](https://github.com/vercel-labs/agent-browser) CLI for browser automation.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Handover.tools

No confirmed install command for Handover.tools yet — follow the setup steps linked from its listing page rather than a guessed package name.

Next Devtools MCP

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "vercel-next-devtools-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "next-devtools-mcp@latest"
      ]
    }
  }
}

Handover.tools vs Next Devtools MCP

Which MCP server should you choose?

H
Choose Handover.tools when

Choose Next Devtools MCP when

Feature & specification comparison

Tools & capabilities

Handover.tools tools 8

Next Devtools MCP tools 4

Ready-to-paste client configs

Handover.tools

Next Devtools MCP

Frequently asked questions

HChoose Handover.tools when

Choose Next Devtools MCP when

Handover.tools tools 8

Next Devtools MCP tools 4

Handover.tools

Next Devtools MCP

Frequently asked questions

What is the main functional difference between Handover.tools and Next Devtools MCP?

How do I install Handover.tools or Next Devtools MCP in Claude Desktop, Cursor, or Windsurf?

Are Handover.tools and Next Devtools MCP free to use, or do they require API keys?

Can I run both Handover.tools and Next Devtools MCP at the same time in my AI client?

Which MCP server has higher directory engagement and quality ratings?

Popular comparisons with Handover.tools

Popular comparisons with Next Devtools MCP

H
Choose Handover.tools when