Project Handoffs MCP Server

MCP server for managing AI session handoffs and next steps

Local serverstdioTypeScript

What is the Project Handoffs MCP server?

MCP server for managing AI session handoffs and next steps. Exposed over MCP by the project handoffs mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

Its toolset

Everything the assistant can do here goes through one of these:

  • list_templates — List available templates for next steps, working sessions, and handoffs
  • create_project — Create a new project for tracking AI session handoffs
  • delete_project — Delete a project and all its data
  • create_next_step — Create a new next step in a project
  • start_working_session — Start working on a next step
  • create_handoff — Complete a working session with handoff details
  • get_latest_next_steps — Get open next steps ordered by priority
  • get_next_step_history — Get complete history of a next step including session and handoff

Adding it to your client

Installation goes through your MCP client rather than a global install: point it at npm on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Project Handoffs's toolset — list_templates, create_project, delete_project and 5 more — is a fair guide to whether it matches your workflow. It is maintained by davidorex; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Project Handoffs's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the project handoffs mcp server does with a few real requests.

Available tools

ToolWhat it does
list_templatesList available templates for next steps, working sessions, and handoffs
create_projectCreate a new project for tracking AI session handoffs
delete_projectDelete a project and all its data
create_next_stepCreate a new next step in a project
start_working_sessionStart working on a next step
create_handoffComplete a working session with handoff details
get_latest_next_stepsGet open next steps ordered by priority
get_next_step_historyGet complete history of a next step including session and handoff

How to install the Project Handoffs MCP server

{
  "mcpServers": {
    "project-handoffs": {
      "command": "npx",
      "args": ["-y", "npm"]
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Example prompts to try

  • Use Project Handoffs to list templates.
  • Use Project Handoffs to create project.
  • Use Project Handoffs to delete project.

Frequently asked questions

It connects Project Handoffs to MCP-compatible AI assistants such as Claude and Cursor, exposing 8 tools (list_templates, create_project, delete_project, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Project Handoffs directly.