Index / MCP servers / Handover

Handover MCP server

Handover is a remote MCP server that gives an AI agent 17 tools, among them handover.annotate, handover.annotations, handover.assign. It answers at https://handover.sh/api/mcp?profile=core over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 12 September 2026; the last check, on 24 October 2026, succeeded.

Status
Answering
Tools
17
Official
yes, served from handover.sh
Reliability
6 of 6 checks
Response time
2055 ms
Transport
streamable HTTP
Last checked
24 October 2026

Shared, versioned context that humans and AI agents can publish, review, annotate, and continue.

Description as the publisher wrote it.

The 17 tools Handover offers

ToolWhat it does
handover.annotateAdd a durable comment anchored to selected text or lines in an immutable artifact revision. Read the artifact first and preserve the exact quote and surrounding context.
Inputs: handoverId, body, target, mentionPrincipalIds
handover.annotationsRead revision-anchored file comments, selected text, status, authorship, and resolution metadata. Use status=open to find feedback that still needs action.
Inputs: handoverId, artifactId, revisionId, status
handover.assignReplace the open assignments with the supplied collaborator identities. This changes collaboration state, not the immutable handover revision.
Inputs: handoverId, principalIds
handover.commentAppend a discussion comment and optionally notify explicitly mentioned collaborators.
Inputs: handoverId, body, mentionPrincipalIds
handover.continueAppend an immutable revision after reading the current snapshot. expectedRevisionId is mandatory to prevent overwriting another collaborator's work. Omitted artifacts are inherited; matching names are replaced.
Inputs: handoverId, expectedRevisionId, note, brief, artifacts
handover.createCreate durable shared context with an initial immutable revision. Authorship comes from the authenticated Handover identity.
Inputs: title, summary, note, brief, artifacts
handover.getRead a handover snapshot, continuation brief, artifact metadata, and revision history. Omit revisionId for the current snapshot.
Inputs: handoverId, revisionId
handover.okf.exportExport a handover revision as an Open Knowledge Format bundle for another human or agent system.
Inputs: handoverId, revisionId
handover.okf.importImport Open Knowledge Format files into a new immutable Handover revision. Replaying the same bundle is idempotent.
Inputs: handoverId, expectedRevisionId, mode, files
handover.publicationRead the stable report URL, entry file, access mode, and selected revision for a handover.
Inputs: handoverId, slug
handover.publishCreate or update a stable /r/{slug}/ report projection of a Handover revision.
Inputs: handoverId, slug, entryPath, access, revisionMode, revisionId
handover.pullReturn the selected files of a published report with paths, hashes, media types, and UTF-8 or base64 content.
Inputs: slug, files, includeBinary
handover.read_artifactRead bounded artifact content after inspecting a handover. Text is returned as UTF-8 and binary content as base64; truncated results report that explicitly.
Inputs: artifactId, maxBytes
handover.searchFind current shared context with hybrid, semantic, or lexical retrieval across metadata and artifact content. Use an empty query to list recent handovers.
Inputs: query, mode, status, limit, cursor
handover.threadRead comments, explicit mentions, assignments, and eligible collaborators without changing revision history.
Inputs: handoverId
handover.update_commentEdit an authored comment, or resolve/reopen an annotation. Set resolvedRevisionId when a new handover revision addressed the feedback.
Inputs: handoverId, commentId, body, target, mentionPrincipalIds, status
handover.whoamiReturn the authenticated person or service agent, organization, workspace, role, and granted scopes. Call this before reading or publishing to confirm attribution and tenancy.

Add Handover to your AI client

Every block below points at https://handover.sh/api/mcp?profile=core. Pick your client and copy.

Claude Code: one command in your terminal
claude mcp add --transport http handover https://handover.sh/api/mcp?profile=core
Claude Desktop: claude_desktop_config.json
{
  "mcpServers": {
    "handover": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://handover.sh/api/mcp?profile=core"]
    }
  }
}
Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json in a project
{
  "mcpServers": {
    "handover": {
      "url": "https://handover.sh/api/mcp?profile=core"
    }
  }
}
VS Code and GitHub Copilot: .vscode/mcp.json
{
  "servers": {
    "handover": {
      "type": "http",
      "url": "https://handover.sh/api/mcp?profile=core"
    }
  }
}
Zed: Zed settings.json
{
  "context_servers": {
    "handover": {
      "url": "https://handover.sh/api/mcp?profile=core"
    }
  }
}
Windsurf: ~/.codeium/mcp_config.json
{
  "mcpServers": {
    "handover": {
      "serverUrl": "https://handover.sh/api/mcp?profile=core"
    }
  }
}
JetBrains AI Assistant: Settings, Tools, AI Assistant, MCP, New MCP Server, as JSON
{
  "mcpServers": {
    "handover": {
      "url": "https://handover.sh/api/mcp?profile=core"
    }
  }
}
Continue: .continue/mcpServers/neuronto.yaml
name: Handover
version: 0.0.1
schema: v1
mcpServers:
  - name: Handover
    type: streamable-http
    url: https://handover.sh/api/mcp?profile=core
Gemini CLI: ~/.gemini/settings.json
{
  "mcpServers": {
    "handover": {
      "httpUrl": "https://handover.sh/api/mcp?profile=core"
    }
  }
}
Codex CLI: MCP server config
{
  "mcpServers": {
    "handover": {
      "type": "http",
      "url": "https://handover.sh/api/mcp?profile=core"
    }
  }
}
Warp: MCP servers, + Add, paste JSON
{
  "mcpServers": {
    "handover": {
      "url": "https://handover.sh/api/mcp?profile=core"
    }
  }
}
Goose: a one-click extension link
goose://extension?url=https%3A%2F%2Fhandover.sh%2Fapi%2Fmcp%3Fprofile%3Dcore&type=streamable_http&id=handover&name=Handover

Is Handover up right now?

It answered our last check on 24 October 2026 in 2055 ms. Over 6 checks since 12 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.

MCP servers similar to Handover

Questions about Handover

Is there an official Handover MCP server?

Yes. It is published by handover.sh and served from handover.sh, the vendor's own domain: https://handover.sh/api/mcp?profile=core.

How many tools does Handover have?

17, as returned by the server's own tools/list on 23 September 2026: handover.annotate, handover.annotations, handover.assign, handover.comment, handover.continue, handover.create, handover.get, handover.okf.export, and 9 more.

Is Handover down?

It answered our last check on 24 October 2026 in 2055 ms. Over 6 checks since 12 September 2026 it answered 6.

How do I add Handover to Cursor?

Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://handover.sh/api/mcp?profile=core. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.

Does Handover need an API key?

It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.

Where this comes from

Publisher: sh.handover. Endpoint host: handover.sh. ARD identifier: urn:air:sh.handover:mcp:handover. First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page is inferred from its name. Ranking in Neuronto search is never for sale.

Is this your server? Get a message the day it stops answering or its tools change: monitoring, 14 days free. Or claim the domain to manage how it is listed.