Coming soon The hosted app is not open yet. These pages describe MotionTyped as it works today, in testing. Anything that is not available yet is marked. Join the waitlist to hear when it opens.
Set it up
The MCP server runs on your own machine today, from the self-hosted package. It uses your Anthropic key, or your Claude Code login when there is no key. Register it once:
claude mcp add --scope user motiontyped -- \
node /abs/path/motiontyped/apps/mcp/dist/index.jsThe developers page has the .mcp.json form and the other settings, and the self-host guide has the install.
Not available yet: a hosted MCP endpoint. Claude can only reach MotionTyped through a copy you run yourself.
The tools
There are 36 tools. Most work on a run, which is one film project, named by a runId.
| Group | Tools |
|---|---|
| Brief and concepts | draft_brief writes the brief and returns at most three questions. answer_brief settles them. list_concepts shows the concepts. choose_concept picks one (t1…, or surprise). |
| Make a film | generate runs the whole pipeline. It can stop at the concepts (concept: "ask") or after the brief (briefOnly), take a goal, aspects, a preset and voice. get_run shows state, progress, QA and exports. |
| Your material | upload_asset attaches a logo, screenshot or brand kit. read_screens reads screenshots of your real product UI. |
| Edit | get_versions, edit_storyboard, undo_edit, redo_edit, diff_versions, regenerate_scene, list_insertables, build_insert_ops, scene_compositions. |
| Music and panels | music_shortlist ranks tracks. plan_panel_ops builds the edits for music, camera and pace, or colours. Apply them with edit_storyboard. |
| Check and export | export_check lists what would block an export. export_run renders a version, with captions if asked. render_video, qa_video and critique_video render and review a run. |
| Presets and batches | save_preset, list_presets, delete_preset, apply_preset, batch_generate (one URL, several goals) and get_batch. |
| Templates | list_templates, get_template, render_template, revise_template. |
| Single steps | ingest_url and generate_storyboard run the early stages one at a time. |
edit_storyboard takes the same typed edits as the editor: set text, set a property, change a length or a transition, move, delete, duplicate or insert a scene, and change film-level settings. It applies all of them or none, and each accepted batch becomes a version, so undo_edit works. Pass the baseVersion you got from get_versions. A stale base or a batch that breaks a rule comes back as an error and changes nothing. It does not render: call export_run or render_video afterwards.
A short example
You say to Claude:
Make a 30-second launch film for acme.com for LinkedIn.
Ask me the brief questions first, then show me the concepts.Claude then calls, in this order:
draft_briefwith the address and your request. It returns arunId, the brief and up to three questions with options. Claude asks you.answer_briefwith your answers.generatewith therunIdandconcept: "ask". It stops once the rough previews are drawn.list_concepts. Claude describes each concept to you and you choose one.choose_conceptwith that concept's id. The film is built. This takes minutes.
Then you say Make the first headline shorter, then export the vertical one with captions.
get_versionsfor the head version and the scenes.edit_storyboardwith thatbaseVersionand oneset_textedit on the headline.export_check. If it lists blocking problems, Claude fixes them or tells you.export_runwithaspects: ["9:16"]and the captions you want.get_runthen lists the exported files.
Captions as SRT or VTT need a voice-over, as in the app. See Exporting.