Reported issues for MCP for Adobe Premiere Pro

Pod holds 23 of 79 GitHub reports that passed its relevance review. This can include external user reports, maintainer-confirmed bugs, and concrete feature gaps. Treat them as evidence to inspect, not a count of distinct defects.

Back to MCP for Adobe Premiere Pro.

Most discussed

4 issues found building a real edit: setSpeed broken, no native transitions, opacity keyframes silently ignored at render, AME preset scan misses installed presets

Environment

premiere-pro-mcp installed via npm install -g premiere-pro-mcp (CEP bridge, --install-cep)
Adobe Premiere Pro 2026 (26.3.2), macOS
Node 22.22.0
UI language: pt-BR

Summary

While building a real ~60s vertical edit (12 clips, color grade, transitions, animated text) I hit four separate issues. Filing them together since they were all found in the same session with full repro steps. Happy to share the .prproj / logs if useful.

1. All three "change clip…

Read the thread · 2026-08-20 · closed · external user · 5 comments

[Bug] set_sequence_audio_settings and set_sequence_frame_rate write inverted units into Time-typed fields

Description

Both tools accept an intuitive rate value (Hz for audio sample rate, fps for frame rate) but write it into a Premiere Time object field that actually expects a duration in seconds — the reciprocal of what's passed. This silently corrupts sequence settings with no error thrown either way. set_sequence_frame_rate is the more serious of the two: its own input validation (rejecting values outside 1–240) then blocks supplying the reciprocal needed to recover, so a sequence's frame…

Read the thread · 2026-08-28 · closed · external user · 3 comments

[Bug] Project-panel delete tools and sequence-nesting tools do not perform the operation they report

Description

Two related clusters of tools report success without performing the claimed structural change:

delete_project_item, delete_multiple_project_items, delete_sequence, and delete_bin all report a deleted count of 0 or otherwise fail to remove the target project item/bin/sequence.
nest_clips and create_subsequence both genuinely create a new sequence containing the selected clip(s), but neither one replaces the original clip(s) on the timeline with a reference to that new…

Read the thread · 2026-08-28 · closed · external user · 3 comments

[Tool]: Four tools fail with "Not Enough Parameters" when called with all documented arguments

Tool name

auto_reframe_sequence (reproduces identically on set_anti_alias_quality, set_sequence_pixel_aspect_ratio, clear_sequence_in_out, create_bars_and_tone — filing together since all five share the identical error signature and likely one root cause)

Premiere Pro MCP version

1.13.0

Premiere Pro version

26.3.2 build 2

Reported backend

Not sure

**(Backend note: the error is a generic argument-marshaling failure — Illegal Parameter type — rather than a…

Read the thread · 2026-08-28 · closed · external user · 3 comments

[Connection]: UXP Bridge: "Manifest entry not found" for ws://127.0.0.1:7777 on Premiere Pro 26.3.2

Operating system

Windows

Premiere Pro version

26.3.2

AI client

Claude Desktop

Installation route

Claude Desktop bundle plus CEP connector

Sanitized connection state

Windows 11 Adobe Premiere Pro 26.3.2 (build 2) Premiere Pro MCP 1.11.1 Claude Desktop

CEP connection: working normally. MCP server: working normally. Active Premiere project and sequence: detected successfully through CEP.

UXP WebSocket listener: 127.0.0.1:7777

Test-NetConnection confirmed:…

Read the thread · 2026-08-18 · closed · external user · 3 comments

remove_effect / remove_effect_by_name crash on 26.x: components[i].remove is not a function

Version: premiere-pro-mcp 1.9.3 (CEP bridge), Premiere Pro 26.x, Windows 11.

Repro: Essential Sound (used briefly for ducking) wrote its automation keyframes into a separate Amplify component on the clip — not Volume/Level. Any remove_effect* tool on that clip then fails.

Observed: bridge error components[i].remove is not a function; effect not removed. Founder had to delete it manually in Effect Controls.

Expected: component removed, or a capability-gated error.…

Read the thread · 2026-08-17 · closed · external user · 3 comments

capture_frame / export_frame fail on Premiere Pro 2026 AND 2025 (not version-specific) — wrong QE DOM object + false silent failure

Bug report — `capture_frame` / `export_frame` fail on Premiere Pro 2026 AND 2025 (not version-specific)

Pronto pra postar como issue no repo ppmcp/premiere-pro-mcp (github.com/leancoderkavy/premiere-pro-mcp, conforme instalado — confirmar org/repo exato antes de postar).

Summary

Both capture_frame and export_frame MCP tools throw the same error, reproduced on two different Premiere Pro versions (2026 v26.3.0 build 93, and 2025 v25.3.0), both on Windows:

Error:…

[Read the thread](https://github.com/leancoderkavy/premiere-pro-mcp/issues/9) · 2026-07-04 · closed · external user · 3 comments

### [Tool]: inspect_video_transition_uxp fails universally, breaking the add/remove-video-transition UXP workflow

### Tool name

inspect_video_transition_uxp

### Premiere Pro MCP version

1.14.9

### Premiere Pro version

26.3.2 build 2

### Reported backend

UXP

### Expected observable result

inspect_video_transition_uxp should return a valid target snapshot (including sequence_guid, project_item_id) for a real clip edge on a real sequence, as it did on 1.14.5. That snapshot is the documented required expected_target input for add_video_transition_uxp/remove_video_transition_uxp.

### Actual sanitized…

[Read the thread](https://github.com/leancoderkavy/premiere-pro-mcp/issues/454) · 2026-09-07 · closed · external user · 2 comments

## Most recent

### [Tool]: get_render_queue_status reports isRunning:"unknown" instead of a capability error -- app.encoder exposes no queue-status API on this host

### Tool name

get_render_queue_status

### Premiere Pro MCP version

1.14.9

### Premiere Pro version

26.3.2 build 2

### Reported backend

CEP / ExtendScript

### Expected observable result

get_render_queue_status should either return a genuine running/idle state backed by a real host API, or fail with a clear capability error naming the missing method -- not a plausible-looking "unknown" string that reads as a legitimate status value.

### Actual sanitized result or diagnostics…

[Read the thread](https://github.com/leancoderkavy/premiere-pro-mcp/issues/466) · 2026-09-07 · closed · external user · 0 comments

### [Tool]: add_tracks (QE.addTracks) silently inserts new tracks at index 0 and shifts every existing track, regardless of requested position

### Tool name

add_tracks

### Premiere Pro MCP version

1.14.9

### Premiere Pro version

26.3.2 build 2

### Reported backend

CEP / ExtendScript

### Expected observable result

When add_tracks genuinely creates new tracks (the false-success failure mode reported and fixed in #128/#131), the new tracks should land at the requested position, and existing tracks/clips should stay at their original indices unless the caller specifically requested an insert-before-existing behavior. A count-only…

[Read the thread](https://github.com/leancoderkavy/premiere-pro-mcp/issues/465) · 2026-09-07 · closed · external user · 0 comments

### [Tool]: import_ae_comps reports success for a nonexistent .aep path with no existence or item-count verification

### Tool name

import_ae_comps

### Premiere Pro MCP version

1.14.9

### Premiere Pro version

26.3.2 build 2

### Reported backend

CEP / ExtendScript

### Expected observable result

import_ae_comps should only report success when the referenced After Effects project file genuinely exists and at least one composition was actually added to the target bin -- verifiable via an independent bin item-count check, not just the tool's own return value.

### Actual sanitized result or diagnostics…

[Read the thread](https://github.com/leancoderkavy/premiere-pro-mcp/issues/464) · 2026-09-07 · closed · external user · 0 comments

### [Tool]: set_effect_property cannot set 2D vector properties (Position, Anchor Point) -- schema only accepts number|string, and readback uses strict equality on arrays

### Tool name

set_effect_property

### Premiere Pro MCP version

1.14.9

### Premiere Pro version

26.3.2 build 2

### Reported backend

CEP / ExtendScript

### Expected observable result

Setting a 2D vector effect property (for example Motion > Position, or Anchor Point, which Premiere's object model stores as an [x, y] array) via set_effect_property should either succeed and be independently verifiable via get_effect_properties, or fail with a clear, specific error -- not silently no-op or…

[Read the thread](https://github.com/leancoderkavy/premiere-pro-mcp/issues/463) · 2026-09-07 · closed · external user · 0 comments

### [Tool]: undo throws ReferenceError and redo reports unverified success -- the #272/#281 undo-stack capability fix was not applied to these two tools

### Tool name

undo, redo

### Premiere Pro MCP version

1.14.9

### Premiere Pro version

26.3.2 build 2

### Reported backend

CEP / ExtendScript

### Expected observable result

undo should reverse the most recently confirmed mutation and report success only when it did, or fail closed with an honest capability error naming the missing host API. redo should behave symmetrically. Neither result should be a bare, unverifiable success/failure.

The same underlying gap (no undo/redo-stack API on…

[Read the thread](https://github.com/leancoderkavy/premiere-pro-mcp/issues/462) · 2026-09-07 · closed · external user · 0 comments

### [Tool]: attach_custom_property reports success but the property is never persisted in actual XMP metadata

### Tool name

attach_custom_property

### Premiere Pro MCP version

1.14.9

### Premiere Pro version

26.3.2 build 2

### Reported backend

CEP / ExtendScript

### Expected observable result

attach_custom_property should either succeed and cause the property to actually appear when the clip's XMP metadata is independently read back (e.g. via get_xmp_metadata or a direct panel/metadata read), or fail with an error reflecting that it did not persist.

### Actual sanitized result or diagnostics…

[Read the thread](https://github.com/leancoderkavy/premiere-pro-mcp/issues/460) · 2026-09-07 · closed · external user · 0 comments

### [Tool]: manage_sequences_uxp rejects its own documented sequence_id/name parameters

### Tool name

manage_sequences_uxp

### Premiere Pro MCP version

1.14.9

### Premiere Pro version

26.3.2 build 2

### Reported backend

UXP

### Expected observable result

manage_sequences_uxp should accept its own documented required parameters (sequence_id and/or name, per the tool schema) for its list/rename/other actions against a real, open project with real sequences.

### Actual sanitized result or diagnostics

Called manage_sequences_uxp with a real sequence_id (a valid UUID-format…

[Read the thread](https://github.com/leancoderkavy/premiere-pro-mcp/issues/459) · 2026-09-07 · closed · external user · 0 comments

### [Tool]: import_fcp_xml hard-errors "Not Enough Parameters" on a real, valid FCP XML file this same bridge just exported

### Tool name

import_fcp_xml

### Premiere Pro MCP version

1.14.9

### Premiere Pro version

26.3.2 build 2

### Reported backend

CEP / ExtendScript

### Expected observable result

After export_as_fcp_xml produces a real FCP XML file for a real sequence, import_fcp_xml should either import it successfully or fail with an error that reflects an actual problem with the file's content, not a parameter-count error on a well-formed, single-argument call.

### Actual sanitized result or…

[Read the thread](https://github.com/leancoderkavy/premiere-pro-mcp/issues/458) · 2026-09-07 · closed · external user · 0 comments

### [Tool]: roll_edit reports success but the visible timeline edge moves while inPoint/outPoint metadata does not match

### Tool name

roll_edit

### Premiere Pro MCP version

1.14.9

### Premiere Pro version

26.3.2 build 2

### Reported backend

CEP / ExtendScript

### Expected observable result

After roll_edit reports success and the visible timeline edge genuinely moves by the requested offset, an independent read (get_full_clip_info) of the same clip should show inPointSeconds/outPointSeconds consistent with the new visible start/end -- not the pre-roll values.

### Actual sanitized result or diagnostics…

[Read the thread](https://github.com/leancoderkavy/premiere-pro-mcp/issues/457) · 2026-09-07 · closed · external user · 0 comments

### [Tool]: inspect_source_proxy_uxp and manage_timeline_source_label_uxp fail universally with "Premiere does not expose getId for this target"

### Tool name

inspect_source_proxy_uxp (reproduced identically on manage_timeline_source_label_uxp's inspect action)

### Premiere Pro MCP version

1.14.9

### Premiere Pro version

26.3.2 build 2

### Reported backend

UXP

### Expected observable result

Both tools should return a valid inspection result for a real, valid project item / timeline clip.

### Actual sanitized result or diagnostics

inspect_source_proxy_uxp({project_item_id}) -> Error: Premiere does not expose getId for this…

[Read the thread](https://github.com/leancoderkavy/premiere-pro-mcp/issues/456) · 2026-09-07 · closed · external user · 0 comments

### [Tool]: ripple_delete_track_item_uxp and slip_track_item_uxp apply genuinely mutates the project, then reports a false failure

### Tool name

ripple_delete_track_item_uxp (reproduced with same symptom shape on slip_track_item_uxp)

### Premiere Pro MCP version

1.14.9

### Premiere Pro version

26.3.2 build 2

### Reported backend

UXP

### Expected observable result

After apply on either tool reports an error, the timeline should be unchanged from before the call (no partial mutation on a reported failure). If the mutation did succeed, the tool should report success, not an error.

### Actual sanitized result or…

[Read the thread](https://github.com/leancoderkavy/premiere-pro-mcp/issues/455) · 2026-09-07 · closed · external user · 0 comments

### [Connection]: 1.14.2+ fails Claude Desktop version negotiation - disposable sibling probe requires the SDK's base StdioClientTransport

### Operating system

macOS Apple Silicon

### Premiere Pro version

26.3.2

### AI client

Claude Desktop

### Installation route

Claude Desktop bundle plus CEP connector

### Sanitized connection state

Claude Desktop 1.40609.1, premiere-pro-mcp 1.14.5 from the released .mcpb, MCPBridgeCEP.zxp 1.14.5.

**CEP connector: healthy.** Panel open, bridge directory created at the macOS per-user temp path, heartbeat `{"protocolVersion":1,"state":"running"}`.

**MCP server: never stays connected.**…

[Read the thread](https://github.com/leancoderkavy/premiere-pro-mcp/issues/347) · 2026-09-02 · closed · external user · 0 comments

### [Tool]: set_sequence_pixel_aspect_ratio throws TypeError on videoPixelAspectRatio

### Tool name

set_sequence_pixel_aspect_ratio

### Premiere Pro MCP version

1.14.5

### Premiere Pro version

26.3.2 build 2

### Reported backend

CEP / ExtendScript

### Expected observable result

After calling set_active_sequence with a specific sequence ID and independently confirming that sequence was active via get_active_sequence, calling set_sequence_pixel_aspect_ratio should either update the active sequence's pixel aspect ratio, or return a clear, structured error if the requested…

[Read the thread](https://github.com/leancoderkavy/premiere-pro-mcp/issues/335) · 2026-09-02 · closed · external user · 1 comment

### [Tool]: detect_scene_edits reports detected:true and committed_unverified but no markers are actually created

### Tool name

detect_scene_edits

### Premiere Pro MCP version

1.14.5

### Premiere Pro version

26.3.2 build 2

### Reported backend

UXP

### Expected observable result

Calling `detect_scene_edits` with `mode: "create_markers"` and a real clip selected should either create sequence/clip markers at the detected scene-change points (independently visible via `list_markers`), or return an error/negative result if it could not. It should not claim `detected: true` while producing no observable…

[Read the thread](https://github.com/leancoderkavy/premiere-pro-mcp/issues/330) · 2026-09-02 · closed · external user · 2 comments

### [Tool]: apply_spot_workflow_plan ignores its own previewed plan's clip_duration_seconds field

### Tool name

apply_spot_workflow_plan

### Premiere Pro MCP version

1.14.5

### Premiere Pro version

26.3.2 build 2

### Reported backend

Not sure

### Expected observable result

`apply_spot_workflow_plan` should apply the exact plan object returned by its corresponding preview tool (e.g. `preview_brand_spot`), including the plan's `clip_duration_seconds` field. After applying a plan requesting a 4-second clip, an independent read of the target sequence should show the inserted clip at…

[Read the thread](https://github.com/leancoderkavy/premiere-pro-mcp/issues/328) · 2026-09-02 · closed · external user · 2 comments

The remaining reports are on [the project's issue tracker](https://github.com/leancoderkavy/premiere-pro-mcp/issues).

Reported issues for MCP for Adobe Premiere Pro

Most discussed

4 issues found building a real edit: setSpeed broken, no native transitions, opacity keyframes silently ignored at render, AME preset scan misses installed presets

Environment

Summary

1. All three "change clip…

[Bug] set_sequence_audio_settings and set_sequence_frame_rate write inverted units into Time-typed fields

Description

[Bug] Project-panel delete tools and sequence-nesting tools do not perform the operation they report

Description

[Tool]: Four tools fail with "Not Enough Parameters" when called with all documented arguments

Tool name

Premiere Pro MCP version

Premiere Pro version

Reported backend

[Connection]: UXP Bridge: "Manifest entry not found" for ws://127.0.0.1:7777 on Premiere Pro 26.3.2

Operating system

Premiere Pro version

AI client

Installation route

Sanitized connection state

remove_effect / remove_effect_by_name crash on 26.x: components[i].remove is not a function

capture_frame / export_frame fail on Premiere Pro 2026 AND 2025 (not version-specific) — wrong QE DOM object + false silent failure

Bug report — capture_frame / export_frame fail on Premiere Pro 2026 AND 2025 (not version-specific)

Summary

Bug report — `capture_frame` / `export_frame` fail on Premiere Pro 2026 AND 2025 (not version-specific)