orchestrator-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ORCHESTRATOR_CONFIG | No | Path to the configuration YAML file. Defaults to 'config.yaml' in the working directory. It is recommended to set an absolute path. |
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| orchestrator_setupA | Say how to finish setting up orchestrator: this server started without a config, so none of its other tools exist yet. |
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 1 tool
With only one tool in the set, there is no possibility of confusion or overlapping purposes. The tool's purpose is clearly stated as setup only.
The single tool name 'orchestrator_setup' uses snake_case consistently. With no other names to compare against, there is no inconsistency.
An orchestrator server should have multiple tools for orchestration tasks, but this set contains only a single trivial setup stub. This is an extreme mismatch for the stated purpose.
The server has no actual orchestration operations, CRUD capabilities, or lifecycle coverage. The tool itself admits that no other tools exist yet, making the surface severely incomplete.