fcp-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fcp_statusA | Check Final Cut Pro, permissions and helpers. Call this first when something fails. |
| fcp_launchA | Open Final Cut Pro (or bring it forward) and wait until it responds. |
| fcp_list_librariesA | List open libraries with their events and projects. |
| fcp_get_projectA | Get a project's sequence details (duration, start, frame rate, timecode format). To see clips, titles and markers inside it, open it in the timeline and use fcp_export_xml. |
| media_probeB | Inspect media files: duration, resolution, frame rate, timecode, audio. |
| fcpxml_build_timelineA | Create a new FCP project from media files, titles and markers, as FCPXML, and import it. Example primary: [{"path": "/clips/a.mov", "source_in": 2, "duration": 5}, {"text": "Chapter 2", "duration": 3}, {"path": "/clips/b.mov"}]. Example connected: [{"path": "/music.mp3", "at": 0, "lane": -1}]. |
| fcpxml_importA | Import an FCPXML file or bundle into Final Cut Pro. Projects are added; nothing is overwritten. |
| fcpxml_readB | Summarise an FCPXML: projects, every clip/title/gap with timeline position and lane, markers, media. |
| fcpxml_add_markersB | Add markers, to-dos or chapter markers to a project in an FCPXML file and save a new file. |
| fcpxml_validateA | Check an FCPXML file against the DTD bundled with the installed Final Cut Pro. |
| fcp_menu_listA | List Final Cut Pro menu items with enabled state and keyboard shortcuts. |
| fcp_menu_clickB | Click a Final Cut Pro menu item. Acts on the current selection, like a person clicking it. |
| fcp_press_keysB | Press a keyboard shortcut in Final Cut Pro (it is brought to the front first). |
| fcp_ui_snapshotB | Describe the UI of the open dialog or front window (buttons, fields, values) as a tree. |
| fcp_click_buttonB | Click a button in Final Cut Pro's open dialog (or front window). |
| fcp_save_dialogB | Fill in Final Cut Pro's open save dialog with a folder and file name, then confirm. |
| fcp_export_xmlA | Export the open timeline (or browser selection) as FCPXML via File > Export XML, then read it. |
| fcp_share_exportB | Render the open timeline via File > Share using that destination's current settings. Rendering runs in the background in FCP; this returns once the export has started. |
| fcp_screenshotB | Take a screenshot of Final Cut Pro so you can see the viewer, timeline or a dialog. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 19 tools
Most tools target clearly different actions/resources: live app control, FCPXML file operations, media inspection, and UI automation. There is some potential confusion between fcpxml_read, fcp_get_project, and fcp_export_xml, and between menu/button/keyboard UI tools, but descriptions clarify the boundaries well enough.
Names use recognizable domain prefixes (fcp_, fcpxml_, media_) which aids grouping, but the conventions are mixed: some are verb_noun (fcp_list_libraries), others are noun_first (fcp_menu_list, fcp_ui_snapshot, fcp_screenshot, fcp_status). It remains readable but not a single predictable pattern.
At 19 tools the set is somewhat heavy, but the scope is broad—live FCP control, FCPXML authoring/validation, media probing, UI automation, and export—so most tools earn their place. It is slightly over the typical 3–15 range but not excessive for the domain.
The surface covers creation via fcpxml_build_timeline, reading/exporting, validation, markers, import, and app/UI control. However, there are notable gaps: no explicit delete/remove operations, no direct editing of existing timeline clips, and limited library/event/project management beyond listing and getting.