task-orchestrator
task-orchestrator is an MCP server. Its repository has 209 GitHub stars and is licensed under MIT; we last read it on 2026-10-22.
Manages workflows for AI agents by providing persistent work items, dependency graphs, and quality gates. Requires schemas defining agent outputs, blocking calls if outputs are not met. Compatible with any MCP-compatible client.
Install
MCP servers are packaged differently from each other -- some run via npx, some as a Docker image, some as a plain script you clone and run. task-orchestrator’s own README did not state one plainly enough for this page to quote it rather than guess, so it will not guess. The repository below states it.
What it reaches, and what it needs
Maintenance
Server-enforced workflow discipline for AI agents. An MCP server providing persistent work items, dependency graphs, quality gates, and actor attribution. Schemas define what agents must produce — the server blocks the call if they don't. Works with any MCP-compatible client.
Common questions about task-orchestrator
- What does task-orchestrator do?
- Manages workflows for AI agents by providing persistent work items, dependency graphs, and quality gates. Requires schemas defining agent outputs, blocking calls if outputs are not met. Compatible with any MCP-compatible client.
- How do I install task-orchestrator?
- Its README did not state an install command plainly enough for us to quote one, so we do not guess. The repository has the instructions: https://github.com/jpicklyk/task-orchestrator
- Is task-orchestrator official and is it maintained?
- We found nothing naming it as a vendor’s official server. Its repository has 209 GitHub stars and its state in our directory is listed. Its last commit we recorded was on 2026-10-17.
- What licence does task-orchestrator use?
- The repository declares the MIT licence.