NeoMotion documentation
Enough to install NeoMotion, connect your keys, brief the agent and get an editable timeline out the other end. It is a first pass — the last section lists what is still missing rather than pretending it is covered.
Start here
NeoMotion is a desktop motion-graphics editor with an AI agent attached. The agent does the production — research, script, assets, composition — and hands you a real timeline instead of a finished file. Everything runs on your machine.
The shortest path from nothing to a rendered video:
- Create an account and download the app for macOS or Windows.
- Sign in from the app to start your free 14-day Studio trial.
- Add an OpenAI key if you want the agent; the editor works without one.
- Brief the agent, approve the storyboard, edit what it built, export.
Install & first launch
Builds for macOS and Windows are published on the download page once you are signed in, and every release is listed on the changelog.
macOS
Right-click NeoMotion.app → Open → Open, or allow it under System Settings → Privacy & Security. If macOS calls the app damaged, clear the quarantine flag:
xattr -dr com.apple.quarantine /Applications/NeoMotion.appWindows
SmartScreen shows “Windows protected your PC”. Click More info → Run anyway. First install only.
Starting the trial
In the app: Settings → License → Sign in with browser. Approving in the browser starts your 14-day Studio trial on that machine — the clock starts on approval, not on signup, so installing early costs you nothing.
Your AI keys
NeoMotion runs on your own provider keys. There are no credits to buy, and we add no markup — the provider bills you directly at their price. Paste keys under Settings → API keys; they are stored locally on your machine and never sent to us.
- OpenAI — the director (research, script, storyboard) and transcription. English and Bahasa Indonesia.
- Replicate — image generation, including transparent-background cutouts.
- No key at all — the editor, the motion library and export still work. You lose the agent, not the app.
Core concepts
Project
A workspace on your disk: its manifest, its imported media, its scenes and its style. Nothing about it is uploaded.
Scene & timeline
A video is a sequence of scenes; each scene is layers on a timeline with real keyframes. Anything the agent builds arrives here, as layers you can select, retime, recolour and delete.
Motion presets
200+ presets the agent can cast into a scene — lower thirds, stat cards, callouts, transitions, chart moves. A cast preset is not a black box: expand it and every element inside becomes an editable layer.
Style
A look — colour, type, motion feel — held across every scene, so the agent doesn't drift from scene three onwards.
Briefing the agent
Give it a topic, a script or raw footage. It plans the production, shows you the plan, and waits for you before it fetches assets or renders anything.
- From a topic or script — the director researches, writes, storyboards, casts presets, and assembles the scenes.
- From raw footage — auto-edit transcribes your talking-head take, cuts it, and builds an editable timeline with captions and b-roll around it.
- When no preset fits — it authors the motion itself, and that custom motion is gated before it lands: schema validation, capability lint, and a determinism probe that checks the same input produces the same frames.
You approve the storyboard before the expensive half runs. Approving is also the cheapest place to redirect it — changing the plan costs nothing, changing a finished render costs everything.
Integrations & MCP
NeoMotion's whole production surface is exposed over MCP, so you can drive it from your own agent — Claude Code, Claude Desktop, Cursor, or anything else that speaks MCP over HTTP. Around sixty verbs, grouped the way a production runs: project, material, direction, authoring, style, output.
Connecting a client
- In NeoMotion: Settings → Control Surface. Toggle it on and copy the session token.
- Register the server with your MCP client using the block below.
- Brief it in plain language — the agent picks the verbs.
{
"mcpServers": {
"neomotion": {
"type": "http",
"url": "http://127.0.0.1:4399/mcp",
"headers": {
"Authorization": "Bearer <token from Settings → Control Surface>"
}
}
}
}Other integrations
- AI providers — OpenAI and Replicate, under your own account and your own key.
- Stock media — the agent can search and import footage and images rather than only generating them.
- Local media — import anything already on your disk.
Exporting
Rendering happens on your own hardware. It is never metered, never a credit, and never queued behind anyone else's job. Export at up to 4K, watermark-free on trial and on every paid plan.
Because the timeline is real, a change after export is a re-render of what you changed — not a fresh generation and not a new bill.
Licences & devices
- Trial — 14 days of full Studio, one device, one per account.
- Studio — 2 devices on monthly, yearly and lifetime. Founding-cohort licences get 3.
- Moving a device — deactivate it from your billing page and the seat is free again. Reinstalling on the same machine does not consume a second seat.
- Your licence key is a secret — anyone holding it can consume a seat. Terms are on the terms page.
Troubleshooting
“NeoMotion is damaged and can't be opened”
macOS quarantine on an unsigned build. Run the xattr command in install.
An AI feature errors immediately
Almost always a missing or exhausted provider key. Check Settings → API keys, then check your balance with that provider — their bill is not ours, so we cannot see it.
My MCP client can't connect
The control surface has to be toggled on in the app first, and the token regenerates when you toggle it. Confirm the port matches the block above and that the client is pointed at 127.0.0.1, not localhost resolving to IPv6.
Sign-in in the app does nothing
It opens your browser to approve the device. If no browser opened, copy the URL from the app and open it manually; if the approval succeeded but the app is still waiting, quit and reopen it.
Not written yet
Being explicit beats a page that looks complete and is not. Still to come:
- A per-verb MCP reference with request and response shapes.
- Authoring guides for custom components and editable motion presets.
- The style-pack workflow — reading a look off a reference end to end.
- Export settings in detail, and render performance tuning.
- Keyboard shortcuts, and a proper tour of the editor UI.
Need one of those before it is written? Ask on the support page — what gets asked for most gets written first.