LabscoMCP early access ↗
dazebMCP SERVER · OFFICIAL PROJECT

MCP Handoff Server

Write down where the work stopped and what comes next, so whoever picks it up does not start blind.

by dazeb ↗Agent Memory✓ Official

LABSCO SUMMARY

Continuity kept as a document rather than a memory.

Work that passes between agents, or between an agent and a person, usually loses its context at the handover. Templated handoffs with an explicit next step and a lifecycle from active to archived make the transfer a written artifact instead of a scrollback search.

What it is

An MCP server that stores structured handoff documents — current state, status, next step, environment — and tracks each one from creation through to archive.

What you get

  • Handoffs created from templates rather than as free text
  • An existing handoff read back in full, including its recorded environment status
  • Progress appended as updates while the work moves
  • A handoff marked complete when the work is finished
  • Completed handoffs archived, keeping the active list short
  • Handoffs listed and filtered, so past work stays findable
  • An HTTP mode with a health endpoint, for testing outside an MCP client

Requirements

npx -y mcp-handoff-server — nothing to install, and the folders and templates are created on first run. No account or key.

Setup effort

One command — npx -y mcp-handoff-server