Adobe Premiere Pro MCP

Community

Give AI full control over Adobe Premiere Pro.

How to install ↓ Compare GitHub source repository ↗

Category: Dev Tools #121 of 438
Stars: ★ 404 Very popular
Transport: stdio (local process) · Streamable HTTP
Runtime: Node.js 20.19+ · Docker · Hosted (no local runtime)
Credentials: No credential needed
License: MIT
Last commit: 3 days ago
Tools: 100

60FMRS · C

Premiere Pro MCP is a powerful server providing extensive control for AI-driven video editing. It supports multiple MCP clients and includes security features like capability profiles. However, its security model requires users to understand the risks and take appropriate precautions.

Strongest · Documentation 14/20 Weakest · Setup experience 10/20

Reliability

11/20

Security and permissions

13/20

Maintenance

12/20

Documentation

14/20

Setup experience

10/20

Why each score

Reliability 11/20: Evidence shows complete TypeScript sources, 31 tool modules, tests, CI workflows, and a Dockerfile; the README claims 280 registered tools, dynamic registration, and authority-profile filtering. However, this review is static only: nothing was executed, the README/release notes are untrusted evidence, and I could not inspect the actual test files and GitHub Actions content in the supplied material to confirm they cover the server's key paths. Reliability is therefore capped at 12; I give 11 for the coherent structure, explicit error handling, and versioned release claims. Deductions: lack of verifiable CI/test evidence in the reviewed file set, and inherent dependence on a live Adobe Premiere host, CEP, and QE DOM, which static review cannot confirm.
Security and permissions 13/20: Evidence shows a stdio-first default, HTTP transport requiring MCP_AUTH_TOKEN, unsafe-script disabled by default, execute_extendscript/evaluate_expression hidden and call-denied without explicit authority, temp directory mode 0700 with ownership checks, a 500 KB script size limit and eval/new Function/System.callSystem guard, telemetry that excludes tokens/paths/arguments/results, and explicit warnings about remote exposure. No red-line issues such as credential theft, covert exfiltration, irreversible destructive defaults, or real secrets in install examples were found. Deductions: the script guard is explicitly a guard rail, not a sandbox; the HTTP transport binds 0.0.0.0 without rate-limiting or audit-trail evidence; the UXP token is plaintext env config; no general second-confirmation mechanism for dangerous edits was found in the static evidence.
Maintenance 12/20: Evidence shows an MIT license, CHANGELOG.md, CONTRIBUTING.md, a token-free GitHub Actions npm publication workflow documented in the README, multiple releases (1.9.2, 1.9.1, 1.9.0, etc.), and an unarchived repository with only one open issue. Deductions: the static review did not include actual commit history, issue-response timeliness, dependency-update frequency, or a security-response channel, and npm/package version consistency cannot be verified from the README alone. On the maintenance anchor, this justifies 12 rather than a higher score.
Documentation 14/20: Evidence shows layered documentation: quick start, Claude Desktop .mcpb install, npm/source install, CEP plugin install, manual Windows/macOS steps, per-client JSON examples, environment variable table, tool tables, resource URIs, troubleshooting, remote deployment, security model, architecture diagrams, project structure, and release notes. It also discloses known Premiere 26.3 QE compatibility limitations and unsupported export formats. Deductions: much of this comes from the README/release notes (untrusted for verification), per-tool parameter references are not present in the supplied evidence, and the large tool surface still leaves hidden assumptions about real-host behavior.
Setup experience 10/20: Evidence shows multiple setup routes: Claude Desktop .mcpb bundle, npm global install with --install-cep, source clone/build, macOS/Windows manual CEP installation, client JSON configs for Claude Desktop/Windsurf/Cursor/Copilot, --doctor and verify_premiere_connection, plus Fly.io remote deployment. Deductions: the actual installer scripts and CI test files were not in the reviewed file set, so executability cannot be verified; the overall setup is inherently multi-part (MCP server + CEP plugin + Premiere + client), and UXP adds token/panel authentication. Per static calibration, setup cannot exceed 15; I give 10. Uncertainty and missing execution evidence lower the score.

Static review · not runListed 2026-08-07

Read the FMRS scoring method →

Fit and risk

What it can accessReads local filesWrites / deletes local filesRuns commands or codeUses the network

Best for

Creative professionals and post-production teams seeking AI-driven video editing.
Developers who want to integrate Premiere Pro automation into AI workflows.
Users who want to automate repetitive editing tasks with AI assistance.

Not for

Non-technical users? Some configuration is required, but Claude Desktop offers a one-click .mcpb install.
Large-scale production? Requires local installation and permission management.
Users needing real-time collaboration or cloud editing? This server is single-machine control, not multi-user.

Required permissions

Read and write project files, media files, and XMP metadata.
Execute ExtendScript code (requires explicit authority).
Communicate with a local Adobe Premiere Pro instance.
Export files to the local filesystem.

Risks and side effects

Any client that can reach the MCP server can fully control Premiere Pro.
execute_extendscript and evaluate_expression allow arbitrary code execution; enable with caution.
Filesystem operations may overwrite or delete files.
Remote deployment requires an auth token to prevent unauthorized access.

Setup

Before you start

Runtime：Node.js 20.19+ · Docker · Hosted (no local runtime)

PREMIERE_UXP_TOKEN optionalsecret WebSocket auth token for the local UXP panel; enter the same value in the panel — generate your own long random secret.

MCP_AUTH_TOKEN optionalsecret Bearer token required by the HTTP transport — the server refuses to start without it; choose a strong random value.

POSTHOG_API_KEY optionalsecret PostHog project token enabling privacy-safe MCP usage telemetry; obtain from your PostHog project settings.

Other optional settings (11)

PREMIERE_TEMP_DIR optional Shared temp directory for MCP-to-CEP communication; defaults to OS temp dir + /premiere-mcp-bridge, only set if the sides disagree.

PREMIERE_TIMEOUT_MS optional Bridge command timeout in milliseconds, default 30000; raise to 60000+ if commands hang.

PREMIERE_DEFAULT_SEQUENCE_PRESET optional Overrides the auto-discovered .sqpreset used by create_sequence.

PREMIERE_MCP_CAPABILITIES optional Comma-separated authority profile, default inspect,edit,export,filesystem; add unsafe-script to enable the raw scripting tools.

PREMIERE_MCP_DEBUG optional Set to 1 (or true) to emit verbose diagnostics to stderr.

PREMIERE_UXP_PORT optional UXP listener port; defaults to loopback 127.0.0.1:7777 but can use another loopback port.

PORT optional HTTP port for the HTTP/SSE transport, default 3000; only used in remote deployments.

ALLOW_UNAUTHENTICATED optional Set to 1 to run HTTP without auth; unsafe, throwaway instances only.

POSTHOG_HOST optional PostHog ingestion host, default https://us.i.posthog.com.

POSTHOG_ENVIRONMENT optional Environment label attached to telemetry events, default production.

POSTHOG_DISTINCT_ID optional Optional stable anonymous server identifier; defaults to Fly machine ID or a random boot ID.

Install Node.js 20.19+ and npm.\n2. Install the server globally: npm install -g premiere-pro-mcp.\n3. Install the CEP plugin: run premiere-pro-mcp --install-cep.\n4. Configure your MCP client (e.g., Claude Desktop) to use the premiere-pro-mcp command.\n5. Restart Premiere Pro, open a project, and enable the “MCP Bridge” extension from the Extensions menu.\n6. Verify the connection using the verify_premiere_connection tool.

claude_desktop_config.json

{
  "mcpServers": {
    "premiere-pro": {
      "command": "premiere-pro-mcp"
    }
  }
}

Shown for Claude Desktop. Other clients may use a different file or key (VS Code uses "servers") — the configurator below converts it.

.vscode/mcp.json

{
  "servers": {
    "premiere-pro": {
      "command": "premiere-pro-mcp"
    }
  }
}

Goes in your project's .vscode/mcp.json (VS Code uses a "servers" key).

Terminal

claude mcp add premiere-pro -- premiere-pro-mcp

Run it in a terminal; replace any <…> placeholders with your own values first.

Generate and validate client config

Check that it works

After installing the CEP connector and restarting Premiere, run ping and get_capabilities from your client (or ask the assistant to run verify_premiere_connection); a returned connection report plus get_project_info reading the open project confirms the bridge works.

Troubleshooting

CEP plugin not appearing: Check debug mode and that the extension is installed correctly.
Commands timing out: Ensure the MCP server and CEP panel use the same temp directory.
AI client can't see tools: Restart the client and check config file paths.
QE DOM tools failing: Ensure there is an active sequence.

Things to try

Once connected, you can ask your AI assistant things like:

Safely check my Premiere connection with verify_premiere_connection. Make no changes.
What is my current Premiere Pro project and active sequence? Do not make changes.
Add the B-roll clips to V2, apply a cross dissolve between each, color correct them to match the A-roll, and export a 1080p ProRes.
List all project panel items and filter by extension to find offline media.

Tools 100

get_project_info read-only

Gets the current project name, path, sequences, and items.

get_active_sequence read-only

Gets detailed active sequence info for all clips.

list_project_items read-only

Lists all items in the project panel.

get_full_project_overview read-only

Gets a comprehensive snapshot: bin tree, sequences, media types.

get_full_sequence_info read-only

Gets exhaustive sequence data: tracks, clips, effects, markers.

get_full_clip_info read-only

Gets everything about a clip: effects, keyframes, metadata.

get_timeline_summary read-only

Gets a human-readable overview: duration, coverage %, effects.

search_project_items read-only

Filters project items by name, extension, offline status, color label.

Show 92 more tools

get_premiere_state read-only

Gets a full snapshot: project, sequence, playhead, selection.

inspect_dom_object read-only

Explores any Premiere Pro DOM object interactively.

get_advanced_feature_support read-only

Checks collaboration and AI feature support, prerequisites, entitlements, and user-assisted boundaries.

save_project writes

Saves the current project.

save_project_as writes

Saves the current project as a new file.

open_project writes

Opens a project file.

create_project writes

Creates a new project.

close_project writes

Closes the current project.

import_media writes

Imports media files into the project.

import_folder writes

Imports media from a folder.

import_ae_comps writes

Imports After Effects compositions.

create_bin writes

Creates a bin.

delete_bin destructive

Deletes a bin.

rename_bin writes

Renames a bin.

create_smart_bin writes

Creates a smart bin.

import_sequences writes

Imports sequences from other projects.

import_fcp_xml writes

Imports FCP XML files.

create_bars_and_tone writes

Generates bars and tone media.

set_scratch_disk_path writes

Configures scratch disks.

consolidate_and_transfer writes

Consolidates and transfers using Project Manager.

add_to_timeline writes

Adds clips to the timeline.

overwrite_clip writes

Overwrites a clip.

ripple_delete destructive

Removes a clip and closes the gap (QE).

roll_edit writes

Performs a roll edit (QE).

slide_edit writes

Performs a slide edit (QE).

slip_edit writes

Performs a slip edit (QE).

move_clip_to_track writes

Moves a clip to a specific track (QE).

set_clip_speed_qe writes

Sets clip speed (QE).

reverse_clip writes

Reverses a clip (QE).

split_clip writes

Splits a clip.

trim_clip writes

Trims a clip.

move_clip writes

Moves a clip.

set_clip_properties writes

Sets opacity, scale, rotation, position, etc.

link_selection writes

Links selected A/V clips.

unlink_selection writes

Unlinks selected A/V clips.

apply_effect writes

Applies an effect by name (QE).

apply_audio_effect writes

Applies an audio effect by name (QE).

remove_effect destructive

Removes an effect.

remove_all_effects destructive

Removes all effects from a clip.

color_correct writes

Color corrects using Lumetri: exposure, contrast, temperature, etc.

apply_lut writes

Applies LUT files.

stabilize_clip writes

Stabilizes using Warp Stabilizer.

add_keyframe writes

Adds a keyframe.

get_keyframes read-only

Gets keyframes.

remove_keyframe destructive

Removes a keyframe.

remove_keyframe_range destructive

Removes keyframes in a range.

set_keyframe_interpolation writes

Sets keyframe interpolation: Linear, Hold, or Bezier.

get_value_at_time read-only

Queries interpolated value at any time.

set_color_value writes

Sets color properties on effects.

export_sequence writes

Exports via Adobe Media Encoder.

validate_export_preset read-only

Validates an .epr file and resolves its output extension in Premiere.

verify_delivery_file read-only

Verifies output size and calculates SHA-256/SHA-512 checksums.

capture_frame read-only

Exports a frame as PNG and returns as base64 image.

export_as_fcp_xml writes

Exports as FCP XML.

export_aaf writes

Exports as AAF.

export_omf writes

Exports as OMF.

encode_project_item writes

Directly encodes a project item.

encode_file writes

Directly encodes a file.

start_batch_encode writes

Starts the render queue.

open_in_source writes

Opens a clip in the source monitor.

close_source_monitor writes

Closes the source monitor.

insert_from_source writes

Inserts from the source monitor.

overwrite_from_source writes

Overwrites from the source monitor.

play_timeline writes

Plays the timeline (QE).

stop_playback writes

Stops playback (QE).

play_source_monitor writes

Plays in the source monitor.

select_clips_by_name writes

Selects clips by name.

select_clips_in_range writes

Selects clips in a range.

copy_effects_between_clips writes

Copies effects via QE.

batch_apply_effect writes

Applies an effect to multiple clips.

set_blend_mode writes

Sets a blend mode (27 modes).

set_offline destructive

Sets a clip offline.

has_proxy read-only

Checks if a clip has a proxy.

detach_proxy writes

Detaches a proxy.

set_override_frame_rate writes

Overrides frame rate.

set_scale_to_frame_size writes

Scales to sequence frame size.

get_xmp_metadata read-only

Gets raw XMP metadata.

set_xmp_metadata writes

Sets raw XMP metadata.

get_color_space read-only

Gets color space info.

create_sequence writes

Creates a sequence.

create_sequence_from_preset writes

Creates a sequence from a .sqpreset file without a modal dialog.

duplicate_sequence writes

Duplicates a sequence.

delete_sequence destructive

Deletes a sequence.

auto_reframe_sequence writes

Auto-reframes for social media.

attach_custom_property writes

Attaches custom properties to FCP XML.

unnest_sequence writes

Replaces a nested sequence with its clips.

get_workspaces read-only

Gets workspace layouts.

set_workspace writes

Switches workspace layout.

create_caption_track writes

Creates a caption track.

execute_extendscript destructive

Runs arbitrary ExtendScript (ES3); requires explicit unsafe-script authority.

evaluate_expression destructive

Evaluates a one-line expression; requires explicit unsafe-script authority.

ping read-only

Tests basic connectivity between MCP server and Premiere.

Use cases

Automating video editing workflows such as adding B-roll, applying transitions, and color correction.

Batch processing media import, effect application, and export.

Allowing AI assistants to generate or modify timelines based on natural language instructions.

Integrating into larger automation pipelines for content production and delivery.

Supported clients

Claude Desktop

Windsurf

Cursor

GitHub Copilot

Listed from the project's documentation, not tested by this site.

Overview

Premiere Pro MCP is a Model Context Protocol (MCP) server that lets AI assistants like Claude, Windsurf, Cursor, GitHub Copilot, or any MCP-compatible client directly control Adobe Premiere Pro. It provides 280 core tools covering media import, timeline editing, effect application, keyframe management, export, and more. The server supports local stdio and remote HTTP/SSE transport, communicating with Premiere via a CEP bridge. It also includes an optional UXP preview bridge offering 19 additional tools, but requires a separate connection. The server is security-aware by default, requiring explicit authority for arbitrary ExtendScript execution.

Similar servers

Context7 80 · B

Upstash's official server providing up-to-date third-party library docs for AI coding assistants

★ 63.3k · Tools 2 Compare with this →

NPM Sentinel MCP Server 79 · B

AI-powered NPM package analysis MCP server

★ 18 · Tools 19 Compare with this →

MartinLoop MCP Server 79 · B

An independent control layer that gives AI coding agents budgets, brakes, and receipts

★ 413 Compare with this →

GitHub MCP Server 76 · B

GitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language

★ 33.7k · Tools 15 Compare with this →

Compare with other MCP servers

Source revision be39a43c15e4 Data synced 2026-10-19 Read the FMRS scoring method