Does Final Cut Pro have an official MCP server?
Short answer
Apple ships no MCP server or agent API for Final Cut Pro: its release notes from 12.0 through 12.4 (September 29, 2026) mention none. Community tools fill the gap three ways: they write FCPXML files you import, push a project in with AppleScript, or run a patched, re-signed copy of the app that exposes its internals. We read their documentation and tested none of them.
No. We read Apple's Final Cut Pro release notes on October 20, 2026. They run from 12.0 (January 28, 2026) through 12.4 (September 29, 2026), and none of those entries mention an MCP server, an agent, or a scripting API. The headline features are Apple's own in-app tools: Transcript Search, Visual Search, Beat Detection and Generate Captions. This is as of the notes we read; Apple could add something later.
What Apple does document is a file format. FCPXML is the supported exchange format for moving projects and events in and out of Final Cut, and the release notes mention FCPXML updates. Apple is careful to say it describes certain, but not all, aspects of projects and events, and is not a substitute for a native project. Apple's Workflow Extensions are a different thing: a panel inside Final Cut for third-party apps, a user interface hook rather than an agent API.
There is one speculative thread. In September 2025, 9to5Mac reported that macOS 26.1 beta code showed groundwork for MCP inside App Intents. We found no shipped system support and no Final Cut announcement, so treat it as unknown.
If you want the general answer first, can Claude edit videos covers why an AI cannot cut video by itself. This page is the Final Cut deep dive; for the DaVinci Resolve equivalent, see Claude and DaVinci Resolve.
The three ways to connect Claude or Codex
Every Final Cut MCP server we found is community built. They differ mainly in what they touch on your Mac, which decides what each one cannot do. Licences, versions and dates below are from each repository on October 20, 2026. Tool counts are the projects' own claims; we installed and ran none of these tools and did not run Claude against Final Cut Pro.
FCPXML files
- What it touches
- Only files on disk. Final Cut does not need to be running
- Examples
- fcp-mcp-server (MIT, v0.26.0, October 9, 2026); fcp-mcp (MIT, v0.2.0, April 23, 2026); ButterCut
- What you give up
- You export and import by hand, and the agent cannot read the open timeline
AppleScript import
- What it touches
- The running app, through its scriptable import, plus a one-time macOS Automation prompt
- Examples
- Live mode in fcp-mcp-server; the AppleScript layer in fcp-mcp
- What you give up
- Import is scriptable, export is not, so a timeline still comes back through File, Export XML
Patched, re-signed copy
- What it touches
- A modified copy of Final Cut in ~/Applications with a bridge on localhost
- Examples
- SpliceKit (MIT, v3.3.9, August 29, 2026)
- What you give up
- You run a re-signed copy, need to re-patch after updates, and accept its built-in crash reporting
| Route | What it touches | Examples | What you give up |
|---|---|---|---|
| FCPXML files | Only files on disk. Final Cut does not need to be running | fcp-mcp-server (MIT, v0.26.0, October 9, 2026); fcp-mcp (MIT, v0.2.0, April 23, 2026); ButterCut | You export and import by hand, and the agent cannot read the open timeline |
| AppleScript import | The running app, through its scriptable import, plus a one-time macOS Automation prompt | Live mode in fcp-mcp-server; the AppleScript layer in fcp-mcp | Import is scriptable, export is not, so a timeline still comes back through File, Export XML |
| Patched, re-signed copy | A modified copy of Final Cut in ~/Applications with a bridge on localhost | SpliceKit (MIT, v3.3.9, August 29, 2026) | You run a re-signed copy, need to re-patch after updates, and accept its built-in crash reporting |
A practical way to read the table: the file route is the one you can undo by deleting an import, while the patched route changes what program you are running. That difference, more than the tool count, is what to weigh. A higher tool count only means more things the agent is allowed to try, and each project reports its own number, so none of these counts has been checked independently. Ask what happens when a step fails halfway: an FCPXML file can be discarded, while a change made inside a live app may need undoing by hand.
Repository activity also differs. fcp-mcp-server had a release in early October 2026, while fcp-mcp's latest tagged release dates from April. A quiet repository is not a broken one, but Final Cut changes its file details between versions, so a tool that is not kept current can lag behind your installed version.
Route one: FCPXML files
An MCP server on this route reads and writes FCPXML files, so the agent edits a description of a project rather than the app. Nothing is patched, and the README of fcp-mcp-server says the approach suits managed Macs. It claims 15 grouped tools and 102 operations, and its README gives a one-line Claude Code install. The fcp-mcp project claims 88 tools, split across an FCPXML engine, live control, and media analysis with ffprobe. ButterCut is a set of Claude Code skills that write FCPXML and other timeline formats. Its repository does not assert a licence, so check it before you rely on it.
The limit is the round trip. fcp-mcp-server's README says Final Cut has a fully scriptable import but no programmatic export, so before each round of AI edits you run File, Export XML yourself. The agent never sees what is on your screen right now.
Route two: AppleScript import
This is a layer on top of the file route rather than a separate product. The server writes an FCPXML project and pushes it into the running app using Apple's own open-document event, so the result appears without you dragging a file in. macOS asks once for Automation permission. It is a convenience for the import half only; getting the timeline back out of Final Cut is still your job.
Route three: a patched, re-signed copy
SpliceKit takes a different route. Its README says the patcher copies Final Cut Pro to ~/Applications/SpliceKit/, injects its library, re-signs the copy, and sets up an MCP server that talks to a bridge inside the patched app on 127.0.0.1:9876. That means the patched copy must be running. The project claims about 200 tools and live control of the timeline. The README states that the original app is never touched, that crash reporting is built in through Sentry, and that Final Cut updates can break compatibility, so you re-patch.
The author makes legal and Apple ID arguments for the approach. Those are the author's claims, we did not verify them, and nothing here is legal advice. The fcp-mcp-server README says this route does not suit managed or corporate Macs. Whichever route you use, decide what you will let an agent do first: what to allow an AI agent to do is a good starting list.
Can Claude edit in Final Cut Pro?
Short answer
Yes, with a community tool in the middle, and with limits that depend on the route. Claude or Codex can build a rough cut as an FCPXML file or drive a patched copy. It cannot be pointed at Final Cut and left alone, and none of this is supported by Apple.
From the documentation, the FCPXML routes suit work that a script can describe from a transcript or a media scan: rough assembly, markers, silence cuts, batch changes. The patched copy claims more, including live reads of the timeline. What the safe routes cannot do is judge footage by eye, read your open timeline without an export, or promise that a new Final Cut release will not change a file detail. A vendor, Jumper, says on its own page (October 8, 2026) that live timeline read and write is not available yet and that you export instead. Jumper sells a footage-search product, so take that as corroboration, not proof.
There is also the screen-control route: Claude's desktop control operating the Final Cut interface with the mouse. It needs no extra software but is slow, and it ties up the Mac while it runs. Footage search is a separate problem from editing. Apple's Visual Search and Transcript Search run inside the app, and we found no source saying an agent can call them.
Codex users follow the same routes; for the MCP setup see editing video with Codex. For the ffmpeg and Remotion alternatives that skip Final Cut entirely, see editing video with Claude Code, which also mentions the FCPXML tip.
What editors say
We read one r/finalcutpro thread, “Final Cut with Claude”, on October 20, 2026. These are individual experiences, not a benchmark, and usernames are dropped.
“Claude, which allows desktop access on my Mac which controls final cut and has helped me make basic cuts, selections etc (still in early stages - feels like early versions of humanoid robots trying to walk and fall down) and one downside is since its recording the screen to use the mouse to operate Final Cut, I am not able to any other tasks.”
“Depending on the video and what I need Claude code will use a few different tools; FFMPeg, whisper flow and a few other methods to analyze the audio and video then it will create and FCPXML file that has the clips and the cuts built-in.”
“Making really nice, niche tools through SpliceKit that are specific to my workflow is a game changer.”
One commenter also said the technology is not there yet for words-first content without a words-driven edit process. Treat that as an opinion about fit, which matches the transcript-based jobs above.
Which route should you use?
Work or client Mac, limited admin rights
- Route to try first
- FCPXML files
- Why
- Nothing is patched or re-signed
Comfortable in Terminal, want fewer manual imports
- Route to try first
- FCPXML with AppleScript import
- Why
- Imports appear in the app, with one permission prompt
Need the agent to see the live timeline
- Route to try first
- Patched copy (SpliceKit)
- Why
- Its claimed bridge is the only route that reads the open app, at the cost of running a re-signed copy
Just curious, want no new software
- Route to try first
- Screen control
- Why
- It is slow and locks the Mac, but needs no install
| Your situation | Route to try first | Why |
|---|---|---|
| Work or client Mac, limited admin rights | FCPXML files | Nothing is patched or re-signed |
| Comfortable in Terminal, want fewer manual imports | FCPXML with AppleScript import | Imports appear in the app, with one permission prompt |
| Need the agent to see the live timeline | Patched copy (SpliceKit) | Its claimed bridge is the only route that reads the open app, at the cost of running a re-signed copy |
| Just curious, want no new software | Screen control | It is slow and locks the Mac, but needs no install |
If you do not need Final Cut specifically
We make Rushilo, so weigh this section accordingly. Rushilo is a separate local editor for Mac and Windows with its own MCP server. It is not a Final Cut plugin or bridge, and it does not open Final Cut projects or FCPXML. If you work in Final Cut, use one of the routes above.
If the aim is only to have Claude or Codex edit video, an editor built for that avoids the export round trip. Rushilo starts from $19 once for 1, 3 or 5 computers, depending on the plan; Buy Rushilo has the details. Every other editor's options are in the video editing MCP servers directory. For Final Cut's own price next to the alternatives, see one-time purchase video editors.
Last checked and what to recheck
Last checked: October 20, 2026. Before relying on this page, recheck:
- Apple's release notes, for any new agent or scripting feature after 12.4.
- Each tool's latest release and licence, since all of these projects move quickly.
- The CommandPost MCP pull request, opened March 19, 2026 and unmerged when we looked.
- Your Claude plan, because Claude Code is not included in every plan. See can Claude edit videos for the plan check.
We installed none of SpliceKit, fcp-mcp-server, fcp-mcp, ButterCut or Jumper, so everything here comes from Apple pages, READMEs, the GitHub API and community posts.
Frequently asked questions
Does Final Cut Pro have an official MCP server?
No. Apple's Final Cut Pro release notes, from 12.0 on January 28, 2026 through 12.4 on September 29, 2026, list no MCP server, agent API or scripting upgrade. Final Cut's supported exchange format is FCPXML. Every MCP server for Final Cut Pro we found is community built and unofficial (checked October 20, 2026).
Can Claude edit in Final Cut Pro?
Yes, through a community tool, not on its own. Claude can write or edit FCPXML files that you import, push a project in with AppleScript, or drive a patched copy of Final Cut through SpliceKit. The safer routes need a manual export to hand a timeline back. We read the tools' documentation and did not test any of them.
What is the best way to use Claude or Codex with Final Cut Pro?
For most people the FCPXML route, such as fcp-mcp-server (MIT, v0.26.0 on October 9, 2026), because it needs no patching and its own table says it works on managed Macs. SpliceKit offers live control through about 200 tools, by its own count, but runs a re-signed copy and needs re-patching. We tested neither.
Is SpliceKit safe to use?
Its README says it copies Final Cut Pro, injects code, re-signs the copy and leaves the original untouched, with built-in crash reporting through Sentry and compatibility that can break after updates. We did not audit the code or test it, and its legal reassurances are the author's claims. Try it on a copy of a library, not client work.
What can an FCPXML MCP server not do?
It works on a file, not the open timeline. fcp-mcp-server's README says Final Cut has scriptable import but no programmatic export, so you choose File, Export XML before each round of AI edits. It also cannot watch your footage; for that you need a transcript or a footage-search tool. Apple notes FCPXML does not describe every project aspect.
Can Claude control Final Cut Pro by moving the mouse?
Claude's desktop control can operate the screen, and one r/finalcutpro editor reports basic cuts and selections that way, with the downside that the Mac is tied up while it runs. It is slower and less precise than an FCPXML route. Its one advantage is that it needs no extra software on top of Final Cut.
What is the best video editor for editing with Claude Code or Codex?
If you do not need Final Cut, Rushilo is built for it: a local Mac and Windows editor with its own MCP server and undoable edits. We make Rushilo, so weigh that. It does not open Final Cut Pro projects or FCPXML. If you work in Final Cut, use one of the FCPXML tools above.
Will Apple add MCP or AI agent support to Final Cut Pro?
Apple has announced nothing for Final Cut that we found. September 2025 reports said macOS 26.1 beta code showed groundwork for MCP support in App Intents, but we found no shipped system support or Final Cut announcement as of October 20, 2026. Treat it as unknown and recheck Apple's release notes.
Sources
- Apple: Final Cut Pro release notesReleases 12.0 (January 28, 2026) to 12.4 (September 29, 2026) list no MCP, agent or scripting feature, and mention FCPXML updates. Read October 20, 2026.
- Apple Developer: FCPXML referenceFCPXML as the documented exchange format; it describes certain but not all aspects of projects and events. Read October 20, 2026.
- Apple Developer: Workflow ExtensionsExtensions run in a floating window inside Final Cut Pro: a UI hook, not an agent API. Read October 20, 2026.
- elliotttate/SpliceKit on GitHubMIT, v3.3.9 released August 29, 2026, about 200 tools by its own claim; README on the patched copy, localhost bridge, Sentry crash reporting and re-patching. Read October 20, 2026.
- SpliceKit siteProduct page for the patched-copy route. Read October 20, 2026.
- DareDev256/fcp-mcp-server on GitHubMIT, v0.26.0 released October 9, 2026, 15 grouped tools and 102 operations by its own claim; README on scriptable import with no programmatic export. Read October 20, 2026.
- dreliq9/fcp-mcp on GitHubMIT, v0.2.0 released April 23, 2026, 88 tools by its own claim, with AppleScript-backed live control. Read October 20, 2026.
- fcp-mcp on PyPITool layers as the package describes them. Read October 20, 2026.
- barefootford/buttercut on GitHubClaude Code skills that write FCPXML and other timeline formats; the licence field is not asserted, so we state no licence. Read October 20, 2026.
- CommandPost pull request 3514An MCP proposal opened March 19, 2026, still open and unmerged. Read October 20, 2026.
- FCP Cafe news, April 2, 2026Community post on the SpliceKit predecessor; legal reasoning there is the author's claim. Read October 20, 2026.
- Jumper: AI agents and Final Cut ProVendor page dated October 8, 2026 saying live timeline read and write is not yet available. A vendor with a product to sell. Read October 20, 2026.
- 9to5Mac: macOS 26.1 beta 1 MCP integrationSeptember 2025 report of MCP groundwork in App Intents; background only. Read October 20, 2026.
Cite this page
Last verified: Oct 20, 2026
Patel, O. (2026, October 20). Final Cut Pro MCP: what works with Claude and Codex today. Rushilo. https://rushilo.com/blog/final-cut-pro-mcp

About the author
Founder, Rushilo
Om Patel is the founder of Rushilo, a desktop video editor driven by the user's own AI, and of BigIdeasDB, a research platform that reads real complaints and reviews to help founders validate products. He writes Rushilo's research articles with the same method: primary sources, dated numbers and the words real users write.