RepoAI
Browse MCPs

Adobe Premiere Pro MCP Server

Adobe Premiere Pro local project management via 283 tools and 13 resources.

Data last scanned yesterday · Reviewed 3 weeks ago

48★ 462TypeScriptMIT

Overview

This bridge enables AI models to interact with local Adobe Premiere Pro projects using a CEP-based architecture. It provides 283 tools and 13 context resources, alongside 10 guided prompts for tasks within the editor. Installation requires Node.js 20+ and works by deploying a CEP panel directly into Premiere Pro. Users must run the installation command and verify the connection before performing any edits. While a UXP plugin is bundled for evaluation, it is considered experimental compared to the primary CEP production bridge.

Our verdict

This server carries a high risk level with a security score of 45/100. It is a community-maintained project that has not undergone editorial review, meaning users should exercise caution given the potential for vulnerabilities in unvetted code. It is suitable for power users who understand the risks of integrating third-party bridges with their professional video editing software, but it is not recommended for environments where strict security governance is required.

  • Supports 283 tools for extensive project control
  • Active development with commits within the last week
  • Small supply-chain footprint with only 5 direct dependencies
  • Multi-language documentation support for global users
  • Not maintained by the official software vendor
  • Experimental status of UXP bridge integration
  • Security architecture remains unreviewed by third-party auditors

Setup

Claude Desktop
{
  "mcpServers": {
    "adobe-premiere-pro-mcp": {
      "args": [
        "-y",
        "adobe-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.

Compatibility

ClientLocalDockerRemoteRead-only
ChatGPT
Claude Desktop
Cursor
VS Code
Windsurf

Frequently asked questions

›What Adobe Premiere Pro version is required?

The server supports Adobe Premiere Pro 2020 and later versions.

›Is the UXP bridge ready for production use?

No, the UXP bridge is an experimental preview; the CEP panel is the supported production bridge.

›What is the role of the --doctor command?

The --doctor command verifies your server build, the CEP installation, the bridge directory, Adobe debug settings, and client configurations.

›How do I verify the server is working after installation?

After starting the CEP bridge in Premiere Pro, you should run the verify_premiere_connection tool within your MCP client.

›Are Node.js requirements specific?

Yes, you must have Node.js version 20 or higher installed on your system.

›Can I use this server with MCP clients other than Claude Desktop?

Yes, you can manually configure other clients by setting the command to premiere-pro-mcp in your mcpServers configuration.

Changelog

Badge

Adobe Premiere Pro MCP Server security score, rated on RepoAI

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