A
licenseB
qualityC
maintenanceThe most capable MCP server for Final Cut Pro — 88 tools covering FCPXML editing, live FCP control, parametric puppets, and media analysis.
88
739 PyPI
10
MIT
fcpxml-mcp-server
by DareDev256
Related Servers
Alternatives to fcpxml-mcp-server
No user-submitted related servers found.
Related Servers
- 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
- AlicenseNot gradedqualityFmaintenanceComprehensive MCP server for DaVinci Resolve with 295+ tools to control projects, timelines, editing, color grading, rendering, and more via natural language.114 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.10013-
- 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.5/5.0
Scored across 15 tools
Disambiguation3/5
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.
Naming Consistency3/5
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.
Tool Count3/5
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.
Completeness5/5
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.
Maintenance
ActivityActive
ResponsivenessWithin a week