Adobe Premiere Mcp

io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.2Updated Oct 30, 2026

Control Adobe Premiere Pro video editing via ExtendScript.

VerifiedSTDIODesktop onlyDeveloper ToolsMedia & Design

Overview

AI-generated overview

Local MCP server that lets an AI assistant drive Adobe Premiere Pro through ExtendScript: inspect projects, import media, build sequences, apply effects and…

What you can do
  • Check whether Premiere Pro is running and read the current project's name, path and sequence count
  • List sequences and the clips in the first sequence, and get active sequence details
  • Create sequences with custom dimensions and frame rate, and import media files into the project
  • Read metadata about media files and apply an effect to the first clip
  • Export a sequence to H.264, ProRes or HEVC, and run arbitrary ExtendScript code
When to use it
Useful when you want an assistant to help with repetitive Premiere Pro editing work on a desktop machine — setting up sequences, importing footage, applying effects or exporting deliverables — without clicking through the UI yourself.
Requirements
Runs as a local process via npx (Node.js). Adobe Premiere Pro must be installed and running on the same machine; desktop only. On macOS, the optional PREMIERE_PATH environment variable can point to a non-standard app bundle location. No authentication is declared.
Before you install
The run_custom_script tool executes arbitrary ExtendScript (JavaScript) inside Premiere, so only use it with code you trust. Tools change the open project and write exported files to disk, and several act on the first sequence or first clip rather than a chosen one. PREMIERE_PATH points at a local application path.

Installation

In SourceWeft

  1. Open Adobe Premiere Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Adobe Premiere MCP

An MCP server for Adobe Premiere Pro, the industry-standard video editing software.

What it does

Control Adobe Premiere Pro from AI agents via ExtendScript. Import media, create sequences, apply effects, export media, and run custom scripts.

Tools

  • is_premiere_running - Check if Premiere Pro is running
  • get_project_info - Get current project info (name, path, sequence count)
  • list_sequences - List all sequences in the project
  • list_clips - List clips in the first sequence
  • create_sequence - Create a new sequence with custom dimensions and frame rate
  • import_media - Import a media file into the project
  • get_media_info - Get metadata about a media file
  • get_sequence_info - Get active sequence details
  • apply_effect - Apply an effect to the first clip
  • export_media - Export the sequence to a file (H.264, ProRes, HEVC)
  • run_custom_script - Run arbitrary ExtendScript (JavaScript) code

Install

bash
npx adobe-premiere-mcp

Requirements

  • Adobe Premiere Pro must be installed
  • On macOS: PREMIERE_PATH env var to the app bundle (default: standard location)
  • On Windows: Premiere must be installed and accessible

Environment Variables

  • PREMIERE_PATH - Optional custom path to Adobe Premiere Pro app

Claude Desktop setup

json
{  "mcpServers": {    "premiere": {      "command": "npx",      "args": ["-y", "adobe-premiere-mcp"]    }  }}

Example usage

"Is Adobe Premiere running?" "Create a 1920x1080 30fps sequence called 'YouTube Video'" "Import /Users/me/videos/clip.mp4 into the current project" "Apply GaussianBlur effect with radius 5.0" "Export the current sequence as H.264 to /Users/me/output.mp4"

License

MIT

Source: README.md at commit 4321d90

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v1.0.2LatestSep 22, 2026
  2. v1.0.1Sep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.