Skip to main content
Glama
README.md
# Orchard MCP Server

Speech-to-text for real-world Spanish and Portuguese, as MCP tools.

[Orchard](https://orchardrun.com) is a transcription and speaker-diarization
API built for LATAM audio: call centers, phone recordings, meetings, field
audio. This server lets any MCP-capable assistant (Claude Desktop, Claude
Code, Cursor, custom agents) transcribe audio conversationally.

## Tools

| tool | what it does |
|---|---|
| `transcribe_file` | Transcribe a local audio file. Optional speaker diarization (`diarize: true`), speaker-count hints, domain prompt. Language auto-detected. |
| `transcribe_url` | Transcribe from a YouTube link or direct audio URL. |
| `get_transcription` | Fetch a job's transcript, optionally as `srt`, `vtt`, `md` or plain text. |
| `get_usage` | Account usage summary and remaining balance. |

Long audio is handled automatically: the tool enqueues the job, polls until
it finishes and returns the final transcript in one call.

## Setup

1. Get an API key at [orchardrun.com](https://orchardrun.com) (free tier, no
   card required).
2. Add the server to your MCP client config:

```json
{
  "mcpServers": {
    "orchard": {
      "command": "npx",
      "args": ["-y", "orchard-mcp"],
      "env": { "ORCHARD_API_KEY": "ork_..." }
    }
  }
}
```

For Claude Code:

```bash
claude mcp add orchard -e ORCHARD_API_KEY=ork_... -- npx -y orchard-mcp
```

## Example prompts

- "Transcribe `/Users/me/call.mp3` and tell me who said what."
- "Transcribe this YouTube interview and summarize each speaker's position."
- "Transcribe `meeting.wav` with diarization for 3 speakers and give me the
  action items per person."
- "Get job `abc123` as SRT subtitles."

## Notes

- Language is auto-detected when omitted; pass `language: "es"` (or `pt`,
  `en`, ...) to pin it.
- `prompt` biases the transcriber toward names, brands or domain jargon.
- Set `ORCHARD_API_URL` to point at a different environment (defaults to
  `https://api.orchardrun.com`).

MIT © Orchard

TDQS

A4.2/5.0

Scored across 4 tools

Disambiguation5/5

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.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (transcribe_file, transcribe_url, get_transcription, get_usage), with clear and predictable naming.

Tool Count5/5

Four tools is well-scoped for a focused transcription service—covering submission, retrieval, and usage—without unnecessary bloat or missing essentials.

Completeness4/5

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.

Maintenance

ActivityMaintained
ResponsivenessNo issues