Reedapt MCP server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REEDAPT_API_KEY | Yes | Your Reedapt API key, created under Developers in Reedapt. Test keys are free and dub the first 60 seconds of a video with a watermark; live keys come with paid plans and use plan minutes. |
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 |
|---|---|
| list_languagesB | The language codes Reedapt can dub into right now, for this API key's plan. |
| get_usageA | The account's plan, whether the key is live or test, and the minutes left. Check this before a long dub: a live dub uses one minute of the plan per minute of video, per language. Test keys are free and dub only the first seconds with a watermark. |
| dub_mediaA | Uploads a local file (an absolute path) or a public https link, and starts one dub per target language. Returns as soon as the dubs have started; dubbing takes minutes. Then call wait_for_dub or get_dub. Languages the plan can't dub into come back under |
| get_dubC | A dub's status (queued, processing, completed or failed), its stage and progress, and the error if it failed. |
| wait_for_dubA | Waits until a dub completes or fails, up to timeout_seconds (at most 240). If it is still running, it returns the latest status: call it again to keep waiting. |
| list_dubsC | The account's API dubs, newest first. |
| get_dub_filesA | Download links for a completed dub: the dubbed video or audio, a WAV of the dubbed audio, and the separate voice and background tracks. Links expire at |
| get_transcriptA | A completed dub's lines in time order: speaker, original words and the dubbed words, with times in milliseconds. Returns 200 lines at a time; use offset for more. |
| get_subtitlesA | A completed dub's subtitles as SRT or WebVTT text, in the dub's language or the original's. |
| cancel_dubA | Stops a dub that hasn't finished. Its reserved minutes are returned. This can't be undone. |
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 10 tools
Each tool has a clearly distinct role across the dubbing lifecycle: usage, starting, polling/waiting, listing, retrieving files/transcripts/subtitles, canceling, and languages. The closest pair, get_dub and wait_for_dub, is well differentiated by status-check versus blocking-wait behavior.
All tool names use consistent snake_case with predictable verb_noun structure (get_usage, dub_media, get_dub, list_dubs, cancel_dub). Even the less common wait_for_dub and dub_media fit the overall convention.
Ten tools is well-scoped for a media dubbing API, covering the full workflow without obvious bloat. Each tool corresponds to a meaningful operation rather than duplicating functionality.
The surface covers the full dubbing lifecycle: checking plan/usage, starting dubs, monitoring progress, waiting, listing dubs, downloading outputs, retrieving transcripts/subtitles, canceling, and listing available languages. No obvious operational gaps are apparent for the stated domain.