Log inSubmit server
MCP for Adobe Premiere Pro logo

MCP for Adobe Premiere Pro

Connects AI assistants to local Adobe Premiere Pro projects for inspection, organization, editing workflows, and verified project operations.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install MCP for Adobe Premiere Pro

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "mcp-for-adobe-premiere-pro": {
      "command": "npx",
      "args": [
        "-y",
        "premiere-pro-mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Automated check passed— started and listed 445 tools correctly (2d ago).

Overview

MCP for Adobe Premiere Pro MCP server connects compatible AI assistants to Adobe Premiere Pro through a local server and a separate Premiere connector. It exposes tools for inspecting projects, sequences, tracks, clips, bins, metadata, and media paths, along with guarded project-management and interchange operations. Reach for it when an agent needs structured access to a local Premiere project rather than direct, unreviewed UI control. The server is positioned for local-first multimedia workflows and begins with a read-only connection check.

Use cases

  • Inspect an open Premiere project before planning an edit
  • Organize bins and locate clips by name or media path
  • Review sequence settings, tracks, selections, and timeline clips
  • Import sequences, After Effects compositions, or Final Cut Pro XML
  • Save, reopen, and verify Premiere project files

Key features

  • Read project, sequence, track, and clip information
  • Create, open, save, and close Premiere projects
  • Manage bins, smart bins, metadata fields, and duplicate items
  • Import AE compositions, sequences, and FCP XML
  • Request Media Encoder batch-encode handoff
  • Perform guarded, stack-checked undo operations

Tools445

What MCP for Adobe Premiere Pro lets your agent do. Expand a tool for its parameters.

Verified live~545.9k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

15/15 checks healthy over the last 45d

What it can do

From the 445 tools this server returned when we ran it; 445 declare their own safety hints.

Runs commands · 5Can delete or modify data · 40Handles credentials · 14Makes network requests · 29Read-only tools · 400
Tool definitions changed on 2026-11-10. Review them if you approved this server earlier.
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceSigned build
Package age256 days
Maintainers1

Observed 2026-11-10 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 14d ago via OSV.dev · premiere-pro-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars511Stargazers on the source repository.
npm downloads25kPackage downloads in the last 30 days.
Last commit2d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed445Callable tools this server registers over MCP.
Directory activity15 viewsConfig copies, upvotes, and views on AllMCPs.

How MCP for Adobe Premiere Pro works

What MCP for Adobe Premiere Pro does

MCP for Adobe Premiere Pro connects an MCP-compatible AI client with Adobe Premiere Pro through a local Node.js server and a Premiere-side connector. It is intended for supported workflows on Windows and macOS with Premiere Pro 2020–2026. The package is published on npm as premiere-pro-mcp, and the project is licensed under MIT.

The exposed operations cover both inspection and project changes. An agent can read project structure, identify the active sequence, inspect tracks and clips, locate items by name or media path, and read sequence settings. It can also manage projects and bins, import sequences or interchange files, create synthetic Bars and Tone media, request batch encoding, and save or open project files.

How it works

The MCP server runs locally and communicates with a separate Premiere connector using Adobe’s documented UXP and CEP/ExtendScript APIs. A compatible client sends tool calls over MCP; Premiere performs the requested operation, and the server returns structured results. The recommended starting point is the connection check before attempting edits or other changes.

The active sequence can be retrieved in bounded pages, with a default of 50 clips and a continuation offset for larger timelines. Project and file operations perform checks against Premiere state or the filesystem where supported. For example, saving reports whether a non-empty file was written, while opening a project verifies that the requested path became active.

Setup and configuration

Install the npm package globally:

Terminal
npm install -g premiere-pro-mcp

Install the Premiere connector with:

bash
premiere-pro-mcp --install-cep

The package requires Node.js 20.19 or newer. Configure an MCP-compatible client to launch the local server, then verify the bridge from Premiere before using project-changing tools. Published setup guidance covers Claude Desktop, Cursor, and Codex configurations; the project also references Windsurf, GitHub Copilot, and VS Code usage.

Tools and capabilities

Representative capabilities include:

  • Read project information, project-panel items, sequences, tracks, selected clips, clip properties, and sequence settings.
  • Find project items recursively by name or search for items by media-path text.
  • Identify the active sequence, set it by name or ID, and locate a clip at a timeline position.
  • Create, open, save, save as, and close Premiere projects, with path and state checks.
  • Rename or delete bins, create smart bins, inspect the insertion bin, consolidate duplicate media, and add metadata schema fields.
  • Import After Effects compositions, Premiere sequences, or Final Cut Pro XML; create Bars and Tone media; and request Media Encoder queue handoff.
  • Request undo operations through Premiere’s QE interface with stack-position checks.

Limitations and notes

Some results describe a request or handoff rather than proving the final outcome. Transcoding-on-ingest reports that the request was dispatched because Premiere does not expose an independent getter. Batch encoding reports accepted handoff, not queue progress or output-file creation. Smart-bin creation verifies identity and name, but its stored search query has no getter.

Undo is experimental and depends on Premiere’s QE undo stack. It can reverse actions recorded by Premiere, but it cannot account reliably for changes made through UXP, the manual UI, other clients, or an engine reset. Marker receipts and tracked undo steps help bound supported reversals, but a matching stack index alone does not identify the action at the top.

Saving a project to a new path causes Premiere to keep the new copy open and close the original; later edits therefore target the copy until the original is opened again. Importing FCP XML into an open project can also bring duplicate clips because the XML includes its own media items.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about MCP for Adobe Premiere Pro

MCP for Adobe Premiere Pro is an MCP server that connects compatible AI assistants to local Adobe Premiere Pro projects through a Premiere connector. Its main tools inspect projects, sequences, tracks, clips, bins, and settings, while also supporting project management, imports, metadata, encoding handoff, and selected guarded edits.

Install it with `npm install -g premiere-pro-mcp`, then install the Premiere connector with `premiere-pro-mcp --install-cep`. Configure an MCP client to launch the local server and verify the Premiere bridge before using project-changing tools. Node.js 20.19 or newer is required.

Yes, Cursor is named as a supported MCP client. Configure Cursor to launch the locally installed `premiere-pro-mcp` package, install the Premiere connector, and verify the connection from Premiere before requesting project inspection or modification operations.

Yes, it provides `import_fcp_xml`. The default mode creates a new Premiere project at a destination path and verifies that Premiere opens that file. An alternative mode imports the XML into the currently open project and succeeds when the project’s sequence count increases.

Yes, the `undo` tool can reverse supported actions recorded in Premiere’s QE undo stack. It is experimental and uses stack-position checks plus tracked undo-step counts. UXP actions, manual UI changes, other clients, and some untracked operations may not be safely attributable or reversible.

Related MCP servers

All in Multimedia Process All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewMCP for Adobe Premiere Pro AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/mcp-for-adobe-premiere-pro?style=directory)](https://allmcps.com/mcp/mcp-for-adobe-premiere-pro)
HTML Embed
<a href="https://allmcps.com/mcp/mcp-for-adobe-premiere-pro"><img src="https://allmcps.com/api/badge/mcp-for-adobe-premiere-pro?style=directory" alt="MCP for Adobe Premiere Pro on AllMCPs" /></a>