Schema | Orchestrator Python MCP Server

Orchestrator Python MCP Server

Describes the environment variables required to run the server.

Name	Required	Description	Default
No arguments

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.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{ "listChanged": false }
`prompts`	{ "listChanged": false }
`resources`	{ "subscribe": false, "listChanged": false }
`experimental`	{}

Functions exposed to the LLM to take actions

Name	Description
orchestrate_initB	Initialize a new orchestration session with HMAC anti-tamper security.
orchestrate_statusB	Query current session status and active phase.
orchestrate_approveC	Grant human approval for the current phase deliverable.
orchestrate_verifyB	Run machine verification on current phase deliverables and advance phase on success.
orchestrate_archiveC	Archive current orchestration deliverables and release session lock.
orchestrate_get_dag_batchesB	Compute topological execution batches from plan.md tasks.
orchestrate_get_agentsA	List all specialized orchestrator agent personas. Each `name` is a registered OpenCode subagent ID, spawnable by name via the `subagent` tool even if hidden from the advertised subagent catalog.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/eustin/mcp-server-orchestrate'

If you have feedback or need assistance with the MCP directory API, please join our Discord server