{"slug": "how-do-you-make-a-rough-cut-from-a-script-with-claude-code", "title": "How do you make a rough cut from a script with Claude Code?", "summary": "Reelary, a local footage-indexing app, now exposes its search to AI agents over MCP, letting Claude Code assemble a rough cut from a script by calling a rough-cut tool that returns a best clip and two alternatives per visual line. The agent orders and selects clips while the Reelary app handles cutting, rendering and FCPXML/XML/EDL export linked to original camera files, and the same MCP server works in Claude Desktop, Cursor and Codex.", "body_md": "Give the agent the script, one visual line per shot, and let it call a local footage index for each line. It comes back with a best clip and two alternatives per line, saves the result as a project you can trim by hand, and exports an MP4 or an FCPXML that opens in Resolve, Premiere or Final Cut with your original files linked.\n\nA rough cut is mostly retrieval. For each beat of the script you go looking for a shot that fits, drop it on the timeline, and move on. The judgement is in the last ten percent; the first ninety is searching. That makes it a good job for an agent, as long as the agent has something faster than scrubbing to search with.\n\nThis example uses Claude Code and [Reelary](https://reelary.app/), which is our app. Reelary keeps a local index of your footage and exposes it to agents over MCP. One command installs the app, connects it to Claude Code and adds the skills:\n\n``` bash\n$ npx reelary\n```\n\nThen, in Claude Code: \"Index ~/Movies/Lisbon with Reelary.\" Indexing runs in the background on your machine; for a few hundred clips that is minutes, for a whole archive drive leave it overnight. You only do it once per folder.\n\nSearch works best on visual lines. \"We arrived on Tuesday\" describes nothing a camera saw; \"Tram climbing a narrow street\" does. If you paste prose, the rough-cut skill asks the agent to rewrite it into short visual beats and show them to you first. A 30-second travel opener might be:\n\n```\nSunrise over the rooftops.\nYellow tram climbing a narrow street.\nCoffee being poured at a cafe counter.\nWaves hitting the rocks below a lighthouse.\nCrowd on a viewpoint at sunset.\n```\n\n\"Rough cut this script from my footage, 9:16.\" The agent calls `reelary_rough_cut` with the five lines. For each line Reelary searches the index and returns the best clip and two alternatives, each with exact start and end times, capped at six seconds by default. The agent reads the draft back to you line by line, with the description of each pick, and flags any line that found nothing.\n\nThis is where the agent earns its place. You can say \"the tram shot is too dark, use the second one\" or \"make the whole thing punchier\" and it swaps alternatives or shortens shots without you opening anything.\n\nThe agent saves the draft as a Reelary project and can open it in the editor. Here you take over: play it through, nudge a trim, swap a shot from the clip bin, add music and captions. The agent is good at finding candidates; it has not watched the shots the way you will.\n\nTwo ways out, both available to the agent:\n\n`reelary_export_video`, rendered on your machine. Good for a social cut or a client preview.`reelary_export_nle`: FCPXML for Final Cut and Resolve, XML for Premiere, EDL as a fallback (Pro). The project points at your original camera files, so grading and sound start from full-quality media, not a render.\n\"Export it for DaVinci Resolve to ~/Desktop/lisbon.fcpxml\" is the whole instruction. Import it in Resolve and the five shots are on the timeline in order, linked to the files on your drive.\n\nReelary's own editor does the same thing without a chat: type the script, get a shot per line, trim, export. The agent version is worth it when the cut is one step in a bigger task (writing the script, making three aspect ratios, filing the export) or when you already live in Claude Code all day.\n\n**Does the agent edit the video itself?** No. The agent chooses and orders clips by calling tools; the cutting, rendering and FCPXML writing happen in the Reelary app on your machine. The agent never handles the video data.\n\n**Can I use Cursor or Codex instead of Claude Code?** Yes. The same MCP server and skills work in Claude Desktop, Cursor, Codex and other MCP clients. The prompts in this article work unchanged.\n\n**Do I need Pro for this?** Not for the rough cut or an MP4. Free exports are 720p, watermarked, up to 60 seconds and five a month. The FCPXML, XML and EDL export for Resolve, Premiere and Final Cut is part of Pro.\n\n**What if a line has no matching footage?** The draft lists it as an empty scene. The agent suggests a different wording, which often helps because search works by meaning; if you never shot it, no wording will find it.\n\nSetup and the full tool list: [Reelary for AI agents](https://reelary.app/agents). MCP server source: [github.com/reelary/cli](https://github.com/reelary/cli).\n\n*Originally published at [reelary.app](https://reelary.app/blog/rough-cut-with-claude-code).*", "url": "https://wpnews.pro/news/how-do-you-make-a-rough-cut-from-a-script-with-claude-code", "canonical_source": "https://dev.to/reelary/how-do-you-make-a-rough-cut-from-a-script-with-claude-code-100j", "published_at": "2026-10-25 01:08:17+00:00", "updated_at": "2026-10-25 01:12:22.967316+00:00", "lang": "en", "topics": ["ai-agents", "ai-tools", "agent-protocols", "developer-tools", "generative-ai"], "entities": ["Reelary", "Claude Code", "Claude Desktop", "Cursor", "Codex", "DaVinci Resolve", "Final Cut", "Premiere"], "also_reported_by": [], "alternates": {"html": "https://wpnews.pro/news/how-do-you-make-a-rough-cut-from-a-script-with-claude-code", "markdown": "https://wpnews.pro/news/how-do-you-make-a-rough-cut-from-a-script-with-claude-code.md", "text": "https://wpnews.pro/news/how-do-you-make-a-rough-cut-from-a-script-with-claude-code.txt", "jsonld": "https://wpnews.pro/news/how-do-you-make-a-rough-cut-from-a-script-with-claude-code.jsonld"}}