MCP Orchestrator Server
MCP オーケストレータ サーバー
MCP Orchestrator Serverは、Claude DesktopやClineなどのMCP対応LLMインスタンス間でタスク管理と調整機能を提供します。簡単に言えば、AIエージェントがインスタンス間でタスクを作成、共有、実行できるようにします。
特徴
バージョン1.1.0
タスクの更新: 保留中のタスクを変更する
安全な削除: 依存関係をチェックしてタスクを削除する
サイクル検出: 依存関係のサイクルを防ぐ
ツールリスト: 包括的なツールドキュメント
強化された状態管理: タスクの状態遷移の改善
コア機能
依存関係のあるタスクの作成
複数インスタンスの調整
永続的なタスクストレージ
依存関係の強制
タスクステータスの追跡
Related MCP server: task-orchestrator-mcp
インストール
Smithery経由でインストール
Smithery経由で Claude Desktop 用の Orchestrator Server を自動的にインストールするには:
npx -y @smithery/cli install orchestrator-server --client claude手動インストール
npm install
npm run build使用法
タスクを作成する
await create_task({
id: 'setup',
description: 'Initial setup'
});次のタスクを取得
const task = await get_next_task({
instance_id: 'worker-1'
});タスクを完了する
await complete_task({
task_id: 'setup',
instance_id: 'worker-1',
result: 'System initialized'
});ドキュメント
ロードマップ
バージョン1.2.0
タスクの優先順位
タイムアウト
インスタンス管理
バージョン1.3.0
タスクグループ
分析
ダッシュボード
ライセンス
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
Scored across 7 tools
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.
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.
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.
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
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
- AlicenseAqualityDmaintenanceA task management server that helps AI assistants break down user requests into manageable tasks and track their completion with user approval steps.2483 npm30MIT
- 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