The Motion by Frapea MCP server,
connected in one click.

close_composition — Closes a composition and removes it from the user's tabs. Use it to clear up attempts you made along the way — an agent that leaves ten of t

connect — Pairs you with a Motion browser tab. The user has an eight-character code on screen, under the Connect MCP button — something like K7M4-P2Q9

create_session — Starts a Motion session WITHOUT the user having a tab open. Use this when they have no pairing code — you can create and edit compositions i

wait_for_tab — WAIT UNTIL THEY HAVE MOTION OPEN. Everything that has to SEE a composition — inspect_composition, and anything touching their media — runs i

tell_user — PUT A SENTENCE ON THEIR SCREEN, as you work. They are watching the Motion tab while you build, and between your tool calls it shows nothing

read_skill — Motion's authoring guides. Read {topic:'motion'} first — it is the API contract: what compiles, what resolves, what renders. Then {topic:'mo

list_media — The user's media library: folders, and files with id, name, kind, size and folder. `storage` says whether a file is 'linked' (still on their

put_media — Adds a file to the library from a URL — the BROWSER fetches it, so nothing travels through this connection, but it only works on https hosts