fcpxml-mcp-server
Related Servers
Alternatives to fcpxml-mcp-server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceEnables an MCP client like Claude to read, edit, and generate real Final Cut Pro timelines from exported FCPXML, covering cut and flash-frame detection, silence and gap removal, markers, keyframes, speed ramps, transcript-based editing, cross-NLE export, and pushing the result into a running Final Cut Pro. Every write is journaled with its sha256 so changes can be undone and unreviewed cuts refused.-
- FlicenseNot gradedqualityAmaintenanceEnables Claude and other MCP clients to read, edit, and generate real Final Cut Pro timelines from exported FCPXML: cut detection, silence and flash-frame removal, markers from transcripts and beats, role assignment, rough cuts, keyframes, speed ramps, and cross-NLE export, with every write journaled, hash-verified, and undoable. It can also push a generated timeline straight into a running Final Cut Pro via Apple's Open Document event, so edits can be reviewed and re-imported without manual XML handling.-
- AlicenseBqualityCmaintenanceThe most capable MCP server for Final Cut Pro — 88 tools covering FCPXML editing, live FCP control, parametric puppets, and media analysis.88183 PyPI12MIT
- FlicenseNot gradedqualityAmaintenanceEnables Claude and other MCP clients to read, edit, and generate real Final Cut Pro timelines from FCPXML, including cut detection, markers, roles, silence removal, transcript-based editing, cross-NLE export, and pushing changes into a running Final Cut Pro. Every write is journaled and undoable, with validation and safety checks for reliable timeline edits.-
- AlicenseNot gradedqualityDmaintenanceMCP server that enables AI to control Final Cut Pro on macOS, including reading libraries/projects, importing FCPXML, and creating title or storyboard projects.MIT
- AlicenseBqualityCmaintenanceEnables Claude or any MCP client to build, validate, import, and read Final Cut Pro XML timelines, and to control the macOS app through menus, shortcuts, dialogs, exports, and screenshots, all locally.19MIT
TDQS
Scored across 15 tools
The 15 tools are grouped into clearly labeled high-level purposes (inspect, diagnose, edit, mark, generate, etc.), but each tool bundles many overlapping sub-actions under vague verbs. The flat tool names 'inspect' and 'diagnose' overlap heavily (both read-only analysis), and 'generate' vs 'gen' (generative fill) are confusingly adjacent, as are 'scenes' vs 'index' vs 'find' which all touch indexing/scene detection.
Names are consistent in style (all lowercase single-word verb/noun groupings) but inconsistent in convention — some are plain verbs (inspect, edit, mark), some are nouns (transcript, scenes), and one is an abbreviation (gen) that nearly duplicates generate. The sub-action names inside descriptions are snake_case but the top-level tool names are not, mixing conventions.
15 tools is at the upper edge of reasonable, but this is a mega-server where only 15 names actually hide well over a hundred sub-actions, making the surface feel deceptively compact while functionally enormous. Each named tool is a mini-server rather than a task, which strains the 'one tool = one clear action' model.
The surface is remarkably complete for a Final Cut Pro XML workflow — inspection, diagnostics, editing, marking, generation, transcription, delivery, preview, watching, indexing, scene detection, organization, search, viewing, and generative fill are all covered. Lifecycle coverage from read through edit, export, round-trip and search is thorough with few obvious gaps.