@synthetic-ai/premiere-mcp 1.1.8

package/CHANGELOG.md

@@ -0,0 +1,100 @@
+# Changelog
+
+## [v1.1.8] — macOS default preset paths
+
+`create_sequence`, `create_sequence_from_clip`, and `get_default_sequence_presets`
+only ever probed Windows install paths for the default `.sqpreset` (and, for
+`create_sequence`, only a single hardcoded PP 2026 path with no probing at
+all). All three now check both Windows and macOS locations across PP
+2026/2025/2024/CC 2023, matching the pattern `export_sequence` already used
+for AME presets. When nothing is found, the tools return a clear error
+asking for an explicit `preset_path` instead of silently using a
+definitely-wrong fallback. Found via a site-wide macOS-compatibility audit
+of every Synthetic product (2026-09-23) — this was the one confirmed gap in
+an otherwise genuinely cross-platform architecture (no launch step to
+break, unlike ae-mcp). Unverified on real macOS hardware — no Mac available
+to test against yet.
+
+## [v1.1.7] — License enforcement
+
+The MCP server itself (all 437 tools) never actually validated
+`PREMIERE_PRO_MCP_LICENSE` — the CEP panel had a license field for its own
+auto-update, but the server side was wide open. Added the same
+`checkLicense()` gate ae-mcp and photoshop-mcp already have: every tool
+except `ping` / `get_version_info` now requires a valid license, validated
+against `https://synthetic.com.ar/api/v1/license/validate` and cached for an
+hour.
+
+---
+
+All notable changes to this MCP server. Every fix below was discovered via
+**static audit + live runtime testing against Premiere Pro 2026.2.2 on
+Spanish-localized Windows**.
+
+The audit started at **31/100 sellability score** (22% green tools) and
+finished at **~78/100** (~75% green) after the rounds below.
+
+---
+
+## [v1.2.0] — PP 2026 compatibility + locale resilience
+
+### Round 6 — Live runtime validation
+- `6f20892` capture_frame: honest error for PP 2026 host limitation
+- `8152021` bridge: sanitize NaN and Infinity to null
+- `a74ce33` Round 5: 8 more fixes from full smoke test (137 tools tested)
+- `45fdaba` track-targeting: locale-resilient set_clip_position/scale/rotation
+- `f9589cb` premiere.jsx: locale-resilient fadeIn/fadeOut/crossFadeClips
+- `29e941d` graceful fallbacks for setSpeed signature + track volume
+- `0533162` Live-test fixes: setSpeed signature, locale prop names, audio clip volume
+- `084ef49` Live-test fixes: set_clip_opacity locale, color_correct Lumetri name
+
+### Round 5 — Bridge JSON sanitization
+- `f3d83d7` Fix bridge JSON: ExtendScript ignores replacer; sanitize tree pre-stringify
+
+### Round 4 — premiere.jsx loading (single highest-impact fix)
+- `366f325` Fix premiere.jsx SyntaxError that broke ALL JSX helpers
+  - **1-char fix, ~30+ tools unblocked**
+  - `premiere.jsx` (22k lines) had `package:` as bare property name at line
+    22006. ExtendScript is strict ES3 where `package` is reserved → entire
+    file fails to parse → every JSX-helper-backed tool returns
+    `ReferenceError: <fn> is not a function`. Quoting fixes everything.
+- `b12a0d8` Round 4: bridge JSON-parse failure + locale-resilient transition lookup
+
+### Round 3 — Concrete code bugs from re-audit
+- `21bf821` Round 3 part 2: fix remaining 9 files
+- `e4534d5` Round 3: fix 32 concrete code bugs from re-audit
+  - ticks/Time correctness (markers, source-monitor, scripting, clipboard, audio)
+  - property-vs-method (media.check_offline_media)
+  - QE-only methods routed correctly (timeline.move_clip/speed_change, transitions)
+  - missing `app.enableQE()` guards
+  - nested Lumetri prop lookup via `__findProp`
+
+### Round 2 — Locale-resilient helpers
+- `bdaebaa` Round 2: guard QE multicam enumeration and proxy detach
+- `48d3648` Round 2 part 2: fix remaining 8 files
+- `2b718b3` Round 2 part 1: locale-resilient helpers + fix 13 tool files
+  - Added `__findIntrinsic(clip, key)` with matchName-first lookup
+  - Added `__findComponent`, `__findProp`, `__readMaybe`, `__findTransition`
+
+### Round 1 — Property-vs-method bugs
+- `ffe6931` Fix 21 red tools: property-vs-method bugs, missing APIs, stub handlers
+- `35ecbfa` Fix PP 2026 compatibility: sequence creation, tracks, audio, effects, export
+
+---
+
+## Validated tool inventory
+
+### ✅ 66 tools confirmed working in runtime (PP 2026.2.2 es-ES)
+Inspection, transform, audio/video FX, timeline editing, selection, markers,
+sequence ops, project/bins, captions, source monitor, track management,
+metadata, scripting, export. Full list in [README.md](README.md).
+
+### ⚠️ Honest errors (PP 2026 host limitations, not bugs)
+- `set_track_volume`, `speed_change`, `capture_frame`, Lumetri-when-not-applied
+- All return clear errors with the recommended UI workaround
+
+### Validated against
+- Premiere Pro 2026.2.2 on Windows
+- Spanish (es-ES) locale — names like "Opacidad", "Movimiento", "Escala",
+  "Posición", "Disolvencia cruzada" all handled
+- 15-item test project with multi-track timeline, transitions, fades, Lumetri

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 Premiere Pro MCP Contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,242 @@
+# Premiere Pro MCP
+
+**Control Adobe Premiere Pro with natural language through Claude (or any MCP-compatible LLM).**
+
+[![Premiere Pro 2026](https://img.shields.io/badge/Premiere%20Pro-2026-blueviolet)](https://www.adobe.com/products/premiere.html)
+[![MCP](https://img.shields.io/badge/MCP-compatible-green)](https://modelcontextprotocol.io)
+[![License](https://img.shields.io/badge/license-MIT-blue)](LICENSE)
+
+---
+
+## What it does
+
+```
+You: "Apply a cinematic look to all clips on V1, ducking the music
+      when there's voice, and export to YouTube 1080p."
+
+Claude: ✓ Applied Lumetri (-15K temperature, +10 contrast) to 4 clips
+        ✓ Added voiceover ducking on A2 (-12dB during A1 voice)
+        ✓ Queued H.264 1080p export to ~/Videos/final.mp4
+```
+
+437 tools exposed via MCP to drive Premiere Pro 2026 from any LLM agent.
+Tested in runtime against PP 2026.2.2 on Spanish-localized Windows install.
+
+---
+
+## Highlights
+
+- **Locale-resilient**: works on Premiere Pro in Spanish, German, French, etc.
+  (most competitors hardcode English component names and silently fail)
+- **Honest errors**: when a Premiere host API genuinely doesn't expose
+  something (PP 2026 has known limitations), you get a clear error with
+  the recommended workaround — not a silent no-op
+- **Battle-tested**: 137 tools validated in live runtime against PP 2026 with
+  detailed bug fixes (see [CHANGELOG.md](CHANGELOG.md))
+- **AI-first**: built for LLM-driven workflows. Pair it with Whisper for
+  speech-to-text, ComfyUI for thumbnails, FFmpeg for analysis — chain MCPs
+
+---
+
+## Quick start
+
+### 1. Install the CEP plugin
+
+Copy `cep-plugin/` to your Adobe CEP extensions folder:
+
+- **Windows**: `%APPDATA%\Adobe\CEP\extensions\MCPBridgeCEP\`
+- **macOS**: `~/Library/Application Support/Adobe/CEP/extensions/MCPBridgeCEP/`
+
+Enable CEP debugging:
+```powershell
+# Windows
+reg add HKCU\Software\Adobe\CSXS.11 /v PlayerDebugMode /t REG_SZ /d 1 /f
+```
+
+### 2. Build the MCP server
+
+```bash
+cd premiere-pro-mcp
+npm install
+npm run build
+```
+
+### 3. Register with Claude Desktop
+
+Add to `%APPDATA%\Claude\claude_desktop_config.json`:
+
+```json
+{
+  "mcpServers": {
+    "premiere-pro": {
+      "command": "node",
+      "args": ["C:/path/to/premiere-pro-mcp/dist/index.js"]
+    }
+  }
+}
+```
+
+### 4. Open Premiere Pro
+
+- Launch Premiere Pro 2026
+- `Window > Extensions > MCPBridgeCEP` (the bridge panel)
+- Click "Start Bridge"
+
+### 5. Talk to Claude
+
+```
+"Show me the active sequence structure."
+"Add a 1-second fade-in to the audio clip on A2."
+"Apply Cross Dissolve at every cut on V1, 0.5 seconds each."
+```
+
+---
+
+## What works (validated runtime, PP 2026 es-ES)
+
+### Project & Inspection
+- Full project / sequence / clip overviews
+- Bins, markers, metadata (XMP), color labels
+- Effect properties with all values, keyframes, source media details
+- Find/search project items, list sequences
+
+### Timeline editing
+- Add/remove/move/duplicate clips, split, trim
+- Set in/out points, playhead, work area
+- Selection by name/range/color, invert, deselect
+- Enable/disable clips, link/unlink
+
+### Transform & Motion
+- Position, scale, rotation, opacity (locale-resilient)
+- Anchor point, blend mode
+- Position/scale keyframes via `add_keyframe`
+
+### Color
+- Lumetri full parameter control: exposure, contrast, highlights/shadows,
+  whites/blacks, temperature/tint, saturation, vibrance, sharpen, vignette,
+  faded film
+- LUTs apply
+- Copy/paste color grade across clips
+- ⚠️ See limitations: applying Lumetri *for the first time* requires manual UI
+
+### Audio
+- Per-clip volume, fade in/out (locale-resilient)
+- Volume/panning keyframes
+- Audio FX pipeline: Compressor, EQ, De-Esser, De-Hum, De-Reverb, Limiter,
+  Noise Reduction
+- Voiceover ducking
+- Normalize, detect clipping
+
+### Effects & Transitions
+- 60+ video effects (Gaussian/Directional Blur, Sharpen, Warp Stabilizer,
+  Noise Reduction, Mirror, Spherize, Corner Pin, Lens Distortion, etc.)
+- Transitions with locale-aware name lookup (Cross Dissolve works on any
+  language install)
+- Batch apply across cuts
+
+### Captions
+- Import SRT files as caption tracks
+- Pipeline integration: Whisper-transcribe → SRT → MCP creates captions
+
+### Export
+- Single sequence + batch export via Adobe Media Encoder
+- Match Source presets, YouTube/Vimeo/Twitter/Facebook presets
+- Encode arbitrary files via AME
+- AAF, OMF, FCPXML export
+
+### Multicam
+- Create multicam sequences, switch angles, flatten
+
+### Markers
+- Add/update/delete on sequence or clip
+- Color labels, comments, in/out range
+- Import/export CSV
+
+---
+
+## Known limitations (PP 2026 host)
+
+These are not bugs in this MCP — they're verified limitations of Premiere Pro
+2026's ExtendScript/QE-DOM surface. Each tool returns a clear actionable error
+with the recommended workaround.
+
+| Feature | Status | Workaround |
+|---------|--------|------------|
+| `capture_frame` programmatic | ❌ `qeSeq.exportFramePNG` reports success but never writes file | UI: File > Export > Media > Single Frame |
+| `set_track_volume` | ❌ Audio track DOM no longer exposes `.components` or `.volume`; QE has no `setVolume` | Use `add_audio_keyframes` per-clip, or Audio Track Mixer |
+| `speed_change` programmatic | ❌ `qeClip.setSpeed` signature changed in PP 2026 (rejects all known forms) | UI: Clip > Speed/Duration, or change duration with `trim_clip` |
+| Apply Lumetri for the first time | ❌ `addVideoEffect` reports success but doesn't add component | Apply Lumetri manually once; afterwards all 28 setters work perfectly |
+| LUFS integrated measurement | ❌ Not scriptable | Export and measure with ffmpeg-loudnorm |
+| Native PP Speech-to-Text | ❌ Adobe AI STT not exposed | Use Whisper + `create_caption_track` (works great) |
+| Adobe Libraries MOGRT | ❌ Adobe Libraries not scriptable | Use local `.mogrt` files via `import_mogrt` |
+| Dynamic Link with AE | ❌ `import_ae_comps` not implemented | Render from AE and import as video |
+| Async export completion | ⚠️ AME runs async, no callback | Poll `get_render_queue_status` |
+
+---
+
+## Architecture
+
+```
+┌─────────────┐         ┌──────────────┐         ┌─────────────┐
+│   Claude    │         │   Node.js    │         │  Premiere   │
+│  (or LLM)   │◄───────►│  MCP server  │◄───────►│   Pro CEP   │
+└─────────────┘  stdio  └──────────────┘  files  │   plugin    │
+                                                  │   (panel)   │
+                                                  └─────────────┘
+                                                        │
+                                                        ▼
+                                                  ┌──────────────┐
+                                                  │ ExtendScript │
+                                                  │  DOM + QE    │
+                                                  └──────────────┘
+```
+
+The bridge automatically prepends locale-resilient helpers to every script:
+
+```javascript
+__findIntrinsic(clip, "motion" | "opacity" | "volume" | "lumetri" | "timeRemap")
+// tries matchName ("AE.ADBE Motion") first — locale-INDEPENDENT —
+// then localized displayName ("Movimiento", "Bewegung", "Mouvement", etc.)
+
+__findProp(component, ["Position", "Posición", "Position", "Position"])
+// also descends one level into nested groups (needed for Lumetri's
+// grouped parameters like Exposure inside Basic Correction)
+
+__readMaybe(obj, "isMuted", false)
+// reads members that are property in some PP versions, method in others
+
+__findTransition(name, "video")
+// resolves transition names across locales:
+// "Cross Dissolve" matches "Disolvencia cruzada" / "Fondu enchaîné"
+```
+
+---
+
+## Development
+
+```bash
+npm run dev      # Watch mode
+npm run build    # Build dist/
+npx tsc --noEmit # Type-check only
+```
+
+When adding a tool, prefer:
+- `__findIntrinsic` / `__findComponent` over hardcoded `displayName === "Motion"`
+- `__readMaybe` for any `isSomething()` / `isSomething` property
+- Pass `.ticks` strings (not Time objects) to `insertClip`/`setInPoint`/etc.
+
+---
+
+## Credits
+
+Built on top of work from
+[`AdobePremiereProMCP`](https://github.com/bdenney99/AdobePremiereProMCP)
+with extensive fixes for PP 2026 compatibility, locale resilience, and
+runtime-validated behavior. See [CHANGELOG.md](CHANGELOG.md) for the full
+fix log.
+
+---
+
+## License
+
+MIT

package/cep-plugin/.debug

@@ -0,0 +1,8 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<ExtensionList>
+  <Extension Id="com.mcp.premiere.bridge.panel">
+    <HostList>
+      <Host Name="PPRO" Port="8088"/>
+    </HostList>
+  </Extension>
+</ExtensionList>

package/cep-plugin/CSInterface.js

@@ -0,0 +1,92 @@
+/**************************************************************************************************
+ * ADOBE SYSTEMS INCORPORATED
+ * Copyright 2013 Adobe Systems Incorporated
+ * All Rights Reserved.
+ *
+ * NOTICE:  Adobe permits you to use, modify, and distribute this file in accordance with the
+ * terms of the Adobe license agreement accompanying it.  If you have received this file from a
+ * source other than Adobe, then your use, modification, or distribution of it requires the prior
+ * written permission of Adobe.
+ *
+ * CSInterface.js - v12.0.0 (minimal shim for MCP Bridge)
+ * Download the full version from: https://github.com/nicscott9/CSInterface
+ **************************************************************************************************/
+
+/**
+ * CSInterface class for Adobe CEP extensions.
+ * This is a minimal implementation. For production use, download the full
+ * CSInterface.js from Adobe's GitHub repository.
+ */
+function CSInterface() {}
+
+/**
+ * Evaluates an ExtendScript in the host application.
+ * @param {string} script - The ExtendScript to evaluate.
+ * @param {function} callback - Callback with the result string.
+ */
+CSInterface.prototype.evalScript = function (script, callback) {
+  if (typeof __adobe_cep__ !== "undefined") {
+    // CEP 9+ requires the callback to be passed directly to __adobe_cep__.evalScript.
+    // Calling it without a callback causes the result to be silently discarded,
+    // making every command return null/undefined.
+    __adobe_cep__.evalScript(script, callback || function () {});
+  } else {
+    // Running outside CEP (for testing)
+    console.warn("[CSInterface] Not running in CEP environment");
+    if (callback) callback("EvalScript Error: Not in CEP environment");
+  }
+};
+
+/**
+ * Get the host environment.
+ */
+CSInterface.prototype.getHostEnvironment = function () {
+  if (typeof __adobe_cep__ !== "undefined") {
+    try {
+      return JSON.parse(__adobe_cep__.getHostEnvironment());
+    } catch (e) {
+      return null;
+    }
+  }
+  return null;
+};
+
+/**
+ * Get the system path.
+ * @param {string} pathType - The path type constant.
+ */
+CSInterface.prototype.getSystemPath = function (pathType) {
+  if (typeof __adobe_cep__ !== "undefined") {
+    return __adobe_cep__.getSystemPath(pathType);
+  }
+  return "";
+};
+
+// System path constants
+CSInterface.prototype.EXTENSION_ID = "extensionId";
+
+/** SystemPath constants — main.js reads these as SystemPath.EXTENSION, but
+ *  this shim never declared the global. Older CEP hosts happened to inject
+ *  a SystemPath global on their own, so cs.getSystemPath(SystemPath.EXTENSION)
+ *  worked by accident; hosts that stop doing that throw "SystemPath is not
+ *  defined" and halt init() before premiere.jsx loads or license/update code
+ *  runs. Same bug class already hit and fixed in the sibling AE MCP panel
+ *  (cep-plugin/CSInterface.js, v2.4.2). Values match Adobe's canonical
+ *  CSInterface.js — must be strings, not indexes: the native
+ *  __adobe_cep__.getSystemPath() doesn't throw on an unrecognized pathType,
+ *  it silently returns the literal string "invalidParam", which then fails
+ *  downstream in a confusing way (e.g. fs.mkdirSync() trying to create a
+ *  folder actually named "invalidParam"). */
+var SystemPath = {
+  USER_DATA: "userData",
+  COMMON_FILES: "commonFiles",
+  MY_DOCUMENTS: "myDocuments",
+  APPLICATION: "application",
+  EXTENSION: "extension",
+  EXTENSION_DATA: "extensionData",
+  HOST_APPLICATION: "hostApplication"
+};
+
+// Note: This is a minimal shim. For the full CSInterface.js, download from:
+// https://github.com/nicscott9/CSInterface
+// and replace this file with the appropriate version for your CEP target.

package/cep-plugin/CSXS/manifest.xml

@@ -0,0 +1,49 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<ExtensionManifest Version="7.0" ExtensionBundleId="com.mcp.premiere.bridge" ExtensionBundleVersion="1.1.6" ExtensionBundleName="MCP Bridge">
+  <ExtensionList>
+    <Extension Id="com.mcp.premiere.bridge.panel" Version="1.1.6"/>
+  </ExtensionList>
+  <ExecutionEnvironment>
+    <HostList>
+      <Host Name="PPRO" Version="[14.0,99.9]"/>
+    </HostList>
+    <LocaleList>
+      <Locale Code="All"/>
+    </LocaleList>
+    <RequiredRuntimeList>
+      <RequiredRuntime Name="CSXS" Version="9.0"/>
+    </RequiredRuntimeList>
+  </ExecutionEnvironment>
+  <DispatchInfoList>
+    <Extension Id="com.mcp.premiere.bridge.panel">
+      <DispatchInfo>
+        <Resources>
+          <MainPath>./index.html</MainPath>
+          <ScriptPath>./host.jsx</ScriptPath>
+          <CEFCommandLine>
+            <Parameter>--allow-file-access-from-files</Parameter>
+            <Parameter>--enable-nodejs</Parameter>
+          </CEFCommandLine>
+        </Resources>
+        <Lifecycle>
+          <AutoVisible>true</AutoVisible>
+        </Lifecycle>
+        <UI>
+          <Type>Panel</Type>
+          <Menu>Synthetic Premiere MCP</Menu>
+          <Geometry>
+            <Size>
+              <Height>300</Height>
+              <Width>400</Width>
+            </Size>
+            <MinSize>
+              <Height>200</Height>
+              <Width>300</Width>
+            </MinSize>
+          </Geometry>
+          <Icons/>
+        </UI>
+      </DispatchInfo>
+    </Extension>
+  </DispatchInfoList>
+</ExtensionManifest>

package/cep-plugin/host.jsx

@@ -0,0 +1,7 @@
+// Host-side ExtendScript (runs in Premiere Pro's ExtendScript engine)
+// This file can contain ExtendScript helper functions that are always available.
+// The main execution happens dynamically via CSInterface.evalScript() from main.js.
+
+function mcpBridgePing() {
+  return "pong";
+}