task-orchestrator

概述

Task Orchestrator 是一个MCP服务器，为多代理AI系统实施服务器强制的工作流程纪律。它提供了一个持久的工作项图，其中包含质量门，只有满足要求后才能推进工作。与依赖模型遵循指令的提示框架不同，此服务器在依赖关系未满足或所需文档缺失时阻止API调用。它具有用于问责制的参与者属性、依赖图验证和通过SQLite数据库后端的会话连续性。

试试问 AI

装完之后，这里有 7 个你可以让 AI 做的事：

• manage_items

  Create, update, or delete work items in the task hierarchy

  试试:Create a new work item for implementing user authentication试试:Update the title of the work item with ref 'auth'试试:Delete the completed work item 'a3f2'
• query_items

  Search for and retrieve work items based on various criteria

  试试:Show me all work items in the 'work' phase试试:Find all items that are currently blocked试试:Get all work items created after January 1st, 2025
• create_work_tree

  Create a hierarchical tree of work items with dependencies

  试试:Create a work tree for the User Authentication feature with child items for schema, API, and tests试试:Build a multi-level breakdown of the payment processing workflow试试:Create a parallel task structure for testing and implementation
• complete_tree

  Mark a work item and all its children as completed

  试试:Complete the entire 'User Authentication' work tree试试:Mark the parent project and all subtasks as finished试试:Complete all items in the current sprint
• manage_notes

  Create, update, or delete phase-specific documentation attached to work items

  试试:Add requirements notes to the login API task试试:Update the implementation notes with what was actually built试试:Delete outdated requirements from the stalled feature task
• query_notes

  Retrieve notes from work items, with optional filtering by role or key

  试试:Show me all the work notes for the 'api' task试试:Get the review notes for the security assessment试试:List all requirements notes in the project
• manage_dependencies

  Create or remove dependency relationships between work items

  试试:Create a dependency that the tests task must wait for the API implementation试试:Remove the dependency between the frontend and backend tasks试试:Set up a fan-in dependency where multiple tasks must complete before the next phase
• query_dependencies

  Retrieve dependency relationships between work items

  试试:Show me what tasks are blocking the payment integration试试:Get all dependencies for the 'api' task试试:Find which tasks depend on the database schema completion
• advance_item

  Move a work item to the next phase in its lifecycle, enforcing quality gates

  试试:Advance the user authentication task from 'queue' to 'work' phase试试:Move the API implementation to 'review' phase试试:Transition the completed task to 'terminal' status
• get_next_status

  Determine the next possible status for a work item based on current state and dependencies

  试试:What's the next possible status for the stalled authentication task?试试:Can the API task advance to work now?试试:Show me available transitions for the blocked feature task
• get_context

  Retrieve the current state of the work item graph with recent changes and actor attribution

  试试:Get all context since yesterday's session试试:Show me the current state of the entire project试试:Get context for the 'api' task with all ancestors
• get_next_item

  Find the next available work item to work on based on dependencies and availability

  试试:Find the next available task for me to work on试试:Get a ready task for the implementation phase试试:Show me items that can advance from queue to work

可对比工具

安装

# 拉取最新镜像
docker pull ghcr.io/jpicklyk/task-orchestrator:latest

# 在Claude Code中注册
claude mcp add-json mcp-task-orchestrator '{
  "command": "docker",
  "args": [
    "run", "--rm", "-i",
    "-v", "mcp-task-data:/app/data",
    "ghcr.io/jpicklyk/task-orchestrator:latest"
  ]
}'

# 对于MCP客户端：添加到.mcp.json
{
  "mcpServers": {
    "mcp-task-orchestrator": {
      "command": "docker",
      "args": [
        "run", "--rm", "-i",
        "-v", "mcp-task-data:/app/data",
        "ghcr.io/jpicklyk/task-orchestrator:latest"
      ]
    }
  }
}

FAQ

这与基于提示的工作流框架有何不同？

与依赖模型遵循指令的提示框架不同，Task Orchestrator在服务器级别强制执行规则，当要求未满足时阻止API调用。规则存在于服务器中，而不是提示中。

我可以将它与任何AI客户端一起使用吗？

是的，它适用于任何兼容MCP的客户端。提供的Claude Code插件添加了额外的自动化功能，但核心功能不需要它。

这是否需要特定的开发方法论？

不需要，Task Orchestrator强制执行工作流程结构而不施加方法论。您可以通过YAML模式定义工作流程规则，而不规定开发过程。

task-orchestrator 对比