Your agent's toolbox
Most video tools grow by adding integrations: a Stripe of partnerships, one service at a time, each behind a settings page. Mixture doesn’t need to, because of where it sits.
Your agent is the integration layer. It runs on your machine, with your keys, your files and whatever MCP servers you’ve connected. It can already reach your recordings, your APIs, your drive, your tracker. Mixture is the canvas it delivers into — and everything it delivers arrives as ordinary scenes, layers and assets you can edit by hand.
So the question isn’t “does Mixture integrate with X?” It’s “can your agent reach X?” — and the answer is usually yes.
Three sources of material
Section titled “Three sources of material”1. What Mixture makes itself. Images are first-party: a server-side model generates backdrops, product scenes and textures straight into your assets, no key required. Everything on the canvas — motion, effects, 3D, captions, data graphics — is Mixture’s own.
2. What your agent ships with. This differs by runtime, and it changes often. Codex has its own image generation; Claude Code doesn’t. Some have web search, some have sandboxes, some have neither.
3. What you’ve given it access to. The big one. Any service your agent can call — with a key in the environment you run it from, or an MCP server you’ve connected — becomes something it can produce material with:
| You want | Reach it through |
|---|---|
| Voice-over | ElevenLabs, OpenAI, or any TTS your agent can call |
| Music | A music-generation API with a key in your environment |
| B-roll / generated video | Runway, Veo, Higgsfield, or similar |
| Screen recordings | Supercut’s MCP |
| Brand material | The web — the real typeface from a site’s @font-face, the logo, the palette |
| Your own data | A drive, a database, an analytics API, a CSV on disk |
| Issues, docs, tickets | Whatever MCP servers you already use |
None of that needs an integration on our side. Drop a key into the environment your agent runs in, or connect one more MCP server, and the next build can use it.
Chaining it into one instruction
Section titled “Chaining it into one instruction”The point isn’t that these services exist — it’s that one instruction can span them:
“Grab my latest Supercut recording, cut the dead air, write and generate a voice-over with ElevenLabs, caption it from that script, and give me a 30-second vertical cut.”
“Pull the numbers from the analytics MCP, chart them with our brand colours, and add a Runway b-roll clip behind the intro.”
“Take the copy and fonts from acme.com, generate the hero imagery, and build a 20-second promo in that brand.”
Each of those crosses three or four services. Your agent sequences them; the results land in your project as assets; you adjust whatever you don’t like in the editor.
What the agent will tell you
Section titled “What the agent will tell you”Because the answer depends on the agent you picked, Mixture’s guidance tells it to check what it has and say so in its first message:
“I can make imagery and a voiceover here; b-roll would need to come from you.”
That line is the fastest way to learn the shape of the agent you’re using — and that a different runtime, or one API key, would change what the piece can be. It asks before spending your credits, too.
The rules it works under
Section titled “The rules it works under”Generated material is useful; pretending it’s real isn’t. So:
- Generated assets are labelled as generated in the asset’s description.
- Generated material is never used as proof: product screens, testimonials, names, faces and numbers come from you.
- Real assets beat invented ones every time — see give it something to work from.
Work it does outside the canvas
Section titled “Work it does outside the canvas”The same reach applies to the work before the build, not just the material:
- Mining a brand — reading a site and bringing back its actual typeface files, logo and palette, rather than approximating them.
- Preparing data — fetching, cleaning and reshaping a dataset in code first, then handing tidy rows to data-driven layers.
- Background removal — matting a subject with a model like Robust Video Matting, delivered as an alpha cutout asset.
- Writing effects — a look that doesn’t exist yet becomes WGSL you can tune, or a GLB it sources or builds.
- Rendering and delivering — “export it and drop the MP4 in this folder”, using Mixture’s own renderer.
The pattern never changes: the agent works wherever the work is, and Mixture is the canvas it delivers into.