Run du -sh on any developer laptop that has experimented with local Claude Code video skills for a few weeks. Between three orphaned Remotion node_modules trees, cached headless Chromium builds, forty gigabytes of half-rendered .mov intermediates in /tmp, and brittle ffprobe bash wrappers, your drive turns into a post-production junkyard.
Worse, every time a subtitle clips outside the 9:16 safe zone, your MacBook fans spin to 5,000 RPM while Claude Code burns Claude Opus 5.5 ($4 / $20 per 1M tokens) or Claude Fable 5.2 ($8 / $40) rewriting JSX layout math.
Developers stay in Claude Code because the terminal sits right next to git history, release notes, and local footage folders, not because anyone enjoys maintaining a local render farm.
Registering Mixbash’s Video Editing MCP (https://mixi.mixbash.com/api/agent/mcp) over Streamable HTTP replaces that entire local stack with one remote connector authenticated via OAuth 2.1 PKCE or a Bearer token. Zero npm packages to maintain, zero Chromium mismatches.
Here is what an actual terminal run looks like. You drop raw phone takes or UI captures into a local folder, transcode once to the lightweight mixbash-intake-v1 spec (1080p H.264 CRF 23 AAC with word-level timestamps), and push the files directly to signed storage URLs using prepare_upload, complete_upload, and register_media.
Next, Claude Code inspects your available aesthetics via get_styles, initializes create_project locked to your custom brand style slug, drafts or refines the spoken narrative with draft_script and revise_script, and maps B-roll timing with plan_visuals. One call to generate_preview hands motion authoring and automated frame-level QA off to Mixbash’s cloud workers.
Because your local session only passes structured JSON arguments and short creative notes, you do not have to keep Claude Code pinned to Opus 5.5 or Fable 5.2 during video tasks. Switching the session model to Claude Haiku 5.5 ($0.10 / $0.50 per 1M tokens) drops your LLM cost below $0.002 per Reel with zero change in visual output.
One practical constraint is worth respecting: a terminal prompt cannot tell you whether a cut *feels* rushed. Even after Mixbash’s automated visual QA clears a preview, always open the link returned by get_project_page in your browser and watch the 30-second cut with sound on.
If beat three feels tight, run revise_preview in plain English; once it clicks, call approve_review, render_final, and get_artifact to pull the master MP4 right back into your working directory.