Use StarCut from ChatGPT, Claude, or Cursor with MCP
An external agent is useful when it drives the same StarCut project you can still open in the browser — not when it only returns a video file in chat.
The same studio, a different front door
StarCut can sit inside supported agent hosts through the StarCut plugin and MCP. ChatGPT, Claude, Cursor, and the other hosts on the plugin page each have their own install path. The destination is the same: a project the browser studio can open and keep editing.
That is the product check. After the external agent stops, you should be able to scrub the timeline, change a caption, or trim a shot in StarCut. A reply that only attaches an MP4 has skipped the studio.
Install for the host you actually use
Open the plugin page, pick the host, and copy the install prompt written for that host. Paste it where the host expects agent setup — a ChatGPT desktop task, a Claude Code session, a Cursor Agent chat, or the matching path for WorkBuddy or TRAE.
Do not invent a generic prompt. Host wiring differs. The plugin page keeps the install text and the short paste hint next to each host so you are not guessing which endpoint or skill name to use.
Walkthrough: ask from the host, verify in the studio
Use a brief you can verify by eye. A short promo is enough to tell whether the host edited a StarCut project or only described one.
- 01Install StarCut for your host from the plugin page. Confirm the host shows StarCut as available before you ask for a cut.
- 02From the host, request a concrete edit: length, master shot, captions, and score. Point it at a StarCut project rather than “make me a video file.”
- 03When the run finishes, open that project in the StarCut browser studio.
- 04Scrub the timeline. Change one thing by hand. If you cannot, the host did not land work in the studio.
- 05For the next pass, resume or continue against the same project. Avoid starting a second overlapping run while the first lease is still active.
Inside StarCut or from another host
You can also stay entirely in the StarCut client: the built-in agent calls tools where the project is open, and chat can resume over SSE or WebSocket. External hosts are another door into the same kind of project, not a parallel product that only exports files.
Pick the door that matches how you already work. The quality bar does not change. Editable timeline in a StarCut project — or it was not a StarCut edit.
If the host only hands back a file, it has not used StarCut. The project should still be editable in the studio.
Questions
Which hosts can use StarCut through MCP?
Supported hosts include ChatGPT, Claude, Cursor, WorkBuddy, TRAE, and others listed on the plugin page. Use that page for the host-specific install prompt.
How do I know the host used StarCut?
Open the project in the browser studio after the run. You should be able to edit the timeline, captions, and assets. A chat-only video file is not enough.
Do I still need the StarCut browser studio?
Yes, if you want to verify and finish the cut. External hosts drive the project; the studio is where you scrub and revise.
Open the studio
Cut in the browser, keep the timeline editable, and install the plugin when another agent host should drive the same project.