Claude Motion Skills and MCP
If you want the Motion workflow outside the Team plan, it lives in Claude Code as skills. These are the ones people actually install.
The Claude Motion skill stack
HyperFrames
HeyGen · Apache 2.0HTML in, deterministic MP4 out. Headless Chrome seeks to each frame time, captures it, and FFmpeg encodes the result — so the same input produces the same video every time.
Needs: Node.js 22+, FFmpeg
Ships its own Claude Code skills, including a faceless-explainer skill and a Figma import skill for brand tokens and storyboards.
Remotion
Open sourceWrite video as React components. Strongest at batch rendering — one composition fed many data sets to produce many videos.
Needs: Node.js
A remotion skill for Claude Code and Codex is widely used. The Studio is good for preview; most people make edits by asking Claude rather than dragging timelines.
JavaScript animation skill packs
CommunityHave Claude write a single HTML page that draws every frame, plus a soundtrack synthesised in code, then render to MP4 in a headless browser.
Needs: Node.js, headless browser, FFmpeg
One side-by-side test produced a finished clip in about thirteen minutes including render.
Voiceover via TTS MCP
Various (e.g. Fish Audio MCP)Generate a voiceover — including a cloned voice — from inside Claude Code, then sync scenes to it.
Needs: An MCP server and a TTS account
Fills the biggest gap in code-built video: Claude writes a good script, but default free voices sound flat.
Captions from voiceover
whisperTurn a recorded or generated voiceover into timed captions that the animation can follow.
Needs: whisper (local or API)
Useful when the video will be watched muted, which is most social and in-app placements.
Music and sound in code
tone.jsCompose whooshes, clicks and simple beats programmatically and sync them to the timeline.
Needs: tone.js
Good for UI sounds and simple beds. A produced soundtrack still needs a music model or a licensed track.
A minimal Claude Motion style setup
You do not need the whole Claude Motion skill stack. The smallest setup that gets you a real MP4 from Claude Code is one renderer plus FFmpeg. Pick HyperFrames if you want predictable Claude Motion style output, Remotion if you will render many versions.
# 1. Prerequisites node --version # 22 or newer for HyperFrames ffmpeg -version # 2. Add a renderer and its Claude Code skill # (follow the project's README — both ship skills for Claude Code) # 3. In Claude Code, brief it the same way you would brief Claude Motion: # who will watch, where it plays, how long, plus attached assets
Then add pieces only when a gap between your setup and Claude Motion appears. If your videos will be watched with sound, add a TTS MCP for voiceover. If they will be watched muted, add captions. Music comes last, and is the piece most worth buying rather than generating.
Skills vs Claude Motion: the honest trade
Claude Motion wins on friction. No install, an editor for small timing changes, one-click export, and hand-offs to seven editing tools. For a team that just wants an explainer by Friday, Claude Motion is the obvious choice if the plan allows it.
Skills beat Claude Motion on control. You set resolution and frame rate explicitly — neither is published for Claude Motion. You can add voice and music, which the Claude Motion help article does not mention. You can render a hundred variants from a spreadsheet. And you are not depending on a beta that could change shape.
The quality ceiling is the same with or without Claude Motion, because the same model is writing the same kind of code. What separates good output from generic output is the brief and the rules around it — brand assets, motion instructions, things to avoid — not whether you used Claude Motion or a skill.
Choosing between Claude Motion and a skill setup
If your workspace has Team, start with Claude Motion. It is already installed, already on, and good enough for most internal explainers. Move to a skill setup only when you hit something Claude Motion does not do: voiceover, music, explicit resolution, many variants, or a house style enforced across a series.
If you are on Pro or Max, the skill route is how you get Claude Motion style output at all. Start with one renderer and FFmpeg, make one short video end to end, and add pieces only when a specific gap appears. Installing every tool on day one is the fastest way to spend an evening debugging instead of making anything.
For agencies and creators producing client work, the skill setup is often the better long-term choice even with Team available. Claude Motion ties output to a beta feature inside one workspace; a Claude Code project with Remotion or HyperFrames is portable, versionable and under your control.
Whichever route you take, the expensive part is the same: the time Claude spends writing and revising animation code. Claude Motion does not make that cheaper. It makes the setup around it disappear.