Handover
Server Details
Shared, versioned context that humans and AI agents can publish, review, annotate, and continue.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- 44-pixels/handover-mcp
- GitHub Stars
- 4
- Server Listing
- Handover
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 17 tools
Most tools are clearly scoped to distinct resources, but the comment/annotation family creates real overlap: annotate versus comment for writing feedback, and annotations versus thread for reading discussion state. The descriptions help, but an agent could still easily select the wrong tool in those workflows.
All tools share a consistent handover.* prefix and snake_case style, with strong verb-led names like create, continue, publish, and search. A few noun-led read tools such as annotations, publication, and thread, plus the okf.* submodule, break the otherwise uniform pattern.
With 17 tools, this is on the higher end, but the scope is broad: revision lifecycle, artifact reading, comment and annotation workflows, publication, search, and OKF interchange. Each tool has a recognizable role, so the count feels slightly over the ideal range rather than bloated.
The surface covers the full durable-handover lifecycle: create, continue, read, export, import, publish, search, and collaborate through comments and assignments. The immutability of revisions makes explicit update/delete tools unnecessary, and the continuation mechanism addresses evolution without creating gaps.
Available Tools
17 toolshandover.annotateAnnotate a handover artifactAInspect
Add 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: body (required), target (required), handoverId (required), mentionPrincipalIds.
handover.annotationsRead artifact annotationsARead-onlyIdempotentInspect
Read revision-anchored file comments, selected text, status, authorship, and resolution metadata. Use status=open to find feedback that still needs action.
Inputs: handoverId (required), status, artifactId, revisionId.
handover.assignSet handover ownersAInspect
Replace the open assignments with the supplied collaborator identities. This changes collaboration state, not the immutable handover revision.
Inputs: handoverId (required), principalIds (required).
handover.commentComment on a handoverAInspect
Append a discussion comment and optionally notify explicitly mentioned collaborators.
Inputs: body (required), handoverId (required), mentionPrincipalIds.
handover.continueContinue a handoverAInspect
Append 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 (required), expectedRevisionId (required), note, brief, +1 more.
handover.createCreate a handoverAInspect
Create durable shared context with an initial immutable revision. Authorship comes from the authenticated Handover identity.
Inputs: title (required), note, brief, summary, +1 more.
handover.getInspect a handoverARead-onlyIdempotentInspect
Read a handover snapshot, continuation brief, artifact metadata, and revision history. Omit revisionId for the current snapshot.
Inputs: handoverId (required), revisionId.
handover.okf.exportExport a handover as OKFBRead-onlyIdempotentInspect
Export a handover revision as an Open Knowledge Format bundle for another human or agent system.
Inputs: handoverId (required), revisionId.
handover.okf.importImport an OKF bundleBInspect
Import Open Knowledge Format files into a new immutable Handover revision. Replaying the same bundle is idempotent.
Inputs: files (required), handoverId (required), mode, expectedRevisionId.
handover.publicationInspect a published reportARead-onlyIdempotentInspect
Read the stable report URL, entry file, access mode, and selected revision for a handover.
Inputs: slug, handoverId.
handover.publishPublish a handover as a reportAInspect
Create or update a stable /r/{slug}/ report projection of a Handover revision.
Inputs: handoverId (required), slug, access, entryPath, +2 more.
handover.pullPull a published reportBRead-onlyIdempotentInspect
Return the selected files of a published report with paths, hashes, media types, and UTF-8 or base64 content.
Inputs: slug (required), files, includeBinary.
handover.read_artifactRead a handover artifactARead-onlyIdempotentInspect
Read 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 (required), maxBytes.
handover.searchSearch handoversARead-onlyIdempotentInspect
Find current shared context with hybrid, semantic, or lexical retrieval across metadata and artifact content. Use an empty query to list recent handovers.
Inputs: mode, limit, query, cursor, +1 more.
handover.threadRead a handover discussionARead-onlyIdempotentInspect
Read comments, explicit mentions, assignments, and eligible collaborators without changing revision history.
Inputs: handoverId (required).
handover.update_commentEdit or resolve a commentAInspect
Edit an authored comment, or resolve/reopen an annotation. Set resolvedRevisionId when a new handover revision addressed the feedback.
Inputs: commentId (required), handoverId (required), body, status, +3 more.
handover.whoamiVerify the active identityARead-onlyIdempotentInspect
Return the authenticated person or service agent, organization, workspace, role, and granted scopes. Call this before reading or publishing to confirm attribution and tenancy.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Shared project context for AI agents and teams: docs, tasks, and messages that stay current.
Shared persistent memory for AI agents to read, verify, continue, and connect knowledge.
Shared, permission-aware company context for AI agents, with provenance, approvals and audit.
Your portable context layer — load it into any AI.
Related MCP Servers
- AlicenseAqualityBmaintenanceEnables teams to share structured, git-synced context among AI coding agents working on the same repository, including living plans, task declarations, handoff briefs, file-provenance history, and conflict detection.1227 npm2MIT
- AlicenseNot gradedqualityBmaintenanceEnables Claude, ChatGPT, and local agents to share one hosted memory layer over the Model Context Protocol, storing per-project state cards and append-only logs as git-versioned markdown with keyword search. Supports conflict-safe state rewrites, output caps to keep token use low, and OAuth or path-token access control.MIT
- AlicenseNot gradedqualityDmaintenanceShared memory hub for LLMs to persist and share project context, enabling seamless handoffs between different AI agents.16 npm1MIT
- AlicenseBqualityBmaintenanceProvides a shared context layer for AI agent teams to improve token efficiency through context deduplication and incremental state sharing. It enables multiple agents to coordinate tasks, share real-time discoveries, and manage dependencies while significantly reducing redundant data transmission.1508MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.