Labsco
MCP SERVER

Project Handoffs

by davidorex

Keeps a chain of next steps, working sessions and handoffs per project, so the next AI session starts from what the last one actually left behind.

Agent Memory
Summary
The next session starts where the last one stopped.

Context does not survive between sessions, so the handoff has to be written down somewhere structured. The priority levels are the useful part: core-critical, full-required and enhancement say what breaks if the step gets skipped.

What it is

An MCP server for tracking handoffs between AI sessions. Work moves through a fixed chain — a next step becomes a working session, which closes as a handoff, which creates the next next step — with everything scoped to a project.

What you get
  • Projects created, and deleted with all their data
  • Next steps created and ranked as core-critical, full-required or enhancement
  • A working session started against a next step
  • A session closed as a handoff, with its details recorded
  • Open next steps returned in priority order
  • The complete history of a next step, its session and its handoff included
  • Templates listed for next steps, working sessions and handoffs
Requirements

Node: npm install then npm run build, and point your client at the built build/index.js. Apache 2.0 licensed.