MCP Server — Early Access

Plug the studio into your Claude.

The HeyMotion MCP server gives Claude hands on all 104 templates: it browses them, fills in your content, previews the frame, and renders a frame-perfect MP4 into your Downloads — locked to your brand, in any format. One-line install. Zero npm dependencies.

claude — heymotion
you: "make a 9:16 stat card — 1.2M views in 30 days"
⦿ claude → describe_template → render_preview → render_clip
big-counter-1080x1920.mp4 · 30fps · H.264 · ~/Downloads
What Claude gets

Six tools. The whole library.

list_templates

All 104 templates by category — stat cards, lists, devices, subscribe pack, overlays, transitions.

describe_template

Every editable field with labels and defaults, so Claude knows exactly what content to fill.

render_preview

A mid-animation PNG Claude can actually see — it checks the frame before spending a render.

render_clip

Frame-perfect 30fps MP4 in 16:9, 9:16, 1:1, 4:5 or 4:3 — dropped straight into ~/Downloads.

get_brand / set_brand

Your colors, fonts, logo and handle persist across every chat. Renders are always on-brand.

how it renders

Headless Chrome + the same deterministic virtual-time engine as the web studio. MCP output is pixel-identical to the app's.

Setup

Two minutes, three steps.

Requirements — you probably have both already:

Node 22+ (nodejs.org)Google ChromemacOS · Linux · Windows

Install — one line in Terminal

Downloads the server + template engine into ~/sp-motion-studio. Nothing else touches your machine — no npm, no build step.

curl -fsSL https://heymotion.io/install-mcp.sh | bash

Add it to Claude Desktop

Settings → Developer → Edit Config, then add this block (the installer prints it with your exact path too):

{ "mcpServers": { "sp-motion-studio": { "command": "node", "args": ["/Users/YOU/sp-motion-studio/tools/mcp/server.mjs"] } } }

Using Claude Code instead? claude mcp add sp-motion-studio -- node ~/sp-motion-studio/tools/mcp/server.mjs

Restart Claude — and ask for a clip

That's it. First render boots Chrome quietly in the background (~2s), then each clip takes seconds. MP4s land in your Downloads, ready for your editor.

Seeing "Add custom connector" under Settings → Connectors? Use it — that's the remote connector: grab your personal key URL and paste it, no install. This local setup is the power-user path — your own machine renders (unlimited, private, files straight into Downloads) and it plugs in via Settings → Developer → Edit Config (step 02 above), not the Connectors dialog.
No install at all

Remote connector BETA

Prefer the dialog you saw in Settings → Connectors? The hosted connector renders on our servers — nothing to install, works on claude.ai web and desktop. Grab your personal key from the studio, paste your URL, done.

Get your personal key

The remote connector is tied to your account so your renders count against you, not a shared pool. Open the studio, sign in, and in the right-hand panel click 👤 Account → 🔑 My remote MCP key. Copy your personal connector URL — it looks like:

https://mcp.systemprompt.co/mcp?key=mtn_your-key

Keep it private — anyone with the URL can render on your account. You can rotate it anytime from the same panel, which instantly revokes the old one.

Add the connector

Claude → Settings → Connectors → Add custom connector. Name it HeyMotion and paste your personal URL from step 01 (the one ending in ?key=…) into the URL field:

https://mcp.systemprompt.co/mcp?key=mtn_your-key

Leave the OAuth fields empty, hit Add, and enable it in your chat's connector menu.

Ask for a clip

"Make me a 9:16 big-counter — 1.2M views in 30 days." Claude previews it, renders server-side, and hands you an MP4 download link. Beta limits: 20 renders/hour on your account, 20s max per clip. For unlimited renders and files straight into your Downloads, use the local install above.

Try these

Things to say to Claude

Make me a 9:16 big-counter clip — 1.2M views in 30 days
List the subscribe templates, preview subscribe-burst, then render it vertical
Render a checklist with my three launch steps, 16:9
Set my brand red to #FF3355, then re-render the lower third
Give me the iris transition in navy and the doors transition in red
Good to know

The fine print (short version)

Overlays are green-screen. Templates marked as overlays render on pure #00FF00 — chroma-key them over your footage.
H.264 everywhere. Chrome encodes H.264 natively; if your browser only does VP9, the server auto-transcodes when ffmpeg is installed — either way QuickTime, Premiere and Final Cut open it.
Renders are local. Your content never leaves your machine — the server runs on your computer and drives your own Chrome.
Early access. The MCP server is free while HeyMotion is in beta; it graduates to the Studio tier at launch. Lock founding pricing →