A
licenseB
qualityA
maintenanceThe most capable MCP server for Final Cut Pro — 88 tools covering FCPXML editing, live FCP control, parametric puppets, and media analysis.
88
51 PyPI
10
MIT
fcpxml-mcp-server
by DareDev256
Related Servers
Alternatives to fcpxml-mcp-server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceMCP server that enables AI to control Final Cut Pro on macOS, including reading libraries/projects, importing FCPXML, and creating title or storyboard projects.-
- AlicenseNot gradedqualityFmaintenanceComprehensive MCP server for DaVinci Resolve with 295+ tools to control projects, timelines, editing, color grading, rendering, and more via natural language.117 PyPI6MIT
- FlicenseCqualityDmaintenanceEnables comprehensive remote control and automation of Final Cut Pro through 99 tools covering timeline editing, project management, and AI-powered features. It facilitates complex workflows including media organization, color grading, and FCPXML generation using AppleScript and JXA automation.10012-
- AlicenseAqualityBmaintenanceGive any MCP client a real video editor — 32 typed tools over ffmpeg, Whisper and MediaPipe, plus an optional local UI with a drag-and-drop timeline.38MIT
- AlicenseAqualityCmaintenanceAn MCP server that assembles CapCut International projects by reading and writing local project files, adding captions, subtitles, overlays, and more so editors start with a mostly-done timeline. It includes tools for inspecting projects, restyling captions, importing subtitles, and rendering alpha-channel overlays via Remotion.81MIT
TDQS
A3.8/5.0
Scored across 13 tools
Disambiguation4/5
The thirteen tools map onto distinct workflow stages—inspect, diagnose, edit, deliver, preview, watch, etc.—so an agent can usually pick the right one by intent. Minor overlap exists between inspect and diagnose (both read-only analysis) and between scenes_split and edit.split_clip, but the descriptions separate general understanding from problem-finding and scene-boundary work.
Naming Consistency4/5
All tool names follow a consistent single-lowercase-word style, which is predictable after seeing a few. The main deviation is grammatical: most are verbs (inspect, edit, mark, watch, find) while transcript, index, and scenes are nouns, and the actual operations live inside as snake_case actions.
Tool Count5/5
With 13 tools, the server sits comfortably in the well-scoped range, and each tool represents a distinct phase of FCP XML editing: analysis, diagnostics, editing, marking, generation, transcription, delivery, preview, round-trip, indexing, scene detection, organization, and search. None feels redundant; the breadth is justified by the size of the domain.
Completeness5/5
The surface is unusually complete for the domain, covering inspection, diagnosis, editing, generation, metadata logging, transcription, export, preview, watch-loop integration, caching, scene detection, organization, and natural-language search. Read-only tools have write counterparts, output paths are verifiable, and there are no obvious dead-end workflows.
Maintenance
ActivityActive
ResponsivenessWithin a week