Quickstart: build with an AI agent
The FX Express MCP server exposes template authoring as tools an AI agent can call. You describe the video in a sentence; the agent writes the template, compiles it, and publishes it as a dynamic movie. Then you render variants of it in the Console.
The video below is the whole path end to end: the prompt, the agent’s build, a few by-hand adjustments in the editor, and finally the publish and the two rendered variants.
You need an ImpossibleFX account and a project — see Before you start.
1. Connect the MCP server
In Claude, go to Customize → Connectors and click Add custom connector. Give it a name — FX Express — and paste the server URL:
https://mcp.impossible.io/fxexpress/mcpContinue, and Claude sends you to an Impossible Software sign-in page. Approve access, and FX Express appears in the connectors list as Connected, with its tools available in every chat. This is a one-time setup.
The server speaks Streamable HTTP and authenticates with OAuth 2.1 against https://accounts.impossible.io. Any MCP client works, not just Claude. In Claude Code, for instance: claude mcp add --transport http fxexpress https://mcp.impossible.io/fxexpress/mcp.
2. Describe the video
Start a chat and ask for the template. Be concrete about the scenes, the placeholders, and where to save it:
Build me a personalized insurance premium quote video with FX Express.
Three scenes: 1) an intro that says "Hello {name}", 2) a quotation scene
showing the policy type {policyType}, the coverage {coverage} and the
monthly premium {premium}, 3) a closing call-to-action scene with a
clickable button-style layer "View my quote".
Calm, modern insurance look: deep blue, white, one warm accent.
Save it in my project project://YOUR-PROJECT-ID (eu-west-1) as
insurance-quote.fxt, compile it and publish it.Two details in that prompt do the real work:
- The braces. Anything you write as
{name}becomes a render variable rather than fixed text. Name them as you’ll pass them to the API later. - The project reference.
project://YOUR-PROJECT-IDplus a region tells the agent where the template lives. Copy the project ID from the Console.
Or let the agent make the project
You don’t have to have a project first. Ask for one in the same breath and the agent creates it for you:
Create a project for this and build me a personalized insurance
premium quote video with FX Express. Three scenes: …It will ask which region to create the project in — that choice is worth a moment’s thought, because a project’s region is where its videos render and it isn’t something you change later. Pick the one closest to your viewers; see Regions & Endpoints.
From there the agent has the project reference it needs and carries straight on into the template, so the rest of this tutorial is the same. The new project shows up in the Console like any other.
3. Watch the agent work
The agent runs a fixed sequence, and it is worth recognising in the tool log:
| Tool | What happens |
|---|---|
get_skill | Loads the FX Express authoring guidance — layout grid, typography scale, animation rules |
create_template | Creates the empty .fxt in your project |
compile_html | Compiles the authored FXHTML into scenes and elements, and returns diagnostics |
publish | Turns the compiled template into a dynamic movie |
compile_html is the loop: if the layout has problems — a text box too short for its
descenders, an element off-canvas — the diagnostics come back and the agent fixes and
recompiles until the compile is clean. Let it finish that loop before you look at the
result.
Ask for changes in the same chat — “make the premium twice as large”, “hold the last scene two seconds longer”. The agent edits the same template and recompiles; you don’t start over.
4. Check the placeholders
When the agent reports it is done, open the template’s preview. Every {...} you asked for
should appear as a placeholder rather than a literal value — {name} in the intro,
{policyType}, {coverage} and {premium} in the quotation scene. Those names are the
contract between the template and everything downstream.
5. Adjust by hand, then publish
The agent’s draft is a normal template, so anything you want to change yourself, you change in the editor — in the video, the greeting’s font weight and colour, and the call-to-action button’s link. Working by hand from a blank canvas is the other quickstart path; the two meet here.
When it looks right, File → Publish… in the editor. Confirm the resolution and frame rate, and set the name of the published movie — this is the name the API and the Console will use, so keep it short and stable.
Publishing takes a snapshot. Later edits don’t change the live movie until you publish again, so you can keep working on the template while the published one keeps rendering.
6. Render two variants
Publishing made the template a dynamic movie named insurance-quote. In the
Console, open your project and click Dynamic Movies in
the sidebar.
-
Select insurance-quote in the list.
-
Open the Play tab. The parameter form lists exactly the placeholders from your template — one field per variable, nothing to configure.
-
Fill in the first variant and press play:
Parameter Value nameAlex policyTypeComprehensive Home & Contents coverage500.000 € Sum Insured premium42,00 € / month -
Now change two values and play again:
Parameter Value nameSam policyTypeBasic Contents coverage150.000 € Sum Insured premium19,50 € / month
Two videos, one template, no re-render of anything you built. That is the whole idea: the template is the design, the parameters are the person.
The Render API tab on the same screen turns whatever you typed into the parameter form into a ready-made render request. It is the quickest way to get the exact JSON body for your own code.
Next
Rendering from the Console is a preview. To do it from an application, see Render from your app, or jump to the Render API reference.