RendGet started

Blog · November 17, 2026

Cursor Product Demo Video: Make One Without Leaving Your Editor

You can make a product demo video from Cursor by connecting it to a video agent over MCP. Add Rend as a custom remote MCP server with the URL https://rend.ai/api/mcp, sign in, then give Cursor's agent a screen recording or screenshots of your app plus a short brief. Cursor writes the script from your code and changelog; Rend voices it, zooms to the clicks, captions it and exports a video you can still edit on a timeline.

That combination suits developers who ship a feature on Friday and need the demo by Monday. Cursor already knows what the feature does, because it helped write it.

Connect Cursor to Rend

In Cursor's MCP settings, add a custom remote server with the URL https://rend.ai/api/mcp. Cursor opens a Rend page; sign in, review the request and approve it. No local render setup is needed, since rendering runs on Rend, and each project has its own Linux computer for heavier work.

If you'd rather drive the same work from a terminal, the commands for Claude Code and Codex are in MCP video editing.

What to capture before you prompt

The agent can generate shots, but a product demo should show your real product. People are buying the actual screen. Give it one of these:

  1. A screen recording of the flow, done once, slowly, without narration. Click deliberately and pause a beat after each result appears.
  2. A folder of screenshots in order, if the UI is still changing daily.
  3. Both, so the agent can use stills for the parts you didn't record.

Record at the size you'll publish. A 1440-pixel-wide window recorded on a 5K display produces tiny text that no zoom fully rescues. Close notification popups and use test data that looks like a real customer's, because "asdf asdf" in a demo reads as unfinished.

The brief, written by Cursor

Let Cursor read the code first. It will describe the feature more accurately than a marketing doc written before the build.

Read the diff on this branch and CHANGELOG.md. Write brief.md
for a 60-second product demo of the new bulk-invite feature:
who it's for, the one problem it solves, the 4 steps a user
takes, and one sentence on what's different from inviting
people one at a time. Plain language, no feature jargon.

Edit brief.md yourself. You know the customer's words better than the diff does.

The production prompt

Using Rend, create a 16:9, 30 fps project "Bulk invite demo".
Upload demo/recording.mov and demo/screens/.
Write a 60-second voiceover from brief.md at about 140 words
a minute, timed to the recording. Zoom into each click and
each result so text is readable on a phone. Design two voices
(calm product designer, not an announcer) and let me pick
from the first sentence. Then voice it, add a light music
bed ducked under the voice, word-timed captions in our brand
kit style, and an end card with the URL. Preview first.

The zoom instruction does more for a demo than anything else in that prompt. Viewers watch on phones and laptops in a browser tab, so a full 16:9 screen with 12-pixel menus is unreadable without the camera pushing in on the action.

Worked example: a bulk-invite feature in 60 seconds

Take a team-chat app shipping a bulk invite: paste a list of emails or upload a CSV, set roles, send. The raw recording is 2 minutes 50 seconds, because the CSV upload dialog takes a while and the narrator-free recording includes two wrong clicks.

Raw recordingWhat the edit does
0:00 to 0:22, navigating to settingsCut to 3 s: one click to Members
0:22 to 1:10, pasting emails, one typo fixedKeep the paste, cut the fix, zoom on the list
1:10 to 2:05, CSV dialog and loadingSpeed up the loading, zoom on the role dropdown
2:05 to 2:30, wrong click and backCut
2:30 to 2:50, "Invites sent" toast and the members listHold 3 s on the toast, then the full list

A script that fits about 60 seconds runs near 140 words. A good draft opens on the customer's problem in their words ("adding forty people used to mean forty invite emails"), names the steps as they appear, and ends on what changed for them, with no list of every option in the dialog.

Expect the first preview to need one or two notes, and keep them specific:

The zoom on the role dropdown cuts away before "Admin" is
selected; hold it half a second longer. And the line "with
just a few clicks" sounds like an ad; change it to "in one step".

Because the voice is on its own track, the second note revoices one line, and the first is a change to one zoom. Then cut it for other places:

Make a 9:16 version for social, 30 seconds, starting on the
pasted list of 40 emails. Captions large and in the safe zone.
And a silent 16:9 loop for the landing page with captions only.

Share it with the team before it ships

Ask the agent for a review link once there's a preview. Your PM and designer can draw on the frame at the exact moment ("the cursor covers the button here"), and Rend's agent reads every note and makes the fix. Versions stay on one link, so nobody asks which file is the latest. More on that loop in ad video review, which applies just as well to demos.

Tips that keep demos honest

Show the real product, not a generated mock. If a step is slow, speed it up visibly rather than hiding it; viewers notice when a three-second load becomes instant. Keep each demo to one feature. A two-minute tour of everything gets watched for about fifteen seconds of it. And reuse a brand kit so every release video has the same intro, caption look and voice without describing them again.

For demos beyond software release notes, product demo videos covers structure for physical products and sales calls, and app promo videos covers store-page and ad formats.

FAQ

Can Cursor make a video by itself?

Cursor's agent can write scripts and code, but it has no video editor or renderer. Connect it to a video agent such as Rend over MCP and it can produce an edited, narrated demo.

How do I add Rend to Cursor?

Add a custom remote MCP server in Cursor's settings with the URL https://rend.ai/api/mcp, then sign in on the Rend page that opens and approve the request.

Do I need to record my screen?

For a product demo, yes, or at least provide screenshots. The agent can generate other shots, but your demo should show your real product.

Can it zoom into the parts I click?

Yes. Ask for zooms on each click and result in the prompt, and adjust any zoom in the timeline afterwards.

Can I edit the video myself afterward?

Yes. The Studio link opens the same timeline in a browser, where you can trim, move clips or fix captions, then export again.

How much does it cost?

Editing is free on Rend. You pay when Rend renders or generates something, such as narration or the export. See Rend pricing.

Make the demo for your next release

Connect Cursor once, record the flow, and have the demo back as a preview the same afternoon: start a free Rend account.

Give Rend the job.

Editing is free. You pay only when Rend renders or generates something.