Premiere Pro MCP Server

Manage Proxies

manage_proxies

Create, attach, or toggle proxies for Premiere Pro project items. Creation requests encoding via Adobe Media Encoder, then attach the rendered proxy using the output path.

Instructions

Create, attach, or toggle proxies for a project item. Note: 'create' only requests a proxy encode from Adobe Media Encoder and returns an unverified handoff. Independently verify the AME queue or output file before calling this tool again with action 'attach' and proxy_path set to the output_path you passed here. There is no single-call create-and-attach in Premiere's ExtendScript API.

Input Schema

TableJSON Schema

Name	Required	Description
`action`	Yes	Action to perform on proxies
`item_id`	Yes	Node ID or name of the project item
`proxy_path`	No	Path to an existing proxy file (required for 'attach')
`output_path`	No	Full output path for the proxy to be rendered to (required for 'create')
`preset_path`	No	Path to a proxy ingest preset (.epr) for 'create'. If omitted, the first preset found in Premiere's IngestPresets/Proxy folder is used.

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes	Whether the tool completed successfully.
`data`	No	Tool-specific result data when ok is true.
`tool`	Yes	The registered MCP tool name.
`error`	No	Failure detail when ok is false.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.14.4Aug 29, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "data": {
+      "description": "Tool-specific result data when ok is true."
+    },
+    "error": {
+      "description": "Failure detail when ok is false.",
+      "type": "string"
+    },
+    "ok": {
+      "description": "Whether the tool completed successfully.",
+      "type": "boolean"
+    },
+    "tool": {
+      "description": "The registered MCP tool name.",
+      "minLength": 1,
+      "type": "string"
+    }
+  },
+  "required": [
+    "ok",
+    "tool"
+  ],
+  "type": "object"
+}

Changed1 schema field changedv1.4.0Jul 27, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```

Changed3 schema fields changedv1.1.5Jul 19, 2026

addedInput schema / properties / output_path

Added value: +{
+  "description": "Full output path for the proxy to be rendered to (required for 'create')",
+  "type": "string"
+}

addedInput schema / properties / preset_path

Added value: +{
+  "description": "Path to a proxy ingest preset (.epr) for 'create'. If omitted, the first preset found in Premiere's IngestPresets/Proxy folder is used.",
+  "type": "string"
+}

changedInput schema / properties / proxy_path / description

Previous value: -"Path to proxy file (required for 'attach' action)"New value: +"Path to an existing proxy file (required for 'attach')"

First observedv1.1.1May 28, 2026

TDQS

A4.3/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

It reveals that create is asynchronous and unverified, requires external AME verification, and cannot be combined with attach in one call. These are non-obvious behavioral traits not visible in the annotations or schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences front-load the purpose and then add the critical workflow caveat without filler. Every sentence contributes necessary behavioral or sequencing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the non-obvious create/attach handoff and external verification requirement, and the output schema covers return values. It is nearly complete, but it leaves the toggle action's exact semantics and the boundary with detach_proxy unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema already documents all 5 parameters at 100% coverage, so the baseline is 3. The description adds cross-parameter semantics by linking output_path to proxy_path and specifying the preset_path default behavior, justifying a slightly higher score.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence names the exact operations (create, attach, toggle) and the target resource (project item), and the caveat clarifies the granular create/attach split. It does not explicitly contrast with sibling tools like has_proxy or detach_proxy, so it is clear but not fully sibling-differentiating.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives a concrete two-step recipe: call create, independently verify the AME queue or output file, then call attach with proxy_path set to the prior output_path. It does not state when to prefer has_proxy/detach_proxy or what toggle implies, so it lacks explicit alternatives and exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server