orquestra-core
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ORQUESTRA_BIN | No | Overrides the path to the native `orquestra` binary used for the catalog and fleet tools (the binary at ~/.local/bin/orquestra is found automatically). | |
| ORQUESTRA_HOME | No | Relocates the whole ~/.orquestra tree (used by the test suite). |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| orquestra_list_skillsB | List every skill in the vault with token weight and whether a scope projects it. |
| orquestra_enable_skillA | Activate a skill in a scope; 'global' propagates the symlink to every harness. |
| orquestra_disable_skillC | Deactivate a skill; 'global' removes its symlink from every harness projection. |
| orquestra_list_mcpsA | List registered MCP servers with their global and per-harness state. |
| orquestra_toggle_mcpB | Enable or disable one MCP server, then redeploy the catalog to every harness. |
| orquestra_read_instructionsA | Return the master ~/.orquestra/AGENTS.md that every harness inherits. |
| orquestra_append_mission_ruleB | Append a mission directive to a section of the master AGENTS.md, with a backup. |
| orquestra_fleet_statusB | Report link state for every harness in the OrquestraAI fleet. |
| orquestra_create_skillC | Create a skill in the vault with frontmatter, markdown body and optional scripts. |
| orquestra_delete_skillA | Archive a skill: unlink it from every scope, then move its vault folder to backups. |
| orquestra_create_mcpC | Register a new MCP server in the catalog, then deploy it to every harness. |
| orquestra_delete_mcpB | Remove an MCP server from the catalog and from every harness config. |
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 12 tools
Each tool targets a distinct resource (skills, MCPs, instructions, fleet) with clear actions, so misselection is unlikely. Minor overlap where toggle_mcp and create/delete_mcp both affect MCP activation, and enable/disable vs create for skills could blur slightly.
Consistent orquestra_ prefix with a verb_noun convention (list_skills, enable_skill, create_mcp, delete_mcp). Only deviation is fleet_status, which uses noun_noun rather than an action verb.
12 tools is well-scoped for a skill/MCP/instruction management server, with balanced CRUD sets for two resource types plus reading and status operations, each earning its place.
Skills and MCPs both have full lifecycle coverage (create/list/enable/delete) and instructions can be read and appended. Minor gaps: no update/edit for skill content or mission rules, only create/delete and append.