Packaged MCP / Agent Control toggleFinished installers / direct links
Translator for Claude and Codex

Subtitle videos with the AI you already pay for.

Connect the Translator desktop app to Claude or Codex. Your agent downloads the video, pulls its captions, translates them itself and exports SRT or a subtitled video. For videos that have captions, that costs no Stage5 credits: the translating is done by the subscription you already have.

Route the job before choosing the tool.

Start with the narrowest workflow. These pages describe the current product; they do not imply a remote agent service or live pay-per-call endpoint.

Set up once

Three steps, about two minutes.

Everything runs on your computer: your agent talks to the Translator app through a local MCP connection. There is no remote Translator server to sign up for.

1. Install Translator and keep it open
Download the app for macOS or Windows below. Your agent works through the running app, so leave it open while you use it.
2. Turn on Agent Control
Settings → Agent Control → Allow agent control, and add a folder the agent may save files to. It takes effect immediately. The same panel shows the exact launcher path for your computer.
3. Add Translator to your agent
Use the command for your client below, then restart it so the Translator tools appear.
Claude Code
Run once in a terminal:
claude mcp add translator -- /Applications/Translator.app/Contents/Resources/translator-mcp
Codex
Run once in a terminal:
codex mcp add translator -- /Applications/Translator.app/Contents/Resources/translator-mcp
Claude Desktop
Add to claude_desktop_config.json (Settings → Developer → Edit Config), then restart Claude:
{
  "mcpServers": {
    "translator": { "command": "/Applications/Translator.app/Contents/Resources/translator-mcp" }
  }
}

These paths are for macOS. On Windows, use the path shown in Settings → Agent Control (it ends in resources\translator-mcp.cmd). Agent Control is off until you turn it on, and your agent only writes to the folders you allow.

First prompt to try

Use the Translator tools to subtitle https://www.youtube.com/watch?v=… in Spanish. Use the video's existing captions, translate them yourself with translation_provider agent, and export an SRT. Don't use paid transcription.

What your agent does

The whole job, in one conversation.

The tools have named inputs and structured results, so your agent works the app directly instead of guessing at the screen.

01

Bring in the video and its captions

Download from a URL, check which caption tracks the video has (creator, auto-generated or YouTube's translated tracks) and import the one to start from.

02

Translate with your own subscription

Your agent reads the subtitles in batches, translates them itself and writes them back by cue ID. Translator checks the result and never falls back to paid translation on this path.

03

Edit, check and export

Fix lines and timing, preview, then export source, translated or dual-language SRT, or burn the subtitles into the video.

04

Paid steps only when you choose

Transcribing audio for videos without captions, and dubbing, use Stage5 credits or your own API key. The agent has to request those explicitly; the free path never spends credits.

Deliberate boundaries

The user stays in control.

Translator gives the agent useful controls without handing it payment, stored secrets or your settings.

  1. 01File-writing and network actions remain visible to the MCP host and should keep its normal approval controls.
  2. 02The agent never sees stored API keys, can’t change your settings and can’t buy anything.
  3. 03Translating with your agent is free. Only transcribing audio (for videos without captions) and dubbing use Stage5 credits or your own API key, and only when the agent asks for them.
Direct artifacts

No button hunting required.

These are stable latest-version URLs. A person or agent can choose the platform explicitly and follow the link directly.

macOS / Homebrew
brew install --cask mikey1384/translator/stage5-translator
Publisher-maintained tap ↗