MCP Task Orchestrator · Field guidePlate 1 of 10
Task Orchestrator is an MCP server that gives AI coding agents a persistent work item graph with quality gates. Prompt-based frameworks hope the model follows instructions. This server blocks the call when it doesn't.
A new session with no memory of yesterday picks up an item and runs into the gate. Write calls take an ops list, and each element answers in data.results[].
select="history", lists recent transitions.requirements note before work starts. The error names it in detail.missing.Everything is a WorkItem. Items nest to any depth and connect with typed dependency edges.
items_write (create_tree, complete_tree) · items_read
Schemas declare which notes must exist at each phase. Transitions fail until they do.
advance · items_read (context) · notes_write
A blocked item cannot start until its blocker reaches the agreed phase. Finishing a blocker reports what it unblocked.
deps_write · items_read (blocked)
Transitions and notes record who made them: the principal of the credential the caller presented, or the single local principal for stdio and unauthenticated modes. A caller cannot name itself.
principal: api:<id> | local
A caller can hold a time-limited claim on an item. While the claim is live, a transition from any other caller is refused. This fence is always on.
advance (claim, release, heartbeat)
A run groups items for a coordinator and hands each seat its own token. A seat that needs a ruling raises a decision, and a human or director answers it.
runs_read · runs_write
Longer text lives in documents anchored to a project root and attached to items, apart from the short notes the gates read.
docs_read · docs_write
Schemas, traits and status labels are stored per project in the database with a version history. Push, validate, roll back or reset them without a restart.
config
A fresh session reads active, blocked and stalled items in one response instead of replaying a conversation.
items_read (context, next)
Notes are keyed by phase. Agents read only the note they need, or search items and notes by keyword.
notes_read · items_read (search)
The server owns these guardrails and nothing else. It has no opinion on how agents plan or write code. Claim fencing, note ownership and the required item type are always on. Note schemas, traits, lifecycle modes and run seats are the layers you opt into through config. The tools come in three profiles: orchestration (the default), knowledge and director.
Each tier builds on the one before. Note schemas (tier 3) can be added at any point.