A
licenseA
qualityA
maintenanceAn MCP bridge that enables AI coding agents to delegate implementation tasks to the OpenAI Codex CLI, allowing the orchestrator to plan and review while Codex executes.
3
358 npm
1
MIT
Orchestrate Codex
by Meapri
Related Servers
Alternatives to Orchestrate Codex
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceA local MCP control plane for Codex that manages task queues, dynamic roles, and side-panel team collaboration with persistence, dependency gating, and structured reporting.MIT
- AlicenseBqualityBmaintenanceA universal Worker control plane exposed over MCP that lets a host configure OpenAI-compatible providers and API keys, discover model capabilities, and run, monitor, steer, or cancel Codex worker threads. It ships an app-only control panel so humans manage secrets and worker permissions while models call worker lifecycle tools.21MIT
- AlicenseNot gradedqualityFmaintenanceAn MCP control plane for Codex native sessions, translating eight explicit operations with strict security boundaries for authenticated access through OpenAI Secure MCP Tunnel.MIT
- AlicenseNot gradedqualityAmaintenanceMCP server for stage-aware, evidence-backed model routing in Codex. It assigns planning, design, development, review, and verification stages to explicit roles while preserving root-agent accountability and live model evidence.MIT
- AlicenseAqualityAmaintenanceLocal-first multi-agent delegation and approval control for Codex via MCP, with persistent task DAG, isolated worktrees, and a web console.141MIT
TDQS
B3.2/5.0
Scored across 8 tools
Disambiguation5/5
Each tool targets a distinct aspect of recipe orchestration: context policy, continuing runs, explaining recipes, fallback chains, fetching run state, listing recipes, planning, and starting runs. No overlaps are apparent.
Naming Consistency4/5
All tools follow the 'orchestrate_' prefix with clear verb_noun or noun phrases, but some like 'orchestrate_fallback_chains' and 'orchestrate_context_policy' use noun-noun patterns while others use verb-noun. Still mostly consistent and predictable.
Tool Count5/5
With 8 tools, the set is well-scoped for a recipe orchestration server, covering planning, execution, state retrieval, and explanation without being overwhelming.
Completeness4/5
The surface covers core lifecycle operations (plan, start, continue, get run, explain, list) and supporting features (fallback chains, context policy). A minor gap is the absence of a cancellation or stop-run tool, but it's not critical for the stated purpose.
Maintenance
ActivityInactive
ResponsivenessNo issues