AI Collaboration 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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| send_directiveB | Send a task directive to the development team. Can create single or batch tasks with dependencies. |
| send_batch_directivesB | Send multiple task directives at once. Use this to queue up multiple tasks for efficient workflow. |
| submit_workC | Submit completed work for review |
| review_workC | Submit a review of submitted work |
| ask_questionC | Ask a question about a task |
| answer_questionB | Answer a previously asked question |
| get_all_tasksB | Get all tasks in the system |
| get_task_statusB | Get status of a specific task |
| pingA | Simple ping to test server connectivity |
| update_project_stateC | Update the state of a project component |
| get_project_stateC | Get current project state |
| generate_reportC | Generate a project status report |
| initC | Initialize agent with role-based autonomous workflow |
| stop_autonomous_workC | Stop autonomous work mode |
| statusC | Get current system status |
| create_missionC | Create a new mission |
| create_ticketC | Create a new ticket |
| update_ticketC | Update an existing ticket |
| list_ticketsB | List tickets with optional filtering |
| generate_context_summaryC | Generate a summary of current project context |
| start_autonomous_loopC | Start an autonomous work loop that continuously checks for and processes work |
| stop_autonomous_loopC | Stop the autonomous work loop |
| get_loop_statusC | Get the current status of the autonomous loop |
| create_project_planB | Create a comprehensive project plan with multiple phases |
| get_project_planB | Get the current active project plan |
| update_plan_progressC | Update project plan progress when phase is complete |
| diagnose_tasksB | Diagnose task state discrepancies between project state and actual tasks |
| reset_task_dependenciesA | Reset task dependencies for tasks that are blocked by completed/missing tasks |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| All Tasks | View all tasks in the system |
| Project State | Current state of all project components |
| Communication Logs | All communication between AIs |
| All Missions | View all missions and their progress |
| Role Configuration | View role definitions and agent assignments |
| All Tickets | View bugs, enhancements, tech debt, and implementation plans |
| Project Context | Current project context and onboarding information |
| Handoff Document | Generated handoff document with current project state |
TDQS
Scored across 28 tools
Most tools have distinct purposes but there is some overlap between create_mission, create_project_plan, and send_directive for task creation. Also, ask_question/answer_question are clear pairs. Overall, an agent can distinguish, but minor ambiguity exists.
Tool names follow a mostly consistent verb_noun pattern in snake_case (e.g., create_mission, get_project_state). However, a few tools like 'ping', 'status', and 'init' lack a noun after the verb, deviating from the pattern.
28 tools is slightly high but reasonable for a collaboration server covering missions, projects, tasks, tickets, autonomous loops, and reporting. The scope justifies the count, though some consolidation could help.
The tools cover core lifecycle operations for projects and tickets but are missing delete operations for missions, tasks, and tickets. Also, no explicit update_task tool exists. This leaves some gaps that agents may need to work around.