A
licenseA
qualityD
maintenanceA task management server that helps AI assistants break down user requests into manageable tasks and track their completion with user approval steps.
24
83 npm
30
MIT
MCP Orchestrator Server
by mokafari
The MCP Orchestrator Server is a task management system that enables coordination and execution of tasks across multiple AI instances with the following capabilities:
Create Tasks: Define new tasks with unique IDs, descriptions, and optional dependencies
Update Tasks: Modify pending tasks' descriptions or dependencies
Delete Tasks: Remove tasks that have no dependents
Get Next Task: Retrieve the next available task for an instance to work on
Complete Tasks: Mark tasks as completed with results
Track Status: Monitor all tasks' statuses and get detailed information about specific tasks
Manage Dependencies: Enforce proper task execution order and detect circular dependencies
Coordinate: Orchestrate work across multiple AI instances
Store Persistently: Maintain reliable task information storage
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., "@MCP Orchestrator Server create a task to update the database schema with dependencies on backup and testing"
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 Orchestrator Server
The MCP Orchestrator Server provides task management and coordination capabilities across MCP enabled LLM instances like Claude Desktop or Cline. In simpler terms it allows for AI agents to create, share and execute tasks across instances
Features
Version 1.1.0
Task Updates: Modify pending tasks
Safe Deletion: Delete tasks with dependency checks
Cycle Detection: Prevent dependency cycles
Tool Listing: Comprehensive tool documentation
Enhanced State Management: Improved task state transitions
Core Features
Task creation with dependencies
Multi-instance coordination
Persistent task storage
Dependency enforcement
Task status tracking
Related MCP server: task-orchestrator-mcp
Installation
Installing via Smithery
To install Orchestrator Server for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install orchestrator-server --client claudeManual Installation
npm install
npm run buildUsage
Create a Task
await create_task({
id: 'setup',
description: 'Initial setup'
});Get Next Task
const task = await get_next_task({
instance_id: 'worker-1'
});Complete Task
await complete_task({
task_id: 'setup',
instance_id: 'worker-1',
result: 'System initialized'
});Documentation
Roadmap
Version 1.2.0
Task priorities
Timeouts
Instance management
Version 1.3.0
Task groups
Analytics
Dashboard
License
Available Tools
7 toolscomplete_taskC
Mark a task as completed
Inputs: task_id (required), instance_id (required), result (required).
create_taskC
Create a new task
Inputs: id (required), description (required), dependencies.
delete_taskA
Delete a task if it has no dependents
Inputs: task_id (required).
get_next_taskC
Get the next available task
Inputs: instance_id (required).
get_task_detailsC
Get details of a specific task
Inputs: task_id (required).
get_task_statusC
Get status of all tasks
Inputs: no named parameters.
update_taskC
Update an existing pending task
Inputs: task_id (required), description, dependencies.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
B3.4/5.0
Scored across 7 tools
Disambiguation5/5
Every tool has a clearly distinct purpose with no ambiguity. The tools target specific actions like creating, updating, deleting, completing, and retrieving tasks, with clear boundaries between them. For example, get_task_details and get_task_status serve different retrieval functions, and delete_task has a specific condition that distinguishes it.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern throughout, such as create_task, update_task, and get_task_details. There are no deviations in naming conventions, making the set predictable and easy to understand for an agent.
Tool Count5/5
With 7 tools, the count is well-scoped for a task management server, covering essential CRUD operations and status checks. Each tool earns its place by addressing a specific aspect of task handling, without being overly sparse or bloated.
Completeness5/5
The tool surface provides complete CRUD/lifecycle coverage for task management, including creation, retrieval, updating, deletion, completion, and status monitoring. There are no obvious gaps, and agents can perform all necessary operations without dead ends.
Maintenance
ActivityInactive
ResponsivenessOutdated data
Related MCP Connectors
Zoom Tasks server for creating, updating, assigning, and synchronizing task workflows.
Task manager for AI agents. Orchestrate agents to achieve large goals in unified control plane.
Hosted MCP server for task-first delegation to remote workstations and workers.
Shared task layer for AI agents: tasks, handoffs and decisions that persist across tools.
Related MCP Servers
- AlicenseAqualityDmaintenanceAn MCP server for task orchestration.726 npm2MIT
- AlicenseNot gradedqualityDmaintenanceA robust task scheduler server for scheduling and managing various types of automated tasks including shell commands, API calls, AI tasks, and reminders.59MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to manage hierarchical tasks, track progress, handle dependencies, and coordinate work through an MCP server.45 npm15GPL 3.0