All docs

Manage runime from Claude, Codex & Cursor (MCP)

runime has an official remote MCP (Model Context Protocol) server. Connect a supported AI client once and it can do — in plain conversation — almost everything you can do in the app: create and edit films, manage characters, locations and assets, arrange the timeline, generate stills, video and audio, export, and read your balance. Everything runs on your account, under the same token balance and rules as the web app.

The server URL

Every client connects to the same endpoint:

https://runime.com/api/mcp

The first time a client connects it opens a runime page in your browser: sign in and approve the access. From then on the client is a "connected app" on your account.

Claude (claude.ai & Desktop)

Open Settings, go to Connectors, and choose "Add custom connector". Enter a name (runime) and the server URL above, then finish. Claude opens the runime sign-in + approval page, and the runime tools appear in your chats.

OpenAI Codex CLI

Add runime to your Codex config (~/.codex/config.toml):

[mcp_servers.runime] url = "https://runime.com/api/mcp"

Then authorise it once:

codex mcp login runime

Codex opens the browser approval and stores the credentials.

Cursor

Open Settings → MCP → Add, and enter the server URL. Cursor runs the browser sign-in the first time you use a runime tool.

Permissions you approve

On the approval screen you tick exactly which of four permissions to grant — untick anything you don't want the app to do:

  • Read — view your films, timeline, characters and balance.
  • Edit — create and edit films, scenes, entities and prompts.
  • Delete — remove shots, audio and entities.
  • Generate — run generation (this is what spends your tokens).

So you can, for example, connect a client read-only, or allow editing but not deleting. You can reconnect any time to change what's granted.

What you can ask it to do

Almost everything you can do in the editor. A few example prompts:

  • "Create a 30-second animated film about a lighthouse keeper."
  • "What's my token balance?"
  • "List my films and show the status of the last one."
  • "Reorder the shots so the sunrise comes first, then render the still for shot 2."
  • "Rewrite shot 3's video prompt to be more cinematic."
  • "Generate the dialogue for the opening scene, then export the film as a 1080p MP4."

Long jobs (running the pipeline, rendering a clip, exporting) run in the background — just ask it to check the film's status to see progress.

Good to know & troubleshooting

  • It runs under the same account rules. A waitlisted / not-yet-enabled account is blocked over MCP too. Creating a film and editing the timeline don't spend tokens; running generation, renders, audio, cover and MP4 super-resolution tiers do (a 720p MP4 is free if that exact film + tier was already produced).
  • "Not authorized" / tools stopped working — reconnect the runime integration. Access is short-lived and refreshes automatically, so a persistent failure means you should re-approve.
  • "This action needs the X permission" — you connected with a narrower set; reconnect and tick that permission.
  • "Not enough tokens" — top up at runime.com/billing. If your wallet is frozen (an open payment dispute), generation is blocked until it resolves.
  • Rate limits — generation is subject to the same rate and concurrency limits as the app; if you batch a lot at once, wait a moment and retry.
  • Security — only connect clients you trust; each connected app can act as you until you revoke it.
All docs