SpliceKit MCP
MCP server and plugin framework for Final Cut Pro: an agent reads the timeline, cuts, applies effects and exports the project
- 209 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- Injects a library into a re-signed copy of a commercial app and calls its private interfaces
- About 200 tools can cut, delete and rewrite the timeline, color and project export
- The author built crash reporting through Sentry into the patcher and the library
Install
- Works in
Manual install
./patcher/patch_fcp.shThe same thing from the terminal, from a repository clone.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Injects a library into a re-signed copy of a commercial app and calls its private interfaces
- About 200 tools can cut, delete and rewrite the timeline, color and project export
- The author built crash reporting through Sentry into the patcher and the library
This is third-party code. Review the repository files before installing.
What it does
SpliceKit injects its own dynamic library into a separate copy of Final Cut Pro and opens the app's internal objects from inside. Three parts run on top: a command palette on `Cmd+Shift+P`, an MCP server and a plugin framework. The patcher leaves the App Store original alone and puts the copy in `~/Applications/SpliceKit/`. The MCP server exposes about 200 tools across the main editing subsystems. An agent reads timeline state, inspects clips, blades, retimes, color-corrects, applies effects and starts a render. Traffic goes through a JSON-RPC bridge on `127.0.0.1:9876`, so the patched Final Cut Pro has to be running. Example plugins ship in the box: speech-transcript text editing, silence removal, captions in 13 styles, scene detection, beat-synced song cuts, batch export and URL import. You write your own plugins in Objective-C, C++, Swift, Lua or Python, and the repository carries an API reference meant to be read by a model.
Who it is for. Video editors on Mac who cut in Final Cut Pro and want an agent to take the routine, and developers who build add-ons for it.
Good fit when
- A 40-minute interview gets cut down to its best moments and the agent assembles the rough cut
- A podcast recording has many pauses: the tool finds silence by threshold, cuts it and adds captions
- A video is cut to music and Song Cut lays a folder of footage out on the beats of a track
- Every clip on the timeline exports as its own file with effects and color baked in
- A task lacks a button, panel or command and the agent writes it as a plugin from the API reference
Not a fit when
- Editing happens in Premiere Pro or DaVinci Resolve: SpliceKit works only with Final Cut Pro
- Final Cut Pro is not installed and the patcher needs its copy on this Mac
- Studio policy rules out modified copies of commercial software and re-signed apps
- A project ships right after a new Final Cut Pro release and the patch for it is not yet verified
Example request
Remove every pause longer than a second from this podcast, add captions and prepare the exportMCP
- Transport
- stdio
- Authentication
- not required
Limitations
- Works only on macOS and only with Final Cut Pro. The patcher copies the installed app and has no copy to fetch.
- A Final Cut Pro update can break compatibility, and the copy is patched again. Private interfaces of the app occasionally behave unpredictably; undo is `Cmd+Z`.
- The bridge on `127.0.0.1:9876` answers only while the patched Final Cut Pro is open.
- The author built crash reporting through Sentry into the patcher and the injected library. The last commit in the repository dates from August 2026.
How to disable. Delete the copy in `~/Applications/SpliceKit/` and the `splicekit` entry from your MCP client config. The original Final Cut Pro and its libraries were never changed, so nothing needs repairing.
FAQ
How do I connect SpliceKit to Claude Code?
Patch Final Cut Pro first, then run `make mcp-setup`: it creates the virtual environment `~/.venvs/splicekit-mcp`. Put that environment's Python and the path to `mcp/server.py` in the MCP config, then launch the Final Cut Pro copy. `make mcp-doctor` confirms that everything is wired.
Does SpliceKit modify my original Final Cut Pro?
No. The patcher works on a copy in `~/Applications/SpliceKit/`, and the format of libraries, projects and media stays the same. You can open the same library in the regular App Store Final Cut Pro.
What should I do after a Final Cut Pro update?
Run the patcher again to build a copy for the new version. The author treats re-patching as the normal route: an app update can break compatibility, while your data stays in place.
Do the command palette and transcription work without the cloud?
Yes, both run on the device. The palette uses Apple Intelligence, and Parakeet transcribes speech in 25 languages with speaker separation. Only the AI client you connect over MCP stays in the cloud.
Can an agent write a plugin for me?
Yes. Describe the task and give the agent the API reference from the repository: a plugin can add panels, buttons, palette commands and MCP tools. The bundled plugins serve as templates, and their sources sit in `Sources/`.
Discussion
No questions or reviews yet.
Related
MCP serversMCP server for Final Cut Pro: read and edit .fcpxml timelines, rough cuts, markers, transcripts and export to other editors
An MCP server with 59 tools for CapCut and OpenCut editing: tracks, clips, text, transitions and voiceover from Cursor and Codex.
The Diffusion Studio video editor plugin: two skills that let an agent compose videos and answer questions about footage
MCP for Adobe Premiere Pro: editing through an agent
MCP for Adobe Premiere Pro
A local MCP server that lets Claude, Cursor and Codex read a Premiere Pro project, edit the timeline and export the result
MCP server that drives local Adobe Premiere Pro projects from Claude, Codex and other MCP clients
PremierPro MCP Server: edit in Adobe Premiere Pro over MCP
PremierPro MCP Server
An open MCP server lets Claude and Cursor drive Premiere Pro: timeline, captions, effects, export, a rough cut from a script
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| SpliceKit (this card) | no | not required | 209 | |
| DaVinci Resolve MCP | no | not required | 4,088 | drives DaVinci Resolve through its official Scripting API, while here Final Cut Pro is edited through an injected library |
| MCP for Adobe Premiere Pro: editing through an agent | no | not required | 525 | connects Premiere Pro, while SpliceKit targets a different app and ships its own plugin framework |
README in short
The page is built on three pillars: a command palette, an MCP server and a plugin framework. It continues with bundled examples, a one-minute install through the patcher and a manual MCP setup with a check. A separate section covers safety, legality and bans from Apple, followed by a plugin-building guide with an injection diagram.