Premiere Pro MCP Server

Adobe Premiere Pro editing workflows controlled via structured AI assistant requests.

Data last scanned today · Reviewed today

185 dangerous tools130 tools239TypeScriptMIT

Overview

This server provides structured control over Adobe Premiere Pro, enabling AI assistants to execute complex editing workflows. It exposes 369 core tools across 53 modules and 17 guided workflows, allowing for fine-grained interaction with project bins and render handoffs. Built with TypeScript and supporting Node.js 20.19+, it includes a connected UXP host that adds 93 capability-gated tools. The project has been tested for After Effects render handoffs, providing automated import receipts and file validation.

Our verdict

With a security score of 48/100, this server is classified as high risk. The rating is primarily due to the fact that its authentication methods and read-only mode support have not yet been editorially reviewed. While it offers extensive automation, users should exercise caution as it is a community-maintained project rather than an official Adobe integration, making it better suited for power users and developers rather than sensitive corporate environments.

  • Supports 369 core tools across 53 distinct modules.
  • Small dependency footprint with only eight direct dependencies.
  • Active development with the most recent commit occurring today.
  • Includes documentation for After Effects render handoff workflows.
  • Authentication methods have not undergone a security review.
  • Community-maintained project lacking official Adobe vendor support.
  • Read-only mode implementation is currently unverified.

Setup

Claude Desktop
{
  "mcpServers": {
    "premiere-pro-mcp": {
      "args": [
        "-y",
        "premiere-pro-mcp"
      ],
      "command": "npx"
    }
  }
}

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), then restart Claude Desktop. Some servers require API keys or tokens as environment variables — check the project's README and add an "env" object if needed.

  • No read-only mode — running this grants full read/write access.
  • No built-in authentication — anyone with access to this config can invoke every tool it exposes.

Tools

ToolDescriptionRisk
get_project_infoCurrent project name, path, sequences, itemslow
get_active_sequenceDetailed active sequence with all clipslow
list_project_itemsAll items in the project panellow
get_full_project_overviewComprehensive snapshot: bin tree, sequences, media typeslow
get_full_sequence_infoExhaustive sequence data: tracks, clips, effects, markerslow
get_full_clip_infoEverything about a clip: effects, keyframes, metadatalow
get_timeline_summaryHuman-readable overview: duration, coverage %, effectslow
search_project_itemsFilter by name, extension, offline status, color labellow
get_premiere_stateFull snapshot: project, sequence, playhead, selectionlow
inspect_dom_objectExplore any Premiere Pro DOM object interactivelylow

Compatibility

ClientLocalDockerRemoteRead-only
Claude Desktop
Cursor
VS Code
Windsurf
ChatGPT

Frequently asked questions

What software prerequisites are required to run this MCP server?

You need Node.js version 20.19 or higher installed, and it supports Adobe Premiere Pro versions 2020 through 2026.

Which operating systems are supported?

The server provides capability coverage for both Windows and macOS environments.

How do I install the required connector for Premiere Pro?

After installing the npm package globally, you must run the command premiere-pro-mcp --install-cep to set up the necessary bridge in Premiere Pro.

Does this server support remote deployment?

Yes, the project includes support for remote deployment via Fly.io.

Alternatives

Changelog

Badge

Premiere Pro MCP Server security score, rated on RepoAI

Maintain this server? Add the live badge to your README.