Make on-brand videos from Claude, ChatGPT, Cursor or Lovable

You already ask your assistant to write the email, draft the launch post and fix the landing page. The video is usually where the conversation stops and the tab-switching starts.

It doesn't have to. Reigniter runs an MCP server, so Claude, ChatGPT, Cursor, Lovable and other assistants can make the video in the same chat, on your brand kit and your credits. We make Reigniter, so this is a product note: what your assistant can do, how to connect it, and the limits.

What your assistant can do

Ask in plain words. The assistant picks the tool.

• Make an advert from a brief. "Make a 4-scene vertical ad for our oat-milk latte, warm and cosy, with my brand." It plans the scenes, then renders them through the same pipeline as the canvas, in 16:9, 9:16 for Reels, TikTok and Shorts, or 1:1.
• Make a presenter video from a script. "Make a presenter video that says: welcome to the team, here is how to book your first shift."
• Make a launch video for an app or product. Give it a name and a description; it writes the script for you and returns it with the video.
• Check a render. Videos render in the background. Ask "is it done?" and you get the progress, then the link.
• Check your account. Plan and credits remaining.

With branded: true the advert uses the brand kit on your account: your logo, your colours and your end card. That is the part a generic video tool cannot do from a chat. The assistant writes the brief; your brand system decides how it looks.

Connect it in two minutes

Every assistant needs the same address:

https://reigniter.ai/mcp

Claude (web and desktop). Settings → Connectors → Add custom connector. Name it Reigniter, paste the address, click Connect, sign in and click Allow.

ChatGPT. Settings → Connectors. Create a connector with the address and OAuth authentication. Depending on your ChatGPT plan, custom connectors may need developer mode.

Cursor and VS Code. Add the server by URL in your MCP config. Both open the Reigniter sign-in in your browser the first time.

Claude Code. One line, with an API key from your account:

claude mcp add --transport http reigniter https://reigniter.ai/mcp \  --header "Authorization: Bearer emp_YOUR_KEY"

Lovable. Open Connectors and choose the custom MCP card. Name it Reigniter, paste the address and keep OAuth, or choose bearer token and paste an API key. Then, while you build a landing page, ask Lovable for the launch video in the same chat.

Step-by-step screens for each are in the docs: Connect your assistant.

What a conversation looks like

A typical exchange, start to finish:

1. You: "Make a 4-scene vertical ad for our new trail shoe. Audience: weekend hikers. Warm, outdoorsy, honest. Use my brand."
2. The assistant calls create_ad with your brief, scene_count: 4, aspect: 9:16 and branded: true. Reigniter plans the scenes on your account and starts the render. The assistant tells you the job has started and lists the scenes it planned.
3. You carry on with the launch email in the same chat.
4. You: "Is the ad ready?" The assistant calls get_job_status and reports the progress, then the link once it is finished.
5. You: "Now a presenter version that says: our new trail shoe, built for long weekends." The assistant calls create_presenter_video with that script.

You never left the chat. Each finished video comes back as a link you can download, share or drop into the page you are building.

Briefs that work

The assistant writes the brief from what you tell it, so a little detail goes a long way:

• Say who it is for. "Weekend hikers" makes a different advert from "trail runners".
• Say the feeling. Warm, playful, premium, urgent. One or two words is enough.
• Give a product picture when you have one. Pass a public image link and the advert features your real product, not a lookalike.
• Ask for the size you need. 9:16 for Reels, TikTok and Shorts; 16:9 for YouTube and your website; 1:1 for feeds.

Your account, your rules

• Same prices as the studio. Tools that make a video spend your credits. Checking a render and reading your account are free. A render that fails refunds what it charged.
• Retries are charged once. Pass the same idempotency key and a retried call is not billed twice.
• You can switch it off. Every connected assistant shows on your API keys page, for example "Connector: Claude". Revoke it and the assistant loses access at once.
• It only sees your work. An assistant can check jobs on your own account, nothing else.

Where it fits with the rest of Reigniter

The canvas is still where you shape a campaign: pick the format, set every scene, swap a shot, edit in the timeline. MCP is for the moments you are already in a chat:

• A developer in Cursor ships a feature and asks for the release video.
• A founder in Claude drafts the launch and asks for the advert in three sizes.
• A builder in Lovable finishes the landing page and asks for the hero video.

The same work is open to your own code through the REST API and webhooks, which tell your systems when a video is ready.

The limits

• Agency plan. Connecting an assistant is part of the Agency plan, the same as the API. See pricing.
• Three ways to make a video today. Advert from a brief, presenter video from a script, launch video from a description. Interactive training, motion graphics and the editor are in the app, not the connector.
• Renders take minutes, not seconds. The assistant gets a job number straight away and checks back for the link.

Try it

Read the MCP overview, or start free and set up your brand kit first, so the first advert your assistant makes already looks like you.