Project Handoffs

🚀 Project Handoffs MCP Server

An MCP server for managing AI session handoffs and next-step tracking.

🚀 Quick Start

The Project Handoffs MCP Server is designed to manage AI session handoffs and next-step tracking. It follows a project-based organizational approach and maps priorities to implementation impacts.

✨ Features

Core Concepts

• NextStep → Working Session → Handoff → New NextStep Link
• Project-based organization
• Priority and implementation impact mapping:
  • core-critical: Crucial for implementation in work.
  • full-required: Necessary for implementing required features.
  • enhancement: Improvements and optimizations.

Available Tools

• list_templates - List available templates for next steps, working sessions, and handoffs.
• create_project - Create a new project to track AI session handoffs.
• delete_project - Delete a project and all its data.
• create_next_step - Create a new next step within a project.
• start_working_session - Start working on the next step.
• create_handoff - Complete the working session and record handoff details.
• get_latest_next_steps - Get open next steps sorted by priority.
• get_next_step_history - Get the full history of a step, including sessions and handoffs.

📦 Installation

npm install
npm run build

📚 Documentation

Configuration

Add the following to your MCP configuration:

{
  "mcpServers": {
    "project-handoffs": {
      "command": "/opt/homebrew/bin/node",
      "args": ["/path/to/project-handoffs/build/index.js"],
      "alwaysAllow": []
    }
  }
}

Project Structure

project-handoffs/
├── src/
│   ├── index.ts           # Main program file
│   ├── templates.ts       # Entity templates
│   ├── types.ts          # TypeScript types
│   └── errors.ts         # Error handling
├── package.json          
└── README.md

Development

# Install dependencies
npm install

# Development mode
npm run dev

# Build
npm run build

🔧 Technical Details

• Error handling implemented through the ProjectError class.
• Template validation for all entity types.
• Consistent state management.
• Secure data persistence with appropriate error handling.
• Type-safe implementation following the project in-memory server pattern.

🛡️ Security

If you discover any security vulnerabilities, please create a new issue with the 'security' label. We take all security reports seriously and will respond promptly.

🤝 Contribution

Contributions are welcome. Please feel free to submit a Pull Request.

📄 License

This project is licensed under the Apache License 2.0 - see the LICENSE file for details.