AI Collaboration MCP Server
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., "@AI Collaboration MCP Server initialize project with Gemini as CTO and start the autonomous loop"
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.
AI Collaboration MCP Server
π§ Work in Progress - Active Development π§
A Model Context Protocol (MCP) server designed to facilitate direct AI-to-AI collaboration between Claude and Gemini, eliminating the need for human intermediation in development workflows.
Note: This project is under active development. While core features are functional, some aspects are still being refined. Contributions and feedback are welcome!
π― Project Goal
Enable truly autonomous AI-to-AI collaboration where:
AI agents work continuously on complex projects
Human intervention is minimal (ideally just starting the process)
Agents create comprehensive project plans and execute 100+ phases autonomously
Work continues until project completion or critical blocker
Related MCP server: Gemini Collaboration MCP Server
π Quick Start
Both AIs just run:
@ai-collab init {"agentName": "gemini", "autonomous": true} // For Gemini (CTO)
@ai-collab init {"agentName": "claude", "autonomous": true} // For Claude (Developer)That's it! The init command:
Loads existing project context and state
Creates or resumes a comprehensive project plan
Automatically detects and continues pending work
Shows critical tickets and blockers
Starts autonomous execution loops
π Recent Enhancements
Workflow Optimization (v2.0) π
Task Dependencies: Define
dependsOnrelationships between tasksBatch Task Creation: CTO can create multiple tasks in one command
Priority-Based Work: Tasks are automatically prioritized (high/medium/low)
Continuous Developer Mode: No waiting between tasks - automatic progression
Smart Task Status:
available,blocked,in_progress,in_review,completedDependency Resolution: Tasks automatically unblock when dependencies complete
Autonomous Loop System
120-second check intervals for more natural workflow pacing
500 iteration maximum for extended autonomous operation
Continuous work mode - agents keep working until project completion
Manual loop execution - requires human to run check commands (automation WIP)
Project Plan Management
Auto-generated 6-phase plans from PROJECT_REQUIREMENTS.md
Smart phase progression - automatically moves to next phase when complete
Duplicate task detection - prevents recreating completed features
Ad-hoc mission support - pause main plan for urgent tasks
Enhanced Validation
Ticket vs Task distinction - prevents confusion between bug reports and work items
Role-based instructions - clearer guidance for CTO vs Developer roles
Workflow enforcement - ensures proper task creation and submission flow
β οΈ Current Limitations
Automation Challenges
Manual loop execution required - AI agents can't schedule their own checks
PATH configuration needed - Claude/Gemini commands must be accessible
API quota limits - Gemini has daily request limits that may be exceeded
Addressed Issues β
Single task queuingβ Now supports batch task creationDeveloper idle timeβ Continuous work mode implementedNo task dependenciesβ Full dependency system addedRandom task orderβ Priority-based scheduling active
Remaining Challenges
Agents occasionally create duplicate tasks (improved but not eliminated)
Edit button functionality may need manual verification
Loop execution still requires human intervention
Workarounds Available
Automation scripts provided (
mcp-automator.js) but require setupManual loop execution instructions included
Simulation mode for tracking when automation fails
Features
Core Capabilities
Comprehensive Project Plans: 100+ phase autonomous execution capability
One-Command Startup: Just
initwith autonomous flagRole-Based System: CTO, Developer, PM, QA, Architect roles
Smart Task Management: Duplicate detection and phase progression
Ticketing System: Track bugs, enhancements, tech debt
Context Retention: Maintains state across sessions
Mission Management: High-level objectives with auto-decomposition
Code Review Workflow: Submit, review, and revision cycles
Question & Answer System: Asynchronous clarifications
Comprehensive Logging: Full audit trail
π Enhanced Workflow Features (v2.0)
Task Dependencies: Tasks can depend on other tasks with automatic blocking/unblocking
Priority-Based Scheduling: High/medium/low priority with smart task selection
Batch Task Creation: CTO can queue multiple tasks at once for efficiency
Continuous Work Mode: Developer automatically moves to next available task
Smart Status System:
available,blocked,in_progress,in_review,completedDependency Visualization: Clear indication of task dependencies and blockers
Installation
Clone this repository:
git clone https://github.com/yourusername/ai-collab-mcp.git
cd ai-collab-mcpInstall dependencies:
npm installMake the server executable:
chmod +x src/index.jsConfiguration
For Claude Code
Create a .mcp.json file in your project root:
{
"mcpServers": {
"ai-collab": {
"command": "node",
"args": [".mcp-server/src/index.js"],
"cwd": "/path/to/your/project"
}
}
}For Gemini
Configure in ~/.gemini/settings.json:
{
"mcpServers": {
"ai-collab": {
"command": "node",
"args": ["/path/to/ai-collab-mcp/src/index.js"]
}
}
}Note: Gemini may require explicit instructions to execute MCP commands.
Usage
π― Autonomous Mode (Recommended)
Start with autonomous flag for continuous operation:
# Terminal 1 - Claude (Developer)
@ai-collab init {"agentName": "claude", "autonomous": true}
# Terminal 2 - Gemini (CTO)
@ai-collab init {"agentName": "gemini", "autonomous": true}
# Terminal 3 - Manual Loop Execution (Required)
# Every 120 seconds, run:
@ai-collab get_loop_status {"agentName": "claude"}
@ai-collab get_loop_status {"agentName": "gemini"}Automation Helpers (Experimental)
For reduced manual intervention:
# Run automation script (requires setup)
cd /path/to/project
node mcp-automator.js auto
# Or simulation mode (shows what would happen)
node mcp-automator-v2.js autoSee AUTOMATION.md for setup details.
Traditional Commands
CTO Tools
send_directive- Create development tasks (now with dependencies & priority)send_batch_directives- Create multiple tasks at oncereview_work- Review submissionscreate_project_plan- Start comprehensive planupdate_plan_progress- Move to next phase
Developer Tools
get_all_tasks- View assigned work (sorted by priority)submit_work- Submit completed tasksask_question- Request clarification
π Enhanced Workflow Examples
Creating Tasks with Dependencies
// Single task with dependency
@ai-collab send_directive {
"taskId": "KAN-002",
"title": "Create database tables",
"specification": "Create user and project tables",
"priority": "high",
"dependsOn": ["KAN-001"] // Won't be available until KAN-001 is approved
}
// Batch creation with dependencies
@ai-collab send_batch_directives {
"tasks": [
{
"taskId": "KAN-003",
"title": "Setup database connection",
"specification": "Configure PostgreSQL connection",
"priority": "high"
},
{
"taskId": "KAN-004",
"title": "Create user model",
"specification": "Implement User model with validation",
"priority": "medium",
"dependsOn": ["KAN-003"]
},
{
"taskId": "KAN-005",
"title": "Create auth endpoints",
"specification": "Implement login/register endpoints",
"priority": "medium",
"dependsOn": ["KAN-004"]
}
]
}Continuous Work Mode (Developer)
When the developer runs get_loop_status, they will:
See prioritized available tasks
Automatically start on the highest priority task
After submitting, immediately move to next task
Continue until all available tasks are complete
No more waiting between tasks! The developer keeps working continuously.
Project Plan Workflow
Automatic Plan Creation: On first init, generates 6-phase plan from requirements
Phase Progression: Automatically advances when all phase tasks complete
Duplicate Prevention: Skips tasks that match completed work
Ad-hoc Missions: Can pause main plan for urgent work
Example phases:
Foundation & Basic Structure
Core Interactive Features
UI/UX Enhancement
Data Persistence
Advanced Features
Polish & Quality Assurance
Data Storage
data/
βββ tasks.json # Task tracking
βββ missions.json # Active missions
βββ project-state.json # Project configuration
βββ project-plans.json # Comprehensive plans (NEW)
βββ loop-states.json # Autonomous loop tracking (NEW)
βββ tickets/
βββ tickets.json # Bug/enhancement trackingTroubleshooting
Gemini Not Executing Commands
Prefix with: "Execute the following MCP command:"
Or: "Use the ai-collab tool to run:"
Duplicate Task Creation
System now detects similar task names
Manually clean duplicates from
data/tasks.jsonif needed
Loop Not Continuing
Ensure 120-second intervals between checks
Verify agent hasn't exceeded maxIterations (500)
Check API quotas haven't been exceeded
Contributing
This project needs help with:
True automation (removing manual loop execution)
Better Gemini CLI integration
Improved duplicate detection algorithms
Cross-platform automation scripts
Fork the repository
Create feature branch (
git checkout -b feature/improvement)Commit changes (
git commit -m 'Add improvement')Push branch (
git push origin feature/improvement)Open Pull Request
Roadmap
Native scheduling in MCP server
WebSocket/SSE for real-time updates
Improved role switching
Better error recovery
Multi-project support
Visual progress dashboard
License
MIT License - see LICENSE file for details.
Support
For issues, questions, or contributions, please open an issue on GitHub.
Remember: This is an experimental project pushing the boundaries of AI collaboration. Expect rough edges but exciting possibilities!
Available Tools
28 toolsanswer_questionB
Answer a previously asked question
Inputs: answer (required), questionId (required).
ask_questionC
Ask a question about a task
Inputs: taskId (required), question (required), context.
create_missionC
Create a new mission
Inputs: mission (required), agentName (required).
create_project_planB
Create a comprehensive project plan with multiple phases
Inputs: title (required), description, autoGenerate, requirementsPath.
create_ticketC
Create a new ticket
Inputs: data (required), type (required), agentName (required).
diagnose_tasksB
Diagnose task state discrepancies between project state and actual tasks
Inputs: no named parameters.
generate_context_summaryC
Generate a summary of current project context
Inputs: agentName.
generate_reportC
Generate a project status report
Inputs: type.
get_all_tasksB
Get all tasks in the system
Inputs: role.
get_loop_statusC
Get the current status of the autonomous loop
Inputs: agentName (required).
get_project_planB
Get the current active project plan
Inputs: no named parameters.
get_project_stateC
Get current project state
Inputs: component.
get_task_statusB
Get status of a specific task
Inputs: taskId (required).
initC
Initialize agent with role-based autonomous workflow
Inputs: agentName (required), mission, autonomous, checkInterval, +2 more.
list_ticketsB
List tickets with optional filtering
Inputs: type, status, priority.
pingA
Simple ping to test server connectivity
Inputs: no named parameters.
reset_task_dependenciesA
Reset task dependencies for tasks that are blocked by completed/missing tasks
Inputs: taskIds.
review_workC
Submit a review of submitted work
Inputs: status (required), taskId (required), feedback (required), actionItems.
send_batch_directivesB
Send multiple task directives at once. Use this to queue up multiple tasks for efficient workflow.
Inputs: tasks (required).
send_directiveB
Send a task directive to the development team. Can create single or batch tasks with dependencies.
Inputs: title (required), taskId (required), specification (required), priority, +4 more.
start_autonomous_loopC
Start an autonomous work loop that continuously checks for and processes work
Inputs: agentName (required), mode, checkInterval, maxIterations.
statusC
Get current system status
Inputs: agentName.
stop_autonomous_loopC
Stop the autonomous work loop
Inputs: agentName (required).
stop_autonomous_workC
Stop autonomous work mode
Inputs: agentName (required).
submit_workC
Submit completed work for review
Inputs: taskId (required), summary (required), files, testResults.
update_plan_progressC
Update project plan progress when phase is complete
Inputs: adjustments, phaseComplete.
update_project_stateC
Update the state of a project component
Inputs: state (required), component (required).
update_ticketC
Update an existing ticket
Inputs: updates (required), ticketId (required), agentName (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogβ¦
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.
Maintenance
Related MCP Connectors
Shared workspace where Claude, ChatGPT, Codex and Grok share files, tasks, decisions and handoffs.
One shared project for a team's coding agents: decisions, a task board and handoffs.
AI work orchestration for plans, tasks, teams, and coding-agent dispatch.
AI-native project management for tasks, docs, collaboration, and agents.
Related MCP Servers
- AlicenseBqualityDmaintenanceEnables collaboration between multiple AI models (GPT, Claude, Gemini) to work together on complex tasks, with intelligent task distribution and role-based expert assignment for code development, review, and optimization.1829 npm49MIT
- AlicenseBqualityDmaintenanceEnables Claude to collaborate with Gemini for code reviews, second opinions, and iterative software development. It facilitates multi-step workflows including PRD creation and code generation through an AI orchestration framework.275 npm1MIT
- FlicenseNot gradedqualityDmaintenanceCoordinates multiple Claude Code agents to work collaboratively on projects with role-based task management, shared state, and automated code review.11 npm2-
- AlicenseDqualityCmaintenanceEnables Claude Code as a team leader to delegate tasks to GPT and Gemini experts, supporting multi-LLM collaboration with tools for consultation, code review, design, and background execution.7645 npmMIT