Feature

Orange in Claude, Cursor & ChatGPT

Orange runs as an MCP server, so the AI assistant you already use can make videos through it. Ask it to turn a blog post into a short, kick off a script, or check a render, and Orange does the work in the background. Connect once with a key, and it shows up as a tool.

Try it free

How it works

1

Connect Orange as a tool

Add Orange to Claude, Claude Code, Cursor, or any MCP client with a one-time key. It appears as a set of actions your assistant can call.

2

Ask in plain language

"Make a 30-second video from this article." "Write me three script options." Your assistant calls Orange and reports back.

3

Pick up the result

Finished videos and scripts land in your Orange account, with links right in the chat.

Why it matters

Create without switching tabs

Stay in the assistant you already work in. Orange handles script, voice, visuals, music, and assembly behind the scenes.

Built for automation

Generate in batches, turn a list of topics into a posting queue, or wire Orange into your own workflow.

The full toolset

Create from a topic or a URL, generate and review scripts, edit scenes, re-render, and pull publish-ready captions, all by asking.

Your account, your credits

Runs against your plan, with per-key spend you can see and revoke any time.

Orange exposes 23 tools over MCP, and 14 of them can spend credits

Orange runs as an MCP server, so an assistant that speaks the protocol gets Orange as a set of callable tools rather than a website to describe. There are 23 of them. Nine are read-only, covering things like checking a balance or fetching a finished job. The other 14 mutate or spend: creating a video from a topic or a URL, generating and editing scripts, re-rendering, cancelling. A key minted read-only is refused at the write set rather than trusted to behave, so an agent you want watching your account without spending from it is a scope decision instead of a promise. Every call lands in an audit log with the tool name, the outcome, and the job it touched. MCP and API access are part of the Studio plan.

Every spending tool takes a dry run and an idempotency key first

Handing an autonomous agent a credit balance fails in one predictable way: a retry loop drains it. Orange's MCP surface is built against that rather than around it. Any tool that spends accepts dryRun, which reports the exact cost and whether the call would clear your live balance, charging nothing, so an agent can price a whole batch before committing to any of it. Every spender also accepts an idempotencyKey, and a repeat call carrying the same key replays the original job id instead of starting a second render. That claim is held for 24 hours. Each key additionally carries its own daily credit cap, 200 by default, enforced separately from your plan's monthly credits, and revoking a key stops it on the next call. None of this relies on the agent behaving well.

Hand your assistant a link and it drives the same URL to video flow the app runs

Repurposing is the shape this gets used in most. You give the assistant an article link, it calls Orange's create-from-URL tool, and Orange scrapes the page, distills it to key points, and renders a vertical short. It is the same URL to video flow the web app runs, calling the same job-creation code, which is why a video made from Claude appears in your Orange account beside one made in the browser. The async tools hand back a durable job id in under 2 seconds, so an assistant can fire a batch of 10 and poll rather than hold a connection open through a render. Script generation over MCP spends no credits at all, so an agent can draft and review several competing angles on the same article before any one of them costs you anything.

How the URL to video flow works

Questions? Answers.

Everything you need to know.

Model Context Protocol. It's the standard that lets AI assistants like Claude use outside tools. Orange is one of those tools.
Anything that speaks MCP, including Claude, Claude Code, Cursor, and Claude.ai on the web. Connection uses a secure one-time approval.
MCP and API access are part of Studio.
Yes. Access uses scoped keys you control, every call is logged, and you can revoke a key whenever you want.

Your next video is
one sentence away

Describe your video idea and get a finished clip in minutes. Free to start, no credit card required.

Make your first video, free