Connect your AI assistant
Design in Mixavis by chatting with your AI assistant. Included with Freelancer and Studio, with a free trial on Free.
Mixavis publishes a connector — an MCP server, the standard AI assistants use to reach outside tools. Once it is connected, you can ask your assistant to work on your Mixavis projects in plain language, and the changes are saved to your account. You do not need the editor open, and nothing is copied out of Mixavis to get there.
It runs on your own assistant subscription. Mixavis charges no credits for connector work, with one exception: asking the assistant to generate an image spends the same Mixa AI credits an image costs inside the editor, and the assistant is told the price and your remaining balance each time.
What you need#
- A Mixavis account on Freelancer or Studio. A Free account gets a 30-day free trial of the connector, with 100 edits to use in those 30 days. The 30 days start the first time you connect. Reading your designs does not count as an edit, and if the 100 edits run out early, the assistant can still read your projects until the 30 days end. Image generation is not part of the trial, since it spends Mixa AI credits.
- An AI assistant that supports remote MCP connectors, on a plan that allows them.
Connecting it#
- In your assistant, open the connector or integrations settings and choose to add a custom connector.
- Give it the Mixavis server URL:
https://mixavis.com/api/mcp - Your browser opens a Mixavis consent screen showing which account is signing in and what the connector will be allowed to do. Read it, then choose Allow.
- You are returned to your assistant, connected. Ask it to list your Mixavis projects to confirm.
The consent screen runs on mixavis.com using the session you already have. Your assistant never sees your password or your payment details, and Mixavis never stores a credential for your assistant.
What you can ask for#
The connector reads and edits the document itself, so the useful requests are the ones about structure and timing rather than about clicking:
- "List my Mixavis projects and tell me what is in the newest one."
- "In my title card, hold the logo for half a second, then fade it out over 400ms."
- "Add a drop shadow to every text layer and stagger their entrances by 80ms."
- "Build a bone chain down this character's arm and bind the artwork to it."
- "Read this project and tell me why the ending feels abrupt."
Ask for the outcome, not the keystrokes. "Make the entrance land harder" gets a better result than "set the easing to 0.2, 0, 0, 1", because the assistant can read the surrounding timing and choose.
What the connector exposes#
These tools, and nothing else. Most of them only read:
list_projects— the designs in your account, most recently updated first.create_project— a new, empty design at the size, frame rate and duration you ask for. Counts against your plan's project limit the same as one made in the editor.add_image— fetches a public image URL into your Mixavis storage and adds it as a layer at its real size. It counts against your storage quota exactly like an upload, and only public hosts are fetched.generate_image— makes a picture from a prompt with the image model and adds it as a layer, stored in your account like an upload. This is the one connector tool that spends Mixa AI credits — the same number an image costs in the editor — and it needs a plan that includes Mixa AI. A failed generation charges nothing; a rejected prompt is reported so the assistant can reword it.add_font— the same for a WOFF2/WOFF/TTF/OTF font: stored in your account and registered on the design, so text layers can use it by family name.rename_project,rename_page,delete_page,move_page— the housekeeping the editor does from its panels. A design always keeps at least one page.share_project— turns the public hosted-player link on or off. Turning it on again issues a new link and the old one stops working, and the assistant is told so.export_project/get_export— a finished MP4, WebM, GIF, PNG, JPEG, Lottie or dotLottie. Rendering happens in your open editor tab: a prompt appears there, you click Start, the file lands in your storage and the assistant gets the link. Nothing renders without that click.delete_project— removes a design. The assistant must pass the project's exact title as confirmation, and is told to ask you first.get_project— one design: canvas size, duration, frame rate, its pages, and the layers on one page (the active page unless the assistant asks for another by name or number).add_page— a new empty page in a design, inheriting the canvas size. Every reading and editing tool can then be pointed at it.set_active_page— chooses the page the editor opens on, and the one the other tools default to.list_versionsandrestore_version— the restore points Mixavis keeps. Every assistant edit leaves a before-and-after pair, so "put it back how it was before your last change" is always possible — and a restore saves the current state first, so it is itself undoable.get_geometry— where each layer's artwork actually renders, in canvas pixels, after its viewBox mapping, scale and rotation are applied. A vector's box and its art are not the same rectangle, and this is the tool that tells them apart.render_preview— a flat PNG of a page for a composition, colour and timing check: the assistant can ask for any moment on the timeline, or up to six moments as one labelled filmstrip, drawn with the same easing the editor uses. It says in the same reply what it did not draw — effects, motion paths, images, 3D — so the assistant never mistakes the preview for the finished design.get_capabilities— Mixavis reference documentation, including the document-ops schema below.apply_ops— the only tool that changes anything.
The document-ops schema#
Edits are made by sending document ops — small, named instructions against your design, applied in order. They cover layers (addLayer, updateLayer, deleteLayer, duplicateLayer, reorderLayer), animation (setKeyframes, setEasing, setAnimation), appearance (addEffect, addModifier, setCanvasBg), timing (setDuration), and rigging (addBoneChain, addIK, bindMesh).
The vocabulary is exact and the full schema is served by the connector itself through get_capabilities, so an assistant always reads the version matching the running server rather than a copy that can drift. Op names are validated before anything is written: an unrecognised op, or one that needs the Mixavis editor, is rejected by name and the whole batch is refused rather than partly applied. If an op fails while running — a layer name that matches nothing, a rig step the armature cannot take — the reply names what did not take effect and tells the assistant to re-read the design before sending the rest, so nothing lands twice.
Every apply_ops call must carry the revision string from a recent get_project. If the design changed in between — including edits you made yourself in an open editor tab — the call is refused rather than applied over your work.
What it will not do#
- It cannot delete your projects. Nothing in the connector removes a project.
- Every edit makes a restore point first. Changes land in your version history, so anything the assistant does can be rolled back from the editor.
- Some work still needs the editor open — weight painting and the character library. Everything else runs over the connector, physics included (the assistant sets it up and bakes it to keyframes) and image generation too; a video render happens in your open tab when the assistant asks. The assistant will say so rather than pretend.
- It will refuse a stale edit. If a project changed since the assistant last read it, the edit is rejected rather than applied over your work. Ask the assistant to re-read the project and try again.
The editor does not live-update from connector edits, so an open tab keeps showing the document as it was when you loaded it. It will tell you when it falls behind: come back to the tab and a bar appears saying This project changed elsewhere. If you have no unsaved work there, Load latest brings the assistant's version in with one click. If you do, you choose which version wins — and keeping yours saves theirs to History first, so nothing is lost either way.
Disconnecting#
Open your Mixavis dashboard and use Disconnect under Connected apps. Access ends immediately. Removing the connector inside your assistant also ends it, since the assistant revokes the token as it goes. Access stops on its own too if your plan no longer includes the connector, or if the account is suspended.
A connection also ends by itself if it goes 30 days without being used, or 180 days after it was made, whichever comes first. Reconnecting takes a few seconds and the limits reset — the point is that a connector you set up once and forgot cannot keep read and write access to your designs indefinitely.
If something goes wrong#
- "Your 30-day free trial of the connector has ended" — the account you consented with is on Free and its 30 days are over. Check which account you signed in as; it is the one on the consent screen, not necessarily the one in the assistant. Use See plans there, then start the connection again.
- "This account has used all 100 edits of its free trial" — the assistant can still read your projects until the 30 days end, but editing needs Freelancer or Studio.
- The consent screen appears but your assistant keeps waiting — a refused connection only tells your assistant once you press Return to… on that screen. Mixavis will not report your plan or account status to an application you have not authorised, so nothing is sent until you choose to send it.
- "Authentication required" after it worked before — the connection was revoked, or it expired: 30 days unused, or 180 days old. Remove the connector and add it again.
- An edit was rejected by name — the assistant guessed a setting that does not exist. Tell it to re-read the capabilities before retrying; it is designed to ask rather than invent.
Anything else, write to hello@mixavis.com with the project name and roughly what you asked for.
See plans →