MCP for Adobe Premiere Pro MCP Server

What the code does

We read the source, 18 h ago · rules 3dff92dd89df

Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.

  const result = spawnSync(npm.command, [...npm.prefix, "root", "--global"], {

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

    var statusPath = path.join(updateDirectory, "premiere-pro-mcp-update-" + suffix + ".json");

  const result = spawnSync(npm.command, [...npm.prefix, "root", "--global"], {

            35 MM · SELECT {String(((chapter + slot + 2) % 3) + 1).padStart(2, "0")}

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add premiere-pro -- npx -y premiere-pro-mcp

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

[mcp_servers.premiere-pro]
command = "npx"
args = ["-y", "premiere-pro-mcp"]

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

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