fcpxml-mcp-server
An MCP (Model Context Protocol) server that parses, analyzes, validates, and batch-edits Final Cut Pro FCPXML timelines using 53 MCP tools (e.g., QC checks like flash frames/gaps/duplicates, marker/chapter operations, rough-cut/montage generation, diffing timelines, subtitle/beat marker import, and exporting to Resolve FCPXML v1.9 or FCP7 XMEML v5).
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Provided excerpts indicate hardened XML handling (defusedxml/XXE/entity-bomb protection) and output/path safety controls (path traversal blocked, null bytes rejected, symlinks resolved, size limits, restricted writes to anchor directories). However, auth details for the MCP server are not described; since it is local, the main risk is file-system access context rather than network auth.
⚡ Reliability
Best When
You need batch, deterministic, frame-accurate edits and analysis of FCPXML timelines that can be reviewed/confirmed via exported XML back into Final Cut Pro.
Avoid When
You require interactive WYSIWYG editing or live preview; or you have strict constraints that prevent local file-system access or XML write-back workflows.
Use Cases
- • Timeline health checks and QC (flash frames, gaps, duplicates)
- • Bulk marker/chapter generation from transcripts or SRT/VTT
- • Extraction of structured data from FCPXML (EDL/CSV, stats, pacing)
- • Batch editing operations (trim/reorder/split/add transitions/speed changes)
- • Automated rough cuts, montages, and A/B roll generation from tagged clips
- • Diffing two timelines to understand what changed
- • Reformatting timelines (aspect ratio) and removing silence candidates
- • Cross-NLE export (DaVinci Resolve, Premiere/Avid formats)
- • Beat sync and snapping edits to beats
Not For
- • Real-time editing inside Final Cut Pro
- • Creative visual work requiring frame-by-frame subjective judgment (color, framing, motion aesthetics)
- • Applications needing a hosted/cloud service with stable network APIs (it’s a local MCP server)
Interface
Authentication
The provided materials describe local execution (server.py with env like FCP_PROJECTS_DIR) rather than a remote authenticated API. No auth/scopes configuration is documented in the excerpts.
Pricing
No pricing information provided; appears to be a local open-source tool.
Agent Metadata
Known Gotchas
- ⚠ This is a local MCP server; the Claude Desktop configuration must correctly set env/paths (e.g., FCP_PROJECTS_DIR) and run server.py/uv from the right directory.
- ⚠ Operations involve exporting/modifying XML round-trips; ensure you understand destructive vs non-destructive behavior (README claims original file is never touched, but specific edge cases not fully verifiable from excerpts).
- ⚠ Non-visual workflow: creative/subjective decisions still require user review in Final Cut Pro.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for fcpxml-mcp-server.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-30.