A
licenseNot graded
qualityA
maintenanceEnables AI coding providers to run structured multi-agent workflows with specs, tracked tasks, handoffs, health gates, and audited repair mode.
29 npm
MIT
Orchestrator Python MCP Server
by eustin
Related Servers
Alternatives to Orchestrator Python MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI coding providers to run structured multi-agent workflows with tracked tasks, document specifications, handoffs, health gates, and server-owned evidence across providers like Claude Code, Codex CLI, Cursor, Grok Build, and OpenCode.29 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI coding providers to run structured multi-agent workflows with specifications, tracked tasks, handoffs, approvals, and health-gated completion across supported coding environments.29 npmMIT
- AlicenseAqualityBmaintenanceEnables coding agents to run persistent, budgeted work sessions with dependency graphs, human decision queues, required validation, and clean handoffs for autonomous or human-in-the-loop execution.16MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI coding providers to run structured multi-agent workflows with shared use-case and spec documents, tracked tasks, handoffs, health checks, and review/repair gates.29 npmMIT
- FlicenseBqualityCmaintenanceEnables autonomous software development by managing requirements, architecture, task dependency DAGs, isolated worker workspaces, execution, contract and integration verification, and checkpoints. It provides observable evidence gates so AI workers can build and verify software against reproducible contracts.28-
TDQS
B3.4/5.0
Scored across 7 tools
Disambiguation5/5
Each tool targets a distinct operation: session init, status, human approval, machine verification, archiving, DAG batch computation, and agent listing. There is no meaningful overlap, and the approve versus verify distinction is clear because one is human-driven and the other is machine-driven.
Naming Consistency4/5
All tools share the orchestrate_ prefix and lowercase snake_case, which makes the set easy to predict. However, status reads as a noun rather than an action verb, and the get_* retrieval tools stand slightly apart from the other lifecycle verbs.
Tool Count5/5
Seven tools is well-scoped for an orchestration lifecycle server, covering session creation, status, approval, verification, archival, DAG computation, and agent discovery without redundancy. The count feels appropriate for the domain.
Completeness3/5
The core lifecycle is present, but the human-in-the-loop workflow lacks explicit reject, cancel, or rollback paths, and verification only advances on success. Additionally, the DAG batch and agent listing tools are auxiliary and do not include an execution tool, leaving a notable gap in the orchestration loop.
Maintenance
ActivityStale
ResponsivenessNo issues