Premiere Pro Full MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| premiere_capabilitiesC | Report the local target, enabled authorities, backend readiness, action risk, and live-host verification boundaries. |
| premiere_apiC | Search or invoke official UXP, safe legacy DOM/QE capabilities, and semantic UI fallback through one risk-gated surface. |
| premiere_inspectC | Run a bounded read-only host, project, or sequence inspection action. |
| premiere_projectD | Run a typed project lifecycle action. |
| premiere_mediaC | Run a typed media import, relink, proxy, or metadata action. |
| premiere_timelineD | Run a typed sequence, track, clip, selection, marker, or transition action. |
| premiere_effects_audioC | Discover or apply typed effects, parameters, keyframes, transitions, and audio operations. |
| premiere_text_captionsC | Inspect or change graphics, transcripts, and captions through an advertised action. |
| premiere_exportC | Run confirmed frame, sequence, interchange, or AME export actions. |
| premiere_workspaceC | Control supported workspace, playback, panel, and history actions. |
| premiere_pluginsC | Inventory installed effects/extensions or invoke a versioned semantic plugin adapter. |
| premiere_cloudC | Inspect or invoke approved signed-in Adobe cloud workflows without extracting credentials. |
| premiere_operationsD | Preview and confirm R2/R3 work, apply an exact request, inspect operation status, or report cancellation/undo boundaries. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| premiere-capabilities | Current backend availability, authorities, and action support states. |
TDQS
Scored across 13 tools
Each tool targets a distinct domain—capabilities, API, inspection, project, media, timeline, effects/audio, text/captions, export, workspace, plugins, cloud, and operations—with no obvious overlaps in purpose. The descriptions clearly delineate what each tool handles, making selection straightforward for an agent.
All tools follow a consistent 'premiere_' prefix followed by a specific noun, using snake_case throughout. This pattern is uniform and predictable, making it easy for an agent to infer tool purposes and group related actions.
With 13 tools, the server falls comfortably within the ideal 3-15 range. Each tool represents a major functional area of Premiere Pro, and none seem redundant or superfluous—every tool earns its place in the set.
The tool surface covers the full lifecycle of Premiere Pro work: project management, media handling, timeline editing, effects/audio, text/captions, export, workspace control, plugin support, cloud workflows, and operation management. This appears to cover all core editing and production needs, with no obvious gaps that would cause agent failures.