Orchestrate Codex
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| orchestrate_list_recipesA | List built-in supervised orchestration recipes. |
| orchestrate_explain_recipeC | Explain a recipe: stages, doc_class, context policy, default leaf bindings. |
| orchestrate_context_policyB | Return context policy for a doc_class (durable|change|transform|direct). |
| orchestrate_plan_recipeC | Build a static plan (steps + suggested tools). Prefer start_run for stateful execution. |
| orchestrate_start_runC | Start a supervised run. Auto-executes local gather stages. Returns next_action (call_tool with leaf name+args, or done). Does not call other MCP servers — Codex must invoke the leaf tool. |
| orchestrate_continue_recipeA | Advance a run after a leaf tool result. Pass run_id and/or full state. On leaf failure set success=false to try fallback_tools (Claude→Grok→AG). |
| orchestrate_get_runA | Fetch run state by run_id (same process only). |
| orchestrate_fallback_chainsC | Show default capability→fallback leaf tool chains. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
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.
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.
With 8 tools, the set is well-scoped for a recipe orchestration server, covering planning, execution, state retrieval, and explanation without being overwhelming.
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.