task-orchestrator and conductor-tasks
About task-orchestrator
jpicklyk/task-orchestrator
A light touch MCP task orchestration server for AI agents. Persistent work tracking and context storage across sessions and agents. Defines planning floors through composable notes with optional gating transitions. Coordinates multi-agent execution without prescribing how agents do their work.
Implements server-enforced workflow gates using YAML-defined note schemas that block phase transitions until required documentation is complete, ensuring deterministic progression independent of agent discipline. Built on MCP's stdio transport with persistent SQLite storage and optional per-project isolation, it surfaces phase-specific structured instructions at exactly the right moment while enabling sub-agent delegation through Claude Code integration. The dependency graph uses typed BLOCKS edges with pattern shortcuts (linear chains, fan-out, fan-in) and BFS traversal to enforce ordering across hierarchical work items up to 4 levels deep.
About conductor-tasks
hridaya423/conductor-tasks
A task management system designed for AI development
Parses requirements into structured tasks and generates implementation plans using multi-LLM routing (OpenAI, Anthropic, Groq, Mistral, Google, Perplexity, etc.), then visualizes progress via Kanban boards and dependency trees. Integrates via MCP protocol for editor-embedded AI assistance or standalone CLI, with features like task expansion, research capabilities, and template-based workflows throughout the development lifecycle.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work