The Project Handoffs MCP Server is a tool for managing AI session handoffs and tracking next steps within projects.
With this server, you can:
Create and delete projects for organizing your work
Create next steps with title, description, priority, dependencies, and parent steps
Start working sessions for specific next steps
Complete sessions by creating handoffs with details about completed work, code state, unresolved issues, and new next steps
Retrieve open next steps ordered by priority
View complete history for specific next steps
Access templates for next steps, working sessions, and handoffs
Prioritize tasks using levels like 'core-critical', 'full-required', and 'enhancement'
Referenced in the configuration example for running the MCP server, used to locate the Node.js executable on macOS systems.
Manages dependencies and provides build scripts for the project handoffs MCP server, supporting installation and development workflows.
Uses TypeScript for type-safe implementation of the project handoffs tracking system, including proper error handling and consistent state management.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Project Handoffs MCP Server create a new project for the customer portal redesign"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP server for managing AI session handoffs and next steps tracking.
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
Related MCP server: handoff-mcp
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
npm install
npm run buildAdd to your MCP configuration:
{
"mcpServers": {
"project-handoffs": {
"command": "/opt/homebrew/bin/node",
"args": ["/path/to/project-handoffs/build/index.js"],
"alwaysAllow": []
}
}
}project-handoffs/
├── src/
│ ├── index.ts # Server implementation
│ ├── templates.ts # Entity templates
│ ├── types.ts # TypeScript types
│ └── errors.ts # Error handling
├── package.json
└── README.md# 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.Complete a working session with handoff details
Inputs: projectId (required), sessionId (required), completedWork (required), codeState (required), +3 more.
Create a new next step in a project
Inputs: projectId (required), title (required), description (required), priority (required), +2 more.
Create a new project for tracking AI session handoffs
Inputs: name (required), description (required).
Delete a project and all its data
Inputs: projectId (required).
Get open next steps ordered by priority
Inputs: projectId (required).
Get complete history of a next step including session and handoff
Inputs: projectId (required), stepId (required).
List available templates for next steps, working sessions, and handoffs
Inputs: no named parameters.
Start working on a next step
Inputs: projectId (required), nextStepId (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 8 tools
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.
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.
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.
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.
AI-native project management for tasks, docs, collaboration, and agents.
Project management for AI agents: tasks, docs, decisions and time in one shared team context.
Manage tasks, projects, roadmaps, files, meetings, and team workflows with AI tools.
Project management for teams and their AI agents.
