orchard-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ORCHARD_API_KEY | Yes | Your Orchard API key (from orchardrun.com) | |
| ORCHARD_API_URL | No | Base URL for the Orchard API (defaults to https://api.orchardrun.com) | https://api.orchardrun.com |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| transcribe_fileA | Transcribe a local audio file (wav, mp3, m4a, ogg...) with Orchard. Handles Spanish and Portuguese real-world audio (calls, meetings, field recordings) especially well; language auto-detected when omitted. Set diarize=true to get speaker-labeled turns. |
| transcribe_urlA | Transcribe audio from a URL (YouTube link or a direct audio file URL) with Orchard. Language auto-detected when omitted. |
| get_transcriptionA | Fetch the status or final transcript of a previously started Orchard transcription job (use the job_id returned by the transcribe tools). Optionally return it formatted as srt, vtt, md or plain text. |
| get_usageA | Show the Orchard account's usage summary and remaining balance. |
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 4 tools
Each tool has a clear, non-overlapping purpose: transcribe_file and transcribe_url cover different input sources, get_transcription retrieves results, and get_usage handles account info. No ambiguity exists.
All tool names follow a consistent verb_noun pattern (transcribe_file, transcribe_url, get_transcription, get_usage), with clear and predictable naming.
Four tools is well-scoped for a focused transcription service—covering submission, retrieval, and usage—without unnecessary bloat or missing essentials.
The core lifecycle of transcription (start from file or URL, fetch result) and account usage is covered. A minor gap is lack of cancellation or listing jobs, but the surface is sufficiently complete for typical use.