Server-enforced workflow discipline for AI agents. An MCP server providing persistent work items, dependency graphs,...
Copy the install, test the workflow, then decide if it earns a permanent slot.
Fresh repo activity plus visible builder pull. This is the kind of tool people test before it turns obvious.
Copy the install, test the workflow, then decide if it earns a permanent slot.
You can test this quickly and remove it cleanly if it misses.
GitHub health 100/100. no security policy. Fresh enough repo health and manageable issue load keep the risk controlled.
AI Agent
Claude Code
Model
Claude
Build Time
Instant
Fastest way to find out if task-orchestrator belongs in your setup.
Copy the install command, run a real test, and back it out cleanly if it slows you down.
claude mcp add task-orchestrator -- npx task-orchestratorRun this first. You will know quickly if the workflow earns a permanent slot.
claude mcp remove task-orchestratorNo messy cleanup loop. If it misses, remove it and keep moving.
Install Location
~/ └─ .claude.json └─ mcp_servers/ └─ task-orchestrator ← registers here
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.