Premiere Pro MCP Server
Related Servers
Alternatives to Premiere Pro MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseCqualityAmaintenanceOperates local Adobe Premiere Pro projects through MCP, exposing 284 tools for AI-driven video editing including timeline editing, effects, exports, and guided assembly workflows.28417 npmMIT
- FlicenseCqualityBmaintenanceEnables AI agents to control Adobe Premiere Pro timelines via MCP, offering transcript search, marker management, timeline editing (cuts, cleanup), and export capabilities through 277 tools.277-
- AlicenseNot gradedqualityDmaintenanceEnables control of Adobe Premiere Pro through Claude using over 170 tools for editing, effects, and timeline management. It supports advanced project operations, automated captions, and AI-generated voiceovers via ElevenLabs integration.5,325 npm35MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to control video editing software (剪映/CapCut and Adobe Premiere Pro) through a unified interface, supporting operations like material import, clip splitting, subtitle addition, effects, transitions, audio mixing, and export.10MIT
- AlicenseNot gradedqualityCmaintenanceControl Adobe Premiere Pro from AI agents via ExtendScript, enabling media import, sequence creation, effect application, media export, and custom scripting.23 npmMIT
- AlicenseAqualityCmaintenanceMakes Claude a real operator for Adobe Premiere Pro 2025, providing 59 tools to control projects, timelines, media, exports, and even create cinematic intros with beat detection and style presets.59MIT
TDQS
Scored across 389 tools
With 389 tools, many read/inspect/analyze/plan tools overlap heavily, such as get_active_sequence, get_full_sequence_info, get_sequence_structure, and get_timeline_summary, or capture_frame versus export_frame and the many export_*_review_frames variants. Detailed descriptions help, but the sheer number of near-parallel tools makes misselection likely.
Tool names are all snake_case and generally readable, but verbs are inconsistently chosen across get_, inspect_, read_, analyze_, check_, validate_, review_, plan_, and preview_. The convention is not chaotic, but it is too mixed to be fully predictable.
389 tools is an extreme mismatch even for a complex domain like Premiere Pro. The surface is far beyond the typical well-scoped range and creates a severe discoverability and selection burden.
The server covers a very broad Premiere lifecycle, including project, sequence, timeline, effects, exports, metadata, and planning workflows. However, several tools are explicitly unavailable or dead ends, such as speed_change, reverse_clip, apply_lut, add_text_overlay, and import_edl, so coverage is not cleanly complete.