Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Beschreibung vom Entwickler (englisches Original)
Final Cut Pro MCP — 88 tools: FCPXML engine, live FCP control, media analysis, puppets.
Diese drei werden nie zu einer Punktzahl zusammengefasst: Meinungen, Messungen und Beliebtheit sind verschiedene Dinge.
Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.
Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.
FCP_MCP_OUTPUT_DIRDu brauchst
Welche App nutzt du?
Wähle oben deine App. Wir merken sie uns, damit der Button beim nächsten Mal „In … installieren“ anzeigt.
Öffne Claude Desktop → Settings → Developer → Edit Config und füge dies in claude_desktop_config.json ein
{
"mcpServers": {
"fcp": {
"command": "uvx",
"args": [
"fcp-mcp"
],
"env": {
"FCP_MCP_OUTPUT_DIR": "your-value"
}
}
}
}Führe das in deinem Terminal aus
claude mcp add fcp --env FCP_MCP_OUTPUT_DIR=your-value -- uvx fcp-mcpTrag die leeren Werte ein, bevor du ihn startest.
In .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen
{
"mcpServers": {
"fcp": {
"command": "uvx",
"args": [
"fcp-mcp"
],
"env": {
"FCP_MCP_OUTPUT_DIR": "your-value"
}
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
In .vscode/mcp.json in deinem Projekt einfügen
{
"servers": {
"fcp": {
"type": "stdio",
"command": "uvx",
"args": [
"fcp-mcp"
],
"env": {
"FCP_MCP_OUTPUT_DIR": "your-value"
}
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
Dieser Server läuft auf deinem Computer, und ChatGPT kann sich nur mit Servern im Internet verbinden. Wähle eine andere App.
Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.
FCP_MCP_OUTPUT_DIR envDiese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.
Läuft auf deinem Computer; die Tool-Liste erscheint nach der Installation in deiner KI-App.
Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 8. Nov. 2026
Der Registry-Name wurde mit dem GitHub-Konto dreliq9 bestätigt, dem das Repo gehört
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieser Server läuft auf deinem Computer; es gibt keinen Endpunkt im Internet
Läuft auf deinem Computer und nutzt stattdessen lokale Einstellungen
Läuft auf deinem Computer; Tool-Listen können wir nur von Endpunkten im Internet lesen
Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.
Er hat 1 von 1 zutreffenden Basischecks bestanden. Den Code haben wir nicht gelesen. Bevor du einen Schlüssel oder Token hinzufügst, sieh nach, welche Zugriffe der Server verlangt, und nutze einen Schlüssel, der nur die Berechtigungen hat, die du brauchst.
Die Registry nennt keinen erforderlichen Schlüssel, manche Server bitten dich aber bei der ersten Nutzung, dich anzumelden.
Er läuft auf deinem Computer. Deine KI-App startet ihn bei Bedarf, und die Daten laufen nicht über die Server des Entwicklers (außer der Server ruft selbst einen Onlinedienst auf).
Das GitHub-Repo wurde zuletzt – geändert, und die neueste Version (0.2.0) kam vor 7 Monaten in die Registry.
Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Außerdem brauchst du Python (uv) auf deinem Computer.
In derselben Kategorie: Spec Driven Development, Remote Desktop Commander, Cape Winelands Visit Planner
Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.
So liest du eine Karte:↓ Downloads pro Wochei★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Cape Winelands wine farm finder and day-route planner
Unverändert aus dem Repo des Entwicklers übernommen. PopNx MCP hat den Inhalt weder geprüft noch empfiehlt es ihn. HTML, Bilder und Skripte wurden entfernt. Links führen von dieser Website weg.
Trusted, local, human-approved Final Cut Pro workflows. fcp-mcp inspects, generates, and transactionally edits FCPXML, then optionally hands verified artifacts to Final Cut Pro. The default profile never performs direct live or offline mutation.
This development catalog adds three import-bridge tools to the v0.3.0 baseline across four profiles. It is a bounded FCPXML interchange and tested Final Cut Pro handoff surface—not a claim of complete autonomous Final Cut Pro control. The default workflow is inspect, prepare, review, hash approval, then commit.
You: "Find and repair flash frames in hero.fcpxml."
Claude → fcpxml_detect_flash_frames → fcpxml_workflow_prepare → review semantic diff + candidate hash → fcpxml_workflow_commit Result: the reviewed candidate is atomically committed with durable evidence
Start here:
fcp-mcp/
├── src/fcp_mcp/ │ ├── init.py │ ├── main.py # python -m fcp_mcp CLI │ ├── cli.py # serve, doctor, doctor --json, --version │ ├── config.py # immutable environment configuration │ ├── contracts.py # stable errors + structured diagnostics │ ├── diagnostics.py # non-mutating runtime readiness checks │ ├── observability.py # text/JSON transaction events │ ├── server.py # MCP v2 entry and profile-selected handlers │ ├── tool_metadata.py # MCP safety annotation presets │ ├── automation/ │ │ └── osascript.py # argv-isolated AppleScript/JXA runner │ ├── security/ │ │ └── paths.py # allowed-root and output policy │ ├── fcpxml/ │ │ ├── parser.py # FCPXML → Python object tree │ │ ├── writer.py # transactional XML mutation/writing │ │ ├── models.py # TimeValue, Timecode, Clip, Timeline, etc. │ │ ├── time_utils.py # rational-arithmetic timecode │ │ ├── analysis.py # pacing, flash frames, gaps, duplicates │ │ ├── validator.py # DTD-style structural validation │ │ ├── generator.py # programmatic project/timeline creation │ │ ├── puppet.py # character puppet system │ │ ├── diff.py # timeline A/B comparison │ │ └── transaction.py # validated atomic FCPXML commits │ ├── fcp_control/ # AppleScript bridge for live FCP control │ ├── media/ │ │ └── ffprobe.py # ffprobe wrapper for media analysis │ ├── pipeline/ # multi-step workflows │ ├── workflow/ # durable prepare, approval, commit, recovery │ └── utils/ │ ├── atomic_write.py # backup, replace, rollback │ ├── safe_xml.py # defusedxml hardening │ └── paths.py # trusted system path helpers ├── tests/ # complete unit + contract suite ├── scripts/ # docs, coverage, and wheel gates ├── docs/ │ ├── README.md # documentation map and status │ ├── research/ # dated research records │ └── reviews/ # release evidence and decisions ├── examples/ │ ├── quickstart.py # install verification │ └── GALLERY.md # workflow gallery with prompts ├── pyproject.toml ├── server.json # MCP Registry manifest ├── LLM_GUIDE.md # operational guide for agents ├── WORKFLOWS.md # production recipes ├── CHANGELOG.md ├── ROADMAP.md ├── CONTRIBUTING.md └── LICENSE
$PATH (for media_* tools): brew install ffmpegcompressor_* tools)Install the current published release from PyPI:
pipx install fcp-mcp
Or from source (for contributors):
git clone https://github.com/dreliq9/fcp-mcp.git
cd fcp-mcp python3 -m venv .venv source .venv/bin/activate pip install -e ".[dev]"
fcp-mcp --version
fcp-mcp doctor fcp-mcp doctor --json python examples/quickstart.py
doctor exits 0 when ready, 1 when offline service is usable but optional capabilities are degraded, and 2 when configuration blocks required runtime behavior. MCP clients can call the same structured surface through fcp_doctor.
claude mcp add-json fcp '{"type":"stdio","command":"fcp-mcp"}' --scope user
Or if you installed from source, point at your venv's Python:
claude mcp add-json fcp '{"type":"stdio","command":"/FULL/PATH/TO/.venv/bin/fcp-mcp"}' --scope user
Or edit ~/.claude.json directly:
{
"mcpServers": { "fcp": { "type": "stdio", "command": "fcp-mcp" } } }
Add the same config to your Claude Desktop config file:
~/Library/Application Support/Claude/claude_desktop_config.jsonclaude mcp list # from terminal
/mcp # inside Claude Code
Select a profile with FCP_MCP_PROFILE. The default workflow profile keeps the inspect → prepare → review → hash approval → commit sequence bounded and reviewable.
| Profile | Tools | Prompts | Resources | Purpose |
|---|---|---|---|---|
inspect | 30 | 2 | 0 | Offline inspection and diagnostics |
workflow (default) | 34 | 3 | 3 | Reviewable transactional FCPXML edits |
edit | 76 | 5 | 3 | Direct offline mutation, import preparation, and workflows |
full | 97 | 5 | 3 | All offline tools and opt-in live FCP, media, and Compressor tools |
The 97 tools include the youtube-mcp.materialized-clip-plan/v1 provenance adapter, fcpxml_generate_from_clip_plan, in edit and full only. Live FCP control remains independently disabled unless FCP_MCP_ENABLE_LIVE_CONTROL=1; choosing full does not grant that authority.
full)The full catalog combines 96 domain tools across 14 functional categories with fcp_doctor.
| Category | Count | What it does |
|---|---|---|
| inspect | 8 | Parse, list clips/markers/effects/roles, analyze pacing, timeline stats, A/B diff |
| qc | 10 | Flash frames, gaps, duplicates, media links, frame rates, audio levels, safe zones, duration, structural validation, aggregate QC report |
| edit | 12 | Markers, keywords, titles, audio, transitions, trim, split, delete, reorder, speed, role assign, reformat |
| heal | 3 | Fix flash frames, fill gaps, remove silence |
| batch | 4 | Markers, rename, role assign, apply transition across many clips |
| generate | 5 | New project/timeline, rough cuts, montages, and provenance-preserving clip-plan FCPXML |
| templates | 3 | List and save FCPXML templates; fcpxml_apply_template remains unsupported_contract in v0.3.0 |
| io | 5 | Import SRT/EDL, export EDL + DaVinci Resolve XML + Premiere FCP7 XMEML |
| live | 20 | AppleScript-backed library/events/projects, playback, menu/keyboard, share, and discovery |
| import bridge | 3 | Validated destination-bound XML preparation, one approved native request, and metadata reconciliation |
| puppet | 7 | Parametric character rigs in FCPXML with motion presets |
| media | 10 | ffprobe + ffmpeg info, loudness, silence, beats, scenes, thumbnails, and audio-to-MIDI |
| compressor | 2 | List Compressor settings and dispatch encode jobs |
| workflow | 4 | Prepare, inspect, hash-approve, commit, or cancel durable edit runs |
Most FCP MCPs pick a lane. DareDev256/fcpxml-mcp-server is FCPXML-only. elliotttate/finalcutpro-mcp is AppleScript/JXA-heavy with thin FCPXML. fcp-mcp does both — and adds media analysis (ffprobe) and a parametric puppet system on top. An agent can open a library, inspect the active timeline, patch the XML, re-import, trigger Share, and dispatch a Compressor job — end to end.
Time values are stored as fractions ("720/24s") and only collapsed to floats at display boundaries. Frame-accurate across 23.976 / 24 / 29.97 / 59.94 / drop-frame — no rounding drift when splitting, trimming, or concatenating.
All .fcpxml reads go through defusedxml via utils/safe_xml.py — XXE, entity expansion, and external entities are blocked by default. The parser enforces configured XML size and depth limits.
User paths are resolved beneath configured roots after symlink resolution. FCPXML writes are serialized to a secure temporary file beside the destination, structurally validated, backed up when replacing an existing destination, atomically committed, and validated again. The built-in validator checks the invariants it implements; it is not a complete Apple schema validator. Import into a disposable Final Cut Pro project is the authoritative compatibility gate for important outputs. On a release workstation with Final Cut Pro installed, preflight a candidate against the DTD matching its declared FCPXML version:
python scripts/apple_dtd_gate.py path/to/candidate.fcpxml
This gate reads the DTD from the installed Final Cut Pro application bundle; the project does not copy or redistribute Apple's schema. A passing DTD check does not replace the disposable-project import because Final Cut Pro also checks media and application-level semantics.
fcpxml_assign_role, fcpxml_batch_assign_roles, and their workflow operations assign audio roles. For an asset-clip, fcp-mcp writes Apple's audioRole attribute and continues to read legacy role values for compatibility.
The default profile exposes four workflow tools: fcpxml_workflow_prepare, fcpxml_workflow_status, fcpxml_workflow_commit, and fcpxml_workflow_cancel.
Prepare runs a fixed, bounded edit graph and stores the candidate, semantic diff, validation evidence, and event chain beneath the private FCP_MCP_STATE_DIR. It does not create or change the public destination. Review the returned summary and diff_uri, then pass the exact returned candidate_sha256 to commit as expected_candidate_sha256. Client approval is cryptographically bound to that candidate but is recorded as client_unverified_human; the server cannot independently prove that a human approved a chat message.
Three read-only templates expose durable evidence: fcp-workflow://runs/{run_id}, fcp-workflow://runs/{run_id}/events, and fcp-workflow://runs/{run_id}/diff. Candidate XML is deliberately private and is not exposed as a resource. Interrupted commits are assessed from durable evidence and can be explicitly reconciled with:
fcp-mcp workflow reconcile RUN_ID --json
This is a bounded workflow engine, not a generic graph runtime. It does not use MCP Tasks or run background autonomous agents.
Same timeline out to three targets:
fcpxml_export_resolve — DaVinci Resolve-flavored XML (v1.9)fcpxml_export_fcp7 — Premiere-compatible XMEML (FCP7 format)fcpxml_export_edl — flat EDL for color-grading and archive pipelinespuppet_* tools build animated character rigs entirely in FCPXML — no third-party motion templates required. Parts, keyframes, and presets (walk, talk, wave, multi-character compositions) emit XML for s
Nur der Anfang wird gezeigt; den Rest findest du im Repo