{"repo":"jpicklyk/task-orchestrator","free":true,"listed":false,"github":"https://github.com/jpicklyk/task-orchestrator","clone":"git clone https://github.com/jpicklyk/task-orchestrator.git","description":"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.","language":"Kotlin","stars":200,"topics":["ai-coding-assistant","ai-development","ai-memory","ai-tools","claude","claude-code","claude-desktop","context-persistence","developer-tools","mcp"],"license":"MIT","category":"mcp-servers","readme_excerpt":"MCP Task Orchestrator Server-enforced workflow discipline for AI agents. Prompt-based frameworks hope the LLM follows instructions. This one blocks the call if it doesn't. --- The Problem Multi-agent workflows need infrastructure the model doesn't provide. When an orchestrator dispatches sub-agents across sessions, there's no built-in way to enforce what documentation must exist before work starts, track which agent made which change, or guarantee dependency ordering across a work breakdown. These are structural concerns — they belong in the server, not in prompts. A Different Approach Task Orchestrator is an MCP server — not a prompt layer. It provides 14 tools that give any MCP-compatible AI agent a persistent work item graph with server-enforced quality gates . The enforcement happens at the tool level: if a required design note isn't filled, advance item returns an error. If a dependency isn't satisfied, the transition is blocked. If actor authentication is enabled and an agent doesn't identify itself, the call is rejected before it reaches the server. The rules live in the server, not the conversation. What this means in practice: - An agent can't start implementation without filling the required specification note - A sub-agent can't advance a blocked task until its upstream dependency is complete - Every transition and note records who made the change (actor attribution) - Auditing mode blocks any write operation where the agent doesn't identify itself - A new session ","default_branch":null,"files":null,"tree":[],"storefront":"/r/jpicklyk","claimed":false,"request_supported":{"post":"https://gitbuyer.com/r/jpicklyk/task-orchestrator/request-supported","requests":0},"note":"indexed from public GitHub; nothing is for sale on this page. Clone it from GitHub. Paid listings live at /search."}