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.28444 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-
- 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
- AlicenseAqualityAmaintenanceLets AI assistants work inside a running Adobe Premiere Pro through nine tools covering ~440 verified operations — cutting, trimming, effects, keyframes, captions, reframing and export, each write read back to confirm it. Works with every UI language Premiere ships, comes with a large skills library and is built for Generative Extend, Generative Media, Object Mask and Enhance Speech.49Apache 2.0
- AlicenseCqualityDmaintenanceEnables 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.1806,095 npm41MIT
- 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
TDQS
Scored across 444 tools
There is heavy functional overlap across large families: sequence inspection (get_active_sequence, get_sequence_structure, get_full_sequence_info, inspect_timeline_snapshot, get_timeline_summary, inspect_sequence_review_report), export (export_sequence, export_sequence_job_start, add_to_render_queue, encode_project_item, encode_file, export_and_verify), markers (add_marker, add_marker_to_project_item, add_markers_batch, plus several plan_*_markers), and clip property setters (set_clip_properties, set_clip_properties_batch, set_clip_scale/position/rotation/opacity/anchor_point). The extremely verbose descriptions do try to steer the agent ("use X instead of Y", "distinct from..."), which prevents a 1, but with 444 tools an agent will routinely misselect.
Most names are snake_case and many follow verb_noun (get_clip_properties, create_sequence, remove_transition), but the set mixes many verb families (get/inspect/preview/plan/review/verify/apply/build/validate) and includes noun-verb or bare-noun outliers such as speed_change, scene_edit_detection, match_frame, freeze_frame, auto_reframe_sequence, can_execute, and ping. Readable overall, but no single predictable pattern an agent can rely on.
444 tools for one server is an extreme mismatch with any reasonable agent-facing surface; discovery, selection, and prompt budget all break down. Even granting the breadth of Premiere automation, the count includes many near-duplicate inspection, planning, preview, and explicitly unavailable tools that do not earn separate slots.
Coverage of the Premiere domain is extraordinarily broad (project, bins, sequences, timeline edits, effects, keyframes, markers, captions, export, AE handoff, interchange, analysis), so few core workflows are missing. However, a substantial number of tools are declared permanently unavailable dead ends (speed_change, set_clip_speed_qe, reverse_clip, apply_lut, add_text_overlay, nest_clips, export_aaf, set_poster_frame, replace_clip_media, import_edl), and caption readback is acknowledged as unreliable, so the surface is not free of blocked paths.