Premiere MCP · Client setup

Setting up your MCP client

Three steps: paste the snippet with your license into the client's config file, restart the client so it picks up the new server, and check that Premiere responds.

1. The snippet you paste

This is the JSON that goes inside your MCP client's config file. Replace your-license-key with your real key from /dashboard/licenses.

{
  "mcpServers": {
    "premiere-mcp": {
      "command": "npx",
      "args": ["-y", "@synthetic-ai/premiere-mcp"],
      "env": {
        "PREMIERE_PRO_MCP_LICENSE": "your-license-key"
      }
    }
  }
}

On /dashboard/downloads there's a 'Copy JSON' button that already has your license key inserted — copy from there rather than typing by hand.

2. Where it goes per client

Claude Desktop

Edit %APPDATA%\Claude\claude_desktop_config.json on Windows, or ~/Library/Application Support/Claude/claude_desktop_config.json on macOS. Drop the block into the mcpServers object. If you already have other servers, add it as one more key.

Cursor

Settings → Cursor Settings → MCP → Edit Config. Paste the snippet into the JSON and save.

Codex CLI / Other

The file ~/.codex/config.toml uses TOML format. Convert the snippet — example:

[mcp_servers.premiere-mcp]
command = "npx"
args = ["-y", "@synthetic-ai/premiere-mcp"]
env = { PREMIERE_PRO_MCP_LICENSE = "your-license-key" }

3. Restart the client and try it

Quit the MCP client and reopen it — servers are loaded at startup. Then open Premiere Pro with a project and ask the client something like:

What sequences are in the active project?

If it answers with your sequence list, the connection works. If not, see the troubleshooting guide.

← Installation Troubleshooting