Your agents,now inmotion.
Motion Designer Pro speaks the Model Context Protocol. The coding agent you already use can direct, edit, preview and render production motion graphics. Manage the results in the studio, render them in our cloud, or render them on your machine straight into your repo.
In the cloud
Your agent creates and edits projects in your account. They appear in the studio instantly for hand-tuning, and cloud renders up to 4K arrive as download links. Renders keep going when you close your laptop.
On your machine
With the motionpro CLI bridge, render_local encodes MP4 on your own CPU with the exact engine our cloud uses. Films without uploaded media render fully offline.
In your repo
Keep films as .motion.json next to your code, review diffs, export a standalone HTML animation into /public, and motionpro push when you want to edit visually.
Add the server (once per machine, or per project with --scope project):
claude mcp add --transport http motion-designer-pro https://www.motionvise.com/api/mcp
Inside Claude Code run /mcp, choose motion-designer-pro → Authenticate. Your browser opens so you can sign in and allow access.
Ask for motion:
Make a 20 s 16:9 launch film for our CLI, brand #5b5bf7, and render 1080p
Every connection is signed in and approved by you
MCP access requires your Motion Designer Pro account. When a client connects, it discovers our authorization server, opens your browser, and you sign in and click Allow. The client receives a short-lived access token (1 hour) bound to this MCP endpoint and a rotating refresh token. It never sees your password, payment details or API keys.
See and disconnect apps any time in Account → Developer access. For CI and scripts that can't open a browser, create a personal token there and send it as Authorization: Bearer mdp_… (or MOTIONPRO_TOKEN for the CLI).
- Discover401 → /.well-known/oauth-protected-resource → authorization server metadata
- RegisterClient ID Metadata Document (preferred) or dynamic registration
- Sign in & allowBrowser consent at www.motionvise.com/oauth/authorize, PKCE S256
- WorkBearer token on every MCP call; refresh rotates silently
A hero animation for your website
The agent adapts a gallery film to your copy and brand, then writes a self-contained HTML animation into your Next.js app.
Social cuts from one brief, rendered in the cloud
One film, re-cut for vertical and square, rendered in parallel in 4K while you keep coding.
npx motionpro login --site https://www.motionvise.com # browser sign-in (OAuth + PKCE) npx motionpro list # your cloud projects npx motionpro pull <projectId> # → film.motion.json npx motionpro render film.motion.json -r 1080 -o media/film.mp4 # local MP4 npx motionpro html film.motion.json -o public/film.html # standalone page npx motionpro push film.motion.json # back to the studio npx motionpro scan . -o context.json # read this repo into product context npx motionpro film "Launch film for our new search" --context . # direct a film from your code npx motionpro mcp # stdio MCP server for coding agents
Local rendering uses the same deterministic engine and encoder as our cloud (H.264 High + AAC, loudness-normalised), so frames match the studio exactly. It needs FFmpeg on your PATH.
Public API. The CLI talks to https://www.motionvise.com/api/v1 (me, projects, render/jobs and assets) with the same bearer tokens. MCP tools run the agent and inspector.
list_projects · get_project | Your projects with revisions. They're the same films you edit in the studio. |
|---|---|
save_project · delete_project | Validated saves with revision checks, so an agent never silently overwrites your edits. |
list_templates · create_from_template | Start from a complete gallery film (with score and sound effects). `included` tells the agent which films your plan includes. |
run_motion_agent | Brief → finished film. Our motion director writes a treatment (idea, the thread that carries it, one planned surprise, a beat grid), builds the scenes, product UI and an arranged score, reviews a storyboard, and returns or saves the project. Pass `context` to rebuild your real product. Uses your plan credits. |
inspect_project | Deterministic quality checks: frame-0 hook, safe areas, overlapping text, contrast, dead time, audio coverage. |
render_preview | Still frames returned as images, so your agent can look at the composition before committing. |
render_video · get_render · list_renders | Cloud renders on Creator and Studio: MP4, ProRes 4444 (alpha), PNG sequence or GIF at 720p–4K, 24/30/60 fps. get_render returns a 1-hour download link your agent can curl into the repo. |
export_project | The editable .motion.json, or a single self-contained animated HTML page (fonts, images and sound inlined) to drop into a website. |
get_account | Plan, credits, what the plan includes, and typical credit costs per model, so agents can budget. |
list_motion_skills · read_motion_skill | The craft playbooks our agent uses: timing, typography, sound design, transitions, social formats. |
render_local · export_local (CLI bridge) | Render MP4 or write HTML / JSON on your own machine, straight into the current project folder. Same engine as the cloud. |
scan_codebase (CLI bridge) | Reads the repo you're in: name and promise, routes, design tokens, fonts, components, real UI copy, logo paths and the motion your app already uses. Env files and secrets are never read. Hand the result to run_motion_agent as context. |
{
"version": 2, "title": "Dashboard launch", "aspect": "16:9", "fps": 30,
"scenes": [{
"name": "Hook", "duration": 3.2, "background": "#0b0f1a",
"transition": { "preset": "slide-up", "duration": 0.6, "ease": "expo.out" },
"layers": [{
"type": "text", "text": "Ship *calmer*.", "x": 50, "y": 46, "fontSize": 120,
"fontFamily": "Manrope", "fill": "#f2f5ed", "accent": "#3b5bfd",
"textMode": "words", "in": { "preset": "rise", "duration": 0.7, "ease": "expo.out" }
}]
}],
"audioTracks": [{ "kind": "music", "style": "cinematic", "tempo": 96, "start": 0, "duration": 25 }]
}Scenes with transitions and camera keyframes, 21 layer types (text, counters, shapes, paths, icons, images, device mockups, charts, particles, light effects…) with entrance, exit and loop animations, per-property keyframes and easing, and audio lanes with music, sound effects, uploads and AI audio.
The same engine renders the browser preview, the HTML export and every MP4, in the cloud or on your machine.
Open Developer access