The studio / Guide

Connect your agent.
Keep the timeline.

Your agent connects over MCP and gets a real editor, every generative model behind one router, and rendering in the cloud. Everything it builds opens in the timeline, so you can finish by hand.

01 / Connect / MCP

One URL, then sign in.

Add Flimming as a remote MCP server in your client. You sign in through Flimming, review the permissions and choose which projects the client can reach.

MCP server URL

In a client that supports remote MCP servers (Claude, ChatGPT developer mode, Codex, Cursor or Claude Code), add this site’s address followed by /mcp.

Follow the sign-in flow and choose which projects the client can access.

Ask your agent to list the Flimming tools, then give it your brief and media.

You stay in control of access. Review or revoke connected clients at any time.

Manage agent connections ↗

Never paste your browser session or a sign-in link into an agent. The connection uses OAuth with project-scoped permissions.

02 / What your agent gets

The editor as tools. The craft as skills.

Editing tools. Timeline, multicam, colour, masks and tracking, subject mattes, the mixer, retime and delivery. Large clients can search the catalog with editor_discover_tools and load schemas with editor_get_tool_schemas.
Skills as resources. Editing, colour, sound, pacing, generation and Remotion know-how, served as MCP resources your agent reads when it needs them, plus an operating guide sent at connection.
The model router. models_list shows every model with what it excels at, what to avoid it for and its limits. models_recommend ranks the models that can serve a shot from its needs, with a quote, before anything is spent.
Durable cloud jobs. Renders and generations run in the cloud and survive a dropped connection. jobs_wait waits for a job to settle instead of polling.
A link back to the timeline. Finished renders carry an editorUrl, and your agent can share a timeline link for any project. Open it in the browser and carry on by hand; edits made by either side show up for the other.

03 / Credits

Pay for cloud work. Not for editing.

Every plan unlocks the whole studio. Plans start at $19 a month and include monthly credits; top-ups are available whenever you need more.

Uses no credits	Uses credits
Editing by hand or through your agent: every timeline, colour, audio and mask edit Reading projects, media and the model catalog Recommendations and quotes Waiting on jobs and opening timeline links	Cloud renders and delivery Rendering Remotion code in the cloud Video, image and voice generation Transcription and subject mattes Hosted review The experimental built-in assistant, on every model call

Your agent can ask for a quote before any job that spends credits. Your own agent’s model usage is billed by its provider, not by Flimming.

04 / Review

Your agent reviews. A second opinion is optional.

By default, your agent reviews its own work: it can read the timeline, pull frames and check the render. When you want more, hosted review sends the cut to a native multimodal model that watches the video with its audio and reports what works and what doesn’t. Your agent can use that report or ignore it. Hosted review uses credits.

05 / Remotion

Your agent writes the code. We render it.

For motion graphics, titles and animated explainers, your agent writes Remotion code. Flimming builds and renders it in the cloud in a sandbox and places the result on the timeline, with a live preview while you work.

Rendering it yourself? Upload your own render as media and edit it like any other clip.

06 / Editing by hand

Your browser is the studio.

Open Flimming and sign in with your email. Bring in your media, cut on the timeline, grade, mix and deliver. There’s nothing to install, and you never need an agent. An experimental built-in assistant is available if you want one.

Open the editor ↗

Account access follows your workspace’s registration settings.