MCP Adobe Premiere Pro
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 | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_toolsA | Search the Premiere tool catalog with a BM25 natural-language query or a regex pattern, then call invoke_tool. Use this instead of expecting 280 editing tools in the MCP tool list. Empty query lists categories. Default 5 matches. |
| get_tool_schemaA | Return the full JSON input schema for one Premiere tool name from search_tools. After reading it, call invoke_tool. |
| invoke_toolA | Run a Premiere tool by exact name. Use after search_tools. Hosts that only advertise the small always-on set cannot call trim_clip etc. as top-level MCP tools. |
| verify_premiere_connectionA | Readiness check for Premiere Pro and the MCP Bridge. Call this before any editing tool. If Premiere is installed and not running, this launches it and waits for the CEP panel, which auto-starts the bridge. If it fails, tell the user the nextStep and do not retry other tools. |
| list_sequencesB | Lists all sequences in the current Premiere Pro project with their IDs, names, and basic properties. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| create_video_project | Guide to create a new video project from scratch |
| edit_music_video | Workflow for editing a music video with beat synchronization |
| color_grade_footage | Step-by-step color grading workflow |
| multicam_editing | Guide for multicam editing workflow |
| podcast_editing | Workflow for editing podcast episodes |
| social_media_content | Create content optimized for social media platforms |
| documentary_editing | Workflow for documentary film editing |
| commercial_editing | Guide for editing commercial advertisements |
| optimize_workflow | Tips for optimizing Premiere Pro workflow and performance |
| audio_cleanup | Guide for cleaning up and enhancing audio |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Current Project Information | Information about the currently open Premiere Pro project |
| Project Sequences | List of all sequences in the current project |
| Project Media | List of all media items in the current project |
| Project Bins | Organizational structure of bins in the current project |
| Timeline Clips | All clips currently on the timeline |
| Timeline Tracks | Information about video and audio tracks |
| Timeline Markers | Markers and their positions on the timeline |
| Available Effects | List of all available effects in Premiere Pro |
| Applied Effects | Effects currently applied to clips |
| Available Transitions | List of all available transitions in Premiere Pro |
| Export Presets | Available export presets and their settings |
| Project Metadata | Metadata information for the current project |
| Premiere Operating Instructions | Attach this before editing to give the model workflow and safety guidance for using the Premiere MCP server |
TDQS
Scored across 5 tools
Each tool occupies a distinct role in the bridge workflow: connection readiness, catalog search, schema lookup, tool invocation, and sequence listing. The search/schema/invoke tools form a clear sequence with explicit handoffs, so an agent should not confuse them.
All tool names follow lowercase snake_case with a verb_noun structure: verify_premiere_connection, search_tools, get_tool_schema, invoke_tool, list_sequences. There are no mixed conventions or vague overloaded verbs.
Five tools is well-scoped for a server that intentionally exposes a 280-tool catalog through a compact bridge layer rather than flooding the MCP tool list. Each tool is necessary for the discovery-and-invocation lifecycle.
The surface covers the full interaction loop: verify connection, search available tools, get a schema, invoke any cataloged tool, and list sequences directly. Since invoke_tool can execute any Premiere tool, there are no obvious missing operations for the server's stated purpose.