AI video dubbing via OrcaRouter (model orca/dub): upload a video or URL, poll, download the MP4.
Connect Orcadub to Claude, Cursor or any other MCP client and it stops being a tab you switch to. AI video dubbing via OrcaRouter (model orca/dub): upload a video or URL, poll, download the MP4. The orcadub mcp server is what makes that connection.
Give any MCP-capable agent — Claude Code, Claude Desktop, Codex CLI, Cursor, Windsurf — the ability to dub a video into another language: upload a file or pass a URL, submit a job to the orca/dub model through the OrcaRouter gateway, poll progress, and download the finished MP4.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
dub_health — End-to-end probe of gateway → orca/dub routing. No job is created, nothing is billeddub_upload — Upload a local video file; returns the file_id for dub_create. Files above 64 MiB are chunked automatically (up to 8 GiB)dub_create — Submit a dubbing job (billed). Source is exactly one of file_id or url (YouTube and direct links are fetched server-side). Required: source_langdub_get — Poll a job: queued → in_progress → completed \dub_download — Save a completed job's MP4 to a local path (refuses to overwrite existing files)Configuration is passed through the environment: ORCADUB_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
An OrcaRouter API key is required — every tool call is authenticated: 1. Register / log in at the OrcaRouter console. 2. Create an API key on the token management page (it looks like sk-orca-...). 3. Provide it via the ORCADUB_API_KEY environment variable (see below). Dubbing jobs are billed per minute of source video. Without a key the server still
The server ships on npm as @orcadub/cli, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Orcadub's toolset — dub_health, dub_upload, dub_create and 2 more — is a fair guide to whether it matches your workflow. It is maintained by Continuum-AI-Corp; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| dub_health | End-to-end probe of gateway → orca/dub routing. No job is created, nothing is billed. |
| dub_upload | Upload a local video file; returns the file_id for dub_create. Files above 64 MiB are chunked automatically (up to 8 GiB). |
| dub_create | Submit a dubbing job (**billed**). Source is exactly one of file_id or url (YouTube and direct links are fetched server-side). Required: source_lang, target_lang (never auto), and video_name when using file_id. Optional |
| dub_get | Poll a job: queued → in_progress → completed \ |
| dub_download | Save a completed job's MP4 to a local path (refuses to overwrite existing files). |
Or as host JSON config:
```json
{
"mcpServers": {
"orcadub": {
"command": "docker",
"args": ["run", "--rm", "-i", "-e", "ORCADUB_API_KEY",
"-v", "/path/to/videos:/work", "-w", "/work",
"ghcr.io/continuum-ai-corp/orcadub-mcp-server:latest"],
"env": { "ORCADUB_API_KEY": "sk-orca-..." }
}
}
}Configuration as documented by the project. Restart the client after saving.
An OrcaRouter API key is required — every tool call is authenticated: 1. Register / log in at the OrcaRouter console. 2. Create an API key on the token management page (it looks like sk-orca-...). 3. Provide it via the ORCADUB_API_KEY environment variable (see below). Dubbing jobs are billed per minute of source video. Without a key the server still
| Variable | Description | Required |
|---|---|---|
| ORCADUB_API_KEY | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.