MCP Bridge for Adobe Premiere Pro — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow Adobe version and tool-discovery changes as video automation evolves

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Local AI-assisted editing and automation of Adobe Premiere Pro projects.

What we know

Local MCP bridge exposing Premiere Pro project, media, sequence, timeline, effects, captions, metadata and export operations through a CEP bridge.

Maintenance / activity evidence

Observed Sep 3, 2026 (UTC)Point the README at premiere-mcp.com so crawlers on GitHub can find t…

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Activity source · commits ↗Activity source · releases ↗

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Broad local Premiere project authority. Writes: Create/update/delete timeline objects; Apply effects and transitions; Edit captions/markers/metadata; Export media.
Authentication not yet verified.
Sensitive access: Video projects, Media files, Project metadata

The bridge can materially modify live creative projects; use project backups and review generated edits.

Security source · repository notice ↗Security source · policy file ↗Security source · policy file (attribution not established) ↗

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

608 repository stars

Stars observed Sep 25, 2026.

Do not overwrite existing reviewed stars/download metrics with nulls from this enrichment batch.

All limitations / Review context

Which Premiere operations and context resources remain supported?

The bounded assessment reviewed the official README, repository notices, security policy path, and security page for known material public-tracking blockers. No such blocker was identified. This is a public-tracking assessment, not an installation safety certification.

The bridge can materially modify live creative projects; use project backups and review generated edits.
Broad local Premiere project authority.
Local project/media are handled by Premiere; anonymous aggregated telemetry is documented with opt-out.
Reviewed write actions: Create/update/delete timeline objects; Apply effects and transitions; Edit captions/markers/metadata; Export media
Sensitive access: Video projects, Media files, Project metadata
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
No independent runtime, installation, or comprehensive security audit was performed.
No installation, runtime, client matrix, or complete tool-contract audit was performed in this review.
Requires Node.js 20+ and Premiere Pro 2020+.
CEP is the supported production bridge; UXP is experimental.
Client, package and Premiere must run on the same computer.

Original activity observations

2026-09-03T19:06:53Z: Point the README at premiere-mcp.com so crawlers on GitHub can find t…

Technical identity

github.com/hetpatel-11/adobe_premiere_pro_mcp

Exact implementation source: https://github.com/hetpatel-11/adobe_premiere_pro_mcp ↗
Reviewed resource type: MCP Server
Repository identity: hetpatel-11/adobe_premiere_pro_mcp
Package identity: npm:adobe-premiere-pro-mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 7, 2026

GitHub repository ↗
hetpatel-11/adobe_premiere_pro_mcp
Recorded repository material and project history.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 13, 2026.

Additional setup details required — see the specific gaps below.

Warning

CEP installation changes editor integration; back up project.
Do not claim UXP experimental adapter as primary supported path.
Exact vendor-specific credential revoke procedure not established from checked official Setup documentation; may be external or not applicable. Do not invent.
Requires review of install side effects, credentials, remote scripts, or privileged application/database access before execution. Multiple publisher-documented README steps combined as an ordered excerpt; not a verbatim single publisher code block.
--install-cep can change local Adobe debug setting, so review.
Preserve Premiere projects and exported media.
MCP100 client-scope note: this Claude Code CLI example applies only to that client and the exact registered name in the command. Desktop, Cursor and other clients use their own configuration; do not run it for a differently named entry.

Install / connect
Publisher instructions
Publisher-specific setup path. Follow prerequisites, then register or connect to your MCP host.
publisher documented install or connect · Publisher instructions · Review before use
```
npm install -g adobe-premiere-pro-mcp
premiere-pro-mcp --install-cep
```
Configure / authenticate
Publisher instructions
Restart Premiere Pro and open Window > Extensions > MCP Bridge (CEP); client command `premiere-pro-mcp`.
Check connection
Publisher instructions
`premiere-pro-mcp --doctor`, then `verify_premiere_connection` (no project changes).
local readiness check · Publisher instructions
premiere-pro-mcp --doctor
Remove / uninstall / revoke
MCP100 setup guide
Remove Premiere MCP client entry; disable/uninstall CEP bridge separately following publisher installer guidance.
MCP100 client-scope guidance: each CLI removal example targets only its named client and exact registered entry. Package names, Desktop/Cursor configuration keys and Codex/Claude registration names may differ; use the entry you actually registered. Client removal does not revoke provider credentials.
claude mcp remove premiere-pro-mcp

Official Documentation & Sources

What it does

Local MCP bridge exposing Premiere Pro project, media, sequence, timeline, effects, captions, metadata and export operations through a CEP bridge.

Capability: Design & Creative
Resource type: MCP Server
Industry: Media & Marketing
Best fit: Local AI-assisted editing and automation of Adobe Premiere Pro projects.

Representative uses

Inspect projects and sequences
Import and arrange media
Edit timeline/effects/transitions/captions/markers
Export project/media outputs

Limitations

Requires Node.js 20+ and Premiere Pro 2020+.
CEP is the supported production bridge; UXP is experimental.
Client, package and Premiere must run on the same computer.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Not documented in the reviewed sources
Permissions: Broad local Premiere project authority.
Data handling: Local project/media are handled by Premiere; anonymous aggregated telemetry is documented with opt-out.
Cost: free
Risk and cautions: The bridge can materially modify live creative projects; use project backups and review generated edits.

Access scope and cautions

Write actions: Create/update/delete timeline objects Apply effects and transitions Edit captions/markers/metadata Export media
Sensitive access: Video projects Media files Project metadata
Risk level: high

FAQ

Based on reviewed evidence as of 2026-10-07. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Inspect projects and sequences; Import and arrange media; Edit timeline/effects/transitions/captions/markers; Export project/media outputs.

What setup and authentication are documented?

Recorded installation/entrypoint step: npm install -g adobe-premiere-pro-mcp && premiere-pro-mcp --install-cep && premiere-pro-mcp --doctor. Recorded transport: stdio/local_bridge. Recorded environment-variable notes: PREMIERE_MCP_TELEMETRY=0 (optional); DO_NOT_TRACK=1 (optional). No configuration values are supplied here. Prerequisites: Node.js 20+; Adobe Premiere Pro 2020+. Client notes: Restart Premiere and open the MCP Bridge CEP panel before verification. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: No remote auth documented; local CEP bridge.

Can it modify data or perform write operations?

Documented write actions include: Create/update/delete timeline objects; Apply effects and transitions; Edit captions/markers/metadata; Export media. Recorded permission boundary: Broad local Premiere project authority.

What data-handling boundary should I consider?

Local project/media are handled by Premiere; anonymous aggregated telemetry is documented with opt-out. Recorded sensitive-access context: Video projects; Media files; Project metadata.

What limitations and risks should I check before use?

The bridge can materially modify live creative projects; use project backups and review generated edits. Requires Node.js 20+ and Premiere Pro 2020+. CEP is the supported production bridge; UXP is experimental. Client, package and Premiere must run on the same computer. No independent runtime, installation, or comprehensive security audit was performed.

Is this an official MCP?

hetpatel-11 is listed as Community implementation in MCP100’s current evidence.