Skip to main content
Glama

MCP 协调器服务器

版本 铁匠徽章

MCP Orchestrator 服务器提供跨 MCP 支持的 LLM 实例(例如 Claude Desktop 或 Cline)的任务管理和协调功能。简单来说,它允许 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 tools
complete_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
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers