I tested Claude Final Cut Pro editing through an MCP server (FCPXML). The goal was a rough cut that removes dead air and failed takes, so I can skip the first 30 minutes of cutting and start with the real edit. This covers the workflow, three rounds of prompts, and what I would do differently.
The intro of the video was edited this way. I saw plenty of AI editing videos for DaVinci Resolve and Premiere, but not many for Final Cut Pro, which is my program of choice.
What AI is actually useful for here
Cutting silence does not need AI. You can do that by looking at the volume level. Cutting repeated takes, where I missed a line and tried again, is where Claude can help. The tricky part is a pause where I hold up a mouse or a pen and say nothing. A human knows that moment stays. An AI working only from audio does not.
This is not meant to replace editing. It gives you a better starting point, and you still refine pacing and timing yourself in Final Cut Pro.
The handoff: export FCPXML
There is one manual step. Export your timeline as XML from Final Cut Pro and place the file in the folder Claude works in. That file is the handoff. Claude edits it, and you get back a new FCPXML such as “Rough cut v1”. Double-click it, select your library, and the project opens in Final Cut Pro. No extra permission setup is needed.
You can also make edits yourself, export again, and send the file back to Claude so it continues from your version.
Round 1: almost no guidance
I told it to do a rough cut and nothing else. I know that leaving everything open is bad practice with AI, but I wanted to see what happens. It removed the silences quickly. It did not remove duplicate takes, because the transcript tool was not installed yet. It also cut the quiet moments where I was holding something up, since it could not tell from the audio that I was showing it. My verdict: okay, and fast.
Round 2: a more specific prompt
Next I asked it to remove unnecessary dead silence, remove pauses and retakes after mistakes, and keep anything relevant on screen even when I am not talking. The result was much better. The first 20 seconds were clean, retakes were deleted, and it kept the silent seconds where I picked up and showed the mouse. It said it only checked frames at the pauses instead of the whole video, which is a smart way to save effort. The transcribe function still was not working at this point.
Two minutes more spent on a prompt can improve the result a lot. You decide what you trust AI to take over and tell it exactly that. Token usage matters too, so more detail and more work means higher cost.
Round 3: master prompt in Claude Code
For the final version I ran it in Claude Code, pointed at the folder with the original untitled project, and gave it a long, detailed prompt. Claude Code mattered. I asked whether it had access to the transcript tool and, if not, to set it up. It found a workaround and fixed it. I do not know exactly what it did, but it worked. That is the difference compared to Cowork in my test, so I recommend Claude Code for this.
I also had it add sound effects, motion graphics, music, and natural-feeling zoom-ins. For motion graphics, give Claude a style guide. It makes the animations match your look instead of the generic output everyone gets. I also asked for the graphics on a layer above the video, so I can hide any I dislike. The zooms and animations use Final Cut Pro keyframes, so you can edit them by hand afterward.
The clip was only two or three minutes long. With over an hour of raw footage, expect more difficulty and more tokens.
What worked and what did not
I was blown away by how much trash it cut out. Timing was good and I did not edit most of it. The problems:
- One second try out of five on a retake was missed. I removed it myself.
- My voice was too quiet. That was my fault: I set up the microphone wrong and did not fix it before handing the project over.
- Some zoom-ins did not match when animations were on screen.
Fix the baseline audio level first, or tell Claude to do it. Next time I will also say: no zoom-ins while an animation is on screen. I plan to write a master document with exactly what Claude should and should not do, personalized to my style, since the MCP server is only the communication link.
Tip: fade every clip edge in Final Cut Pro
After the AI cuts, select all clips and press Option + T. It adds a short fade at the start and end of each clip, which reduces pops at the cuts. Then fine-tune only the clips that need it.
Setting up the FCPXML MCP server
In the video I show the setup with Claude desktop:
- Install uv.
- Open Claude’s settings, go to Developer, and click Edit Config.
- It points you to the config file in a folder. Open it, paste the server entry, and save.
- Reload the page. If the server does not show up, quit the app and open it again.
- Under Developer, FCPXML should now show as running.
{
"mcpServers": {
"fcpxml": {
"command": "uvx",
"args": ["fcp-mcp-server"],
"env": { "FCP_PROJECTS_DIR": "/Users/you/Movies" }
}
}I have a playlist on AI-assisted editing in Final Cut Pro with Claude. Links are in the video description.
This post may contain affiliate links. These links are marked with an * and I may earn a commission from qualifying purchases.