mcp.film

mcp.film / Editing & Post / OrkasVideoStudio

OrkasVideoStudio

Officialby Orkas-AIfreeverified Aug 12, 2026

Local MCP and CLI toolkit for agent-driven video composition, editing, analysis, and rendering.

What it does

OrkasVideoStudio gives coding agents typed MCP tools for building editable plan.json timelines, rendering HyperFrames compositions, and handling practical post work with ffmpeg. It can trim, concatenate, mix, caption, transcribe, inspect shots, and run deterministic delivery checks before a final render. The zero-key path works locally; image, speech, and video generation are optional provider-backed extensions.

Connect

Claude Code
claude mcp add ovs -- node /absolute/path/to/Orkas-VideoStudio/packages/mcp/dist/index.js
Claude Desktop (claude_desktop_config.json)
{
  "mcpServers": {
    "orkas-videostudio": {
      "command": "node",
      "args": [
        "/absolute/path/to/Orkas-VideoStudio/packages/mcp/dist/index.js"
      ]
    }
  }
}
Cursor (.cursor/mcp.json)
{
  "mcpServers": {
    "orkas-videostudio": {
      "command": "node",
      "args": [
        "/absolute/path/to/Orkas-VideoStudio/packages/mcp/dist/index.js"
      ]
    }
  }
}
Auth: none

Tools you'll see

draftrenderedit_trimedit_concatedit_burnsubsedit_mixtranscribescenesqualityplan_promise_check

Field notes

MIT and source-installable while the npm packages are still being published. The working path requires Node 22+, pnpm, a source build, and ffmpeg/ffprobe for editing and local media QA. The MCP is local stdio only, and generated media is written to caller-supplied filesystem paths. The core composition, editing, analysis, transcription, and render path needs no provider key; speech, image, and video generation require separately configured provider credentials.

Pairs well with