Project Handoffs MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_templatesB | List available templates for next steps, working sessions, and handoffs |
| create_projectB | Create a new project for tracking AI session handoffs |
| delete_projectC | Delete a project and all its data |
| create_next_stepC | Create a new next step in a project |
| start_working_sessionC | Start working on a next step |
| create_handoffC | Complete a working session with handoff details |
| get_latest_next_stepsB | Get open next steps ordered by priority |
| get_next_step_historyC | Get complete history of a next step including session and handoff |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
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.