Plans & Limits
The local CLI MCP server is free. When the server runs from
npx @devmotion/cli mcpon your machine (the default — see AI Coding Assistants), there’s no account, plan, or quota. Everything below applies to the cloud MCP server athttps://devmotion.app/mcp.
Cloud MCP access requires a Creator or Pro plan. All cloud MCP operations run under your DevMotion account — the same limits apply as in the web editor.
Plan Comparison
| Feature | Free | Creator ($9/mo) | Pro ($29/mo) |
|---|---|---|---|
| MCP Access | — | ✓ | ✓ |
| Rate limit | — | 30 req/min | 120 req/min |
| AI credits/month | — | 200 | 1000 |
| Cloud projects | — | 10 | Unlimited |
| Video exports/month | — | 50 | 200 |
| Max export res. | — | 1080p | 4k |
| Webhooks | — | ✓ | ✓ |
Video exports/month counts hosted exports across the web editor and REST API. The quota is shared.
How credits work
AI credits are shared across the web editor and MCP. They are consumed only by server-side AI features — things like caption generation and dubbing that require DevMotion’s servers to run an AI model on your behalf.
Regular MCP tool calls (create_project, upsert_layer, etc.) do not consume credits. When you use Claude, Cursor, or any other MCP client to build animations, the AI reasoning happens entirely on the client side — DevMotion only executes the resulting tool calls. Credits are only spent if the client invokes a server-side AI tool explicitly.
Account & quota
Sign in with the same DevMotion account you use in the browser. Projects created via MCP appear in your editor and count toward your plan’s project quota. If you hit the project limit,
create_projectwill return an error until you delete an existing project or upgrade your plan.