Skip to content

Releases

v1.2.11

Choose a tag to compare

@hetpatel-11 hetpatel-11 released this 24 Oct 21:05

Fixes

  • import_media puts the file in binName when that bin exists, and fails when it does not. The previous call imported to the project root and still echoed the bin name.
  • move_clip_to_track removes the extra audio clip Premiere creates for the parked copy. The original linked audio stays.
  • ripple_delete removes the clip and its linked audio, closes the gap by the deleted duration, and reports ripple: true only after the later clips have moved.
  • add_adjustment_layer places an adjustment layer already in the project. It no longer imports a transparent PNG.
  • verify_premiere_connection reports readOnly from the project file. A stalled ExtendScript call is no longer hidden by a fresh panel heartbeat.
  • The CEP manifest names Premiere as the dispatch host. The macOS installer enables PlayerDebugMode for CSXS 9 through 15. Windows doctor fails when that value is a DWORD, or when the CEP log says this panel's signature was rejected.
  • detect_silence looks outside PATH for ffmpeg and, when it is missing, returns the install command for this machine.
  • export_frame keeps Premiere 26's timecode error. A later raw-seconds attempt no longer replaces it with "Illegal Parameter type".
npm install -g adobe-premiere-pro-mcp@1.2.11
premiere-pro-mcp --install-cep

Quit Premiere, reopen it, reload Window > Extensions > MCP Bridge, then restart the MCP client.

v1.2.10

Choose a tag to compare

@hetpatel-11 hetpatel-11 released this 24 Oct 19:19

Fixes

  • apply_lut stores a .cube or .3dl on Lumetri's Input LUT and selects it. The previous call wrote the path onto the numeric menu, swallowed the error, and still returned success. A missing file, or a path Premiere does not keep, is now a failure. The second Input LUT menu is left alone, because writing it clears the first. apply_effect uses the same path when Input LUT is a file path.

Telemetry

  • Clients send at most one launch per install per UTC day and at most one failed tool call per UTC day. Successful tool calls are not sent.
npm install -g adobe-premiere-pro-mcp@1.2.10
premiere-pro-mcp --install-cep

Reload Window > Extensions > MCP Bridge, then restart the MCP client.

v1.2.9

Choose a tag to compare

@hetpatel-11 hetpatel-11 released this 12 Oct 23:16

Fixes

  • export_sequence finds Adobe Media Encoder inside the Creative Cloud folder (/Applications/Adobe Media Encoder 2026/Adobe Media Encoder 2026.app). The 1.2.8 check only matched an .app directly under /Applications, so a normal macOS install always returned MEDIA_ENCODER_NOT_INSTALLED.
  • get_encoder_presets also looks in ~/Documents/Adobe/Adobe Media Encoder/<version>/Presets, which is where Media Encoder saves user presets.
npm install -g adobe-premiere-pro-mcp@1.2.9
premiere-pro-mcp --install-cep

Reload Window > Extensions > MCP Bridge, then restart the MCP client.

v1.2.8

Choose a tag to compare

@hetpatel-11 hetpatel-11 released this 02 Sep 20:43

Fixes

  • move_clip_to_track parks past the last clip on the destination, restores source in/out and timeline duration, slides into the occupancy-checked span, then lifts the source. The 1.2.6 fallback wrote overwriteClip at the destination using the project item's own duration, so a trimmed still could take out a neighbour the guard never saw.
  • The CEP update banner copies npm install -g adobe-premiere-pro-mcp@latest && premiere-pro-mcp --install-cep instead of spawning npm from Premiere.
  • --install-cep copies over the live extension instead of rm -rf.
npm install -g adobe-premiere-pro-mcp@1.2.8
premiere-pro-mcp --install-cep

Reload Window > Extensions > MCP Bridge, then restart the MCP client.

v1.2.7

Choose a tag to compare

@hetpatel-11 hetpatel-11 released this 31 Aug 22:37

Fixes

  • Premiere 26 QE cannot enumerate sequences (getSequenceAt throws; openInTimeline is missing). __qeSequenceFor now activates the requested sequence via openSequence / activeSequence so QE tools address that timeline, not whatever is on screen.
  • set_sequence_field_type writes numeric field type 0 / 1 / 2 instead of the string "No Fields".
  • set_metadata no longer coerces value to a number when a metadata key is present.
  • Expanded tools that need a clip or project item now require clipId / projectItemId in the schema.
  • add_transition matches add_transition_to_clip (applied_verified / accepted_unverified). Transition verification no longer exports FCP XML, which opened Translation Results dialogs.
  • apply_audio_effect rejects video-only clips with clip_has_no_audio.
  • import_fcp_xml warns that Premiere may still show Translation Results windows.

Removed

remove_effect, remove_effect_by_name, and remove_all_effects. Premiere 26 has no effect-removal API. Catalog is 283 tools.

Install

npm install -g adobe-premiere-pro-mcp@1.2.7
premiere-pro-mcp --install-cep

Reload the MCP Bridge CEP panel in Premiere after updating.

See CHANGELOG.md for details.

v1.2.6

Choose a tag to compare

@cursor cursor released this 31 Aug 19:42
2a2f8b9

Fixes

  • Prelude defines __ticksToSeconds / __secondsToTicks (Premiere Time objects and tick strings). list_sequences, get_active_sequence, set_playhead_position, create_sequence, work area, MOGRT import, and subclip tools no longer throw ReferenceError on a Connected panel.
  • replace_clip honors preserveEffects (default true): restore trim, enabled, Motion, and re-apply other effects.
  • move_clip_to_track restores source in/out, skips the source clip in occupancy checks, and refuses an occupied destination unless overwrite is true.
  • trim_clip duration writes clip.end and only then syncs source outPoint if the duration actually applied.
  • create_sequence_from_clips parses JSON-encoded id arrays (["000f4241"]) and comma-separated hex ids.
  • apply_effect matches localized parameter names (Exposure / Exposition) and coerces values. Effect removal tries components.remove / QE, then verifies the component is gone.
  • CEP panel auto-starts the bridge on load. verify_premiere_connection launches Premiere when it is installed.
  • Premiere launch paths are joined with posix/win32 keyed off process.platform so Windows CI stubs do not feed backslashes to open -a.

Tool search

tools/list now advertises a small always-on set: search_tools, get_tool_schema, invoke_tool, verify_premiere_connection, and list_sequences. Search the rest with BM25 query or regex pattern, then invoke_tool. Set PREMIERE_MCP_TOOLSET=full to list every tool (for hosts that natively defer MCP schemas).

Install

npm install -g adobe-premiere-pro-mcp@1.2.6
premiere-pro-mcp --install-cep

Reload the MCP Bridge CEP panel in Premiere after updating.

See CHANGELOG.md for details.

v1.2.5

Choose a tag to compare

@cursor cursor released this 30 Aug 21:39
887e32c

Fixes

  • Clip, effect, and transition names match localized Premiere labels (Motion/Movimento, Scale/Escala, Volume/Lautstärke, Gaussian Blur/Flou gaussien, Cross Dissolve, Crop, and the same family).
  • add_keyframe, set_clip_properties, and adjust_audio_levels resolve Opacity on Motion, Position X/Y as the Position array plus an axis, and do not pass arrays into scalar Scale.
  • Sequences resolve by GUID, name, or hex projectItem.nodeId. A timeline clip id can resolve to clip.projectItem.
  • export_frame converts seconds to HH:MM:SS:FF first and retries QE after opening the sequence.
  • apply_effect reuses a component that is already present. Transitions settle then resolve by localized name.
  • capture_frame writes to tmpdir()/premiere-mcp-frame-*.png when outputPath is omitted.

Install

npm install -g adobe-premiere-pro-mcp@1.2.5
premiere-pro-mcp --install-cep

Reload the MCP Bridge CEP panel in Premiere after updating.

See CHANGELOG.md for details.

v1.2.4

Choose a tag to compare

@hetpatel-11 hetpatel-11 released this 28 Aug 23:39

Fixes

  • Clip speed uses the real QE setSpeed signature (fixes Not Enough Parameters / Illegal Parameter type).
  • create_sequence_from_clips resolves hex timeline ids like 000f4242 across sequences.
  • add_text_overlay probes more MOGRT text fields, including JSON after a binary prefix.
  • Telemetry no longer stores quoted sequence names.

Update prompt

The MCP Bridge panel shows Update now / Later when a newer npm version is published. Later snoozes for 7 days. Opt out with PREMIERE_MCP_UPDATE_CHECK=0.

Install

npm install -g adobe-premiere-pro-mcp@1.2.4
premiere-pro-mcp --install-cep

Reload the MCP Bridge CEP panel in Premiere after updating.

See CHANGELOG.md for details.

v1.2.3

Choose a tag to compare

@hetpatel-11 hetpatel-11 released this 27 Aug 16:51

Fixes

  • Tool arguments accept snake_case and numeric strings; add_transition_to_clip accepts End / in / out and string durations.
  • speed_change sends QE percents (50, not 0.5).
  • create_sequence_from_clips accepts a single item or timeline clip id; keyframes match names without regard to case.

UX

  • If the MCP Bridge panel is not running, tools fail in about two seconds with retry: false instead of hanging for a minute. Reload the CEP panel after updating so it writes the heartbeat file.
  • add_text_overlay without a .mogrt fails immediately. Premiere cannot create titles from text alone.

Telemetry

Failed tool calls now send a short error code, the Zod field names that failed, and a path-stripped error template. Project names, media paths, and arguments are still not sent. See PRIVACY.md.

Install

npm install adobe-premiere-pro-mcp@1.2.3

Reload Window > Extensions > MCP Bridge in Premiere after updating.

v1.2.2

Choose a tag to compare

@hetpatel-11 hetpatel-11 released this 26 Aug 19:57

Telemetry

Anonymous usage telemetry is on by default: install id, tool names, success or failure, duration, OS, and version. Project names, media paths, arguments, and results are not sent.

Opt out from Share anonymous usage data in Window > Extensions > MCP Bridge (CEP), with PREMIERE_MCP_TELEMETRY=0, DO_NOT_TRACK=1, or "telemetry": false in ~/.premiere-mcp-bridge/config.json. See PRIVACY.md.

Install

npm install adobe-premiere-pro-mcp@1.2.2

Reload the MCP Bridge CEP panel in Premiere after updating so it is not running the old JavaScript.

See CHANGELOG.md for details.