Can Claude Make Videos? Yes, With Orange's MCP Server

Yes. Claude can make videos when you connect it to Orange's MCP server, which is included with the Studio plan. Claude doesn't render anything itself; it calls Orange as a tool, Orange builds the video (script, visuals, narration, music, subtitles), and the finished file lands in your Orange account.

The same connection works from Claude Code and Cursor, and from any other client that speaks MCP.

#How it works

MCP (Model Context Protocol) is the standard that lets an AI assistant call outside tools. Orange runs as an MCP server, so once it's connected, video creation shows up in your assistant as a set of actions it can take: generate a script, start a render, check a job, pull the result.

You ask in plain English. The assistant turns that into tool calls, Orange does the work in the background (a render takes 5-8 minutes), and the assistant reports back with a link. The Use Orange from Claude feature page keeps the current tool list.

#Setup

1. Get on the Studio plan ($84/month billed yearly, or $129 monthly, for 1,300 credits). MCP and API access are part of it.
2. In Orange's settings, create an API key. Keys are scoped: a read key can check jobs and balances but never spend, while a write key can start renders.
3. Set a daily spend cap on the key. Spending stops at that limit no matter what the assistant asks for.
4. Add the Orange MCP server in your client: Claude.ai's connector settings, Claude Code, or Cursor. The connection uses a one-time approval.
5. Ask for a video.

#What you can ask for

The point of driving Orange from Claude is that requests stay conversational.

• A topic video. "Make a 30-second vertical video about cold brew ratios."
• A video from a URL. "Turn this blog post into a short." Orange reads the article and builds the script from its key points, the same URL to video flow the app uses.
• A script first. "Draft the script and show me before you render anything." You review the scenes, then approve the render.
• A batch. "Make one video for each of these five product pages." Jobs run in the background; ask for status whenever you like.

Each finished video is a download-ready vertical file with narration and burned-in subtitles. Orange doesn't post to social platforms for you; you download the file and post it.

#Guardrails

Handing an AI assistant the ability to spend credits deserves real controls, and this is where the MCP setup earns its keep.

#Dry runs

Any credit-spending request can run as an estimate first. A dry run returns the exact credit cost without spending anything, so the assistant can check the price before committing.

#Spend caps

Every key carries its own daily credit cap. A misbehaving script or an over-eager agent hits the cap and stops there.

#Audit log

Every call is recorded, down to which key ran which tool and whether it succeeded. If something looks off, revoke the key and the access dies with it.