Premiere Pro MCP
Related Servers
Alternatives to Premiere Pro MCP
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceEnables AI assistants to inspect and organize Adobe Premiere Pro projects, edit timelines with frame-accurate cuts and trims, animate motion and opacity keyframes, and trigger exports through natural language.41MIT
- AlicenseAqualityBmaintenanceEnables AI clients to drive local video editing projects through a CEP bridge, covering media ingest, sequence and timeline editing, effects, keyframes, captions, markers, audio, color, and exports across hundreds of discoverable tools. Ships context resources, guided prompts, and higher-level assembly workflows for agent-driven editing.53,943 npmMIT
- AlicenseAqualityAmaintenanceLets AI assistants work inside a running Adobe Premiere Pro: ~440 readback-verified operations behind nine tools. Every UI language Premiere ships, and it sees the frame: draws Object Masks on the people or parts it sees (click or lasso, add/subtract, tracking; macOS), checks keyframes frame by frame. Large skills library; built for Generative Extend, Generative Media, Object Mask, Enhance Speech.491,241 npmApache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to edit talking-head videos locally by transcribing footage, applying validated edit operations like cutting fillers and silences, adding zooms, captions, looks and branding, and checking results with rendered previews. Agents can also read pinned editor feedback notes with annotated frames, resolve them, and export MP4, SRT or OTIO while the user watches changes live.52 npm1MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to drive a desktop video editor through MCP, providing the same editing operations as the user — placing, trimming, rippling, grading, captioning, and exporting — on the actual project with local rendering.7GPL 3.0
- AlicenseNot gradedqualityCmaintenanceEnables MCP-compatible AI assistants to control Adobe Premiere Pro through natural language, automating project and media management, timeline editing, color and audio adjustments, titles and markers, and batch exports via a local bridge.6,954 npm1MIT
TDQS
Scored across 289 tools
With 289 tools there are many overlapping clusters: multiple info getters (get_clip_properties, get_full_clip_info, get_qe_clip_info, get_project_item_info, get_full_project_overview), selection tools, effect tools, transition/marker/import variants, and generic 'expanded operation' tools whose names give little separation. An agent cannot reliably choose among them, so boundaries are severely unclear.
Names are broadly snake_case, but consistency breaks down: batch prefix vs suffix (batch_add_transitions vs add_to_timeline_batch/set_clip_properties_batch), noun-first or single-word names (scene_edit_detection, undo, ping, multiple_undo), and many generic expanded-operation names. Still readable, but mixed conventions.
289 tools far exceeds any reasonable scoped MCP server and dwarfs the 50+ threshold. The domain is broad, but the count is an extreme mismatch.
The surface covers project, sequence, clip, effect, marker, track, import/export, and metadata lifecycles comprehensively, with few obvious functional gaps. Some tools are explicit dead ends (caption read, EDL import, render queue status), so minor gaps remain.