MCP Task Orchestrator

About MCP Task Orchestrator

Use MCP Task Orchestrator with your agent

claude mcp add mcp-task-orchestrator -- docker run -i --rm ghcr.io/jpicklyk/task-orchestrator:latest

{
  "mcpServers": {
    "mcp-task-orchestrator": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/jpicklyk/task-orchestrator:latest"
      ]
    }
  }
}

Frequently asked questions

What is MCP Task Orchestrator?

MCP Task Orchestrator is an MCP (Model Context Protocol) server by jpicklyk in the Autonomous Agents category. Server-enforced workflow discipline for AI agents: work items, dependency graphs, quality gates

How do I connect MCP Task Orchestrator to Claude, Cursor, or another MCP client?

Install MCP Task Orchestrator from its oci package (ghcr.io/jpicklyk/task-orchestrator:latest) and register it under "mcpServers" in your client's MCP configuration — for example claude_desktop_config.json or Cursor's mcp.json — then restart the client.

Is MCP Task Orchestrator open source?

Yes — the source code is public at github.com/jpicklyk/task-orchestrator, with 193 GitHub stars.

Can AI agents pay to use MCP Task Orchestrator?

Not yet through Loomal — MCP Task Orchestrator is listed as a free directory entry. If its maintainer verifies ownership, they can set per-call USDC pricing that agents pay over x402, with settlement on Base.