Skip to main content
Glama
davidorex

Project Handoffs MCP Server

by davidorex
README.md
# Project Handoffs MCP Server

MCP server for managing AI session handoffs and next steps tracking.

## Core Concepts

- NextStep → WorkingSession → Handoff → New NextStep chains
- Project-based organization
- Priority levels mapped to implementation impact:
  - core-critical: Critical for working implementation
  - full-required: Necessary for desired implementation
  - enhancement: Improvements and optimizations

## Available Tools

- `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

## Installation

```bash
npm install
npm run build
```

## Configuration

Add to your MCP configuration:

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

## Project Structure

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

## Development

```bash
# Install dependencies
npm install

# Development mode
npm run dev

# Build
npm run build


## Implementation Details

- Error handling through ProjectError class
- Template validation for all entity types
- Consistent state management
- Safe data persistence with proper error handling
- Type-safe implementation following project-memory-server patterns

## Security

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

## Contributing

Contributions are welcome. Feel free to submit a Pull Request.

## License

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

TDQS

B3.2/5.0

Scored across 8 tools

Disambiguation4/5

Most tools have distinct purposes, but 'create_handoff' and 'start_working_session' could be slightly ambiguous as both relate to working sessions. The other tools clearly target different resources like projects, next steps, and templates, with minimal overlap in functionality.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern using snake_case, such as 'create_project', 'delete_project', 'get_latest_next_steps', and 'list_templates'. This uniformity makes the set predictable and easy to navigate for an agent.

Tool Count5/5

With 8 tools, this server is well-scoped for managing project handoffs, covering key operations like creating, deleting, and retrieving projects, next steps, and sessions. The count is neither too sparse nor overwhelming, fitting the domain effectively.

Completeness4/5

The tool set provides good coverage for project handoffs, including CRUD for projects and next steps, session management, and template listing. A minor gap exists in updating or deleting next steps and handoffs, which could limit agent flexibility in modifying existing data.

Maintenance

ActivityInactive
ResponsivenessNo issues