premiere-pro-mcp
Related Servers
Alternatives to premiere-pro-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables editing Adobe Premiere Pro projects and sequences from Claude Code through local pr_* tools, including media import, clip placement and properties, effects and LUT copying, frame/video export, and batched edit plans.MIT
- AlicenseCqualityAmaintenanceConnects Claude to a running Adobe Premiere Pro via a CEP bridge, exposing hundreds of low-level project, sequence, clip, effect and export tools plus studio-grade workflows such as proxy generation, rough cuts from slate calls, text-based shot search, beat-driven cuts, per-scene colour, captions, aspect versions and delivery exports. All processing stays on the local Mac, with speech, vision and beat analysis handled by a companion media engine.317MIT
- FlicenseAqualityDmaintenanceEnables Claude to drive Adobe Premiere Pro directly through natural-language requests, supporting import, timeline editing, markers, effects, transitions, and export.23-
- AlicenseCqualityBmaintenanceEnables Claude to control Adobe Premiere Pro directly, covering project and sequence management, batch timeline assembly with in/out points, transforms and keyframes, effect presets, titles, audio, markers, exports, and frame previews returned as images. It also offers consolidated selectors, media analysis via FFmpeg, and a single batch call for running many operations in one round-trip.741MIT
- 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.1MIT
- FlicenseNot gradedqualityDmaintenanceEnables prompt-driven video editing in Adobe Premiere Pro, allowing Claude to transcribe footage, decide cuts, build motion graphics, and assemble timelines via natural language.-
TDQS
Scored across 445 tools
The set contains many near-duplicate or overlapping tools: get_project_info, get_full_project_overview, get_premiere_state; get_active_sequence, get_full_sequence_info, get_sequence_structure; list_sequences, get_sequence_count; numerous preview/apply pairs; and many inspect/get tools for project items, clips, metadata, and timelines. An agent would struggle to choose the right tool without extensive trial and error.
Most names are snake_case, but conventions are mixed: verb_noun (get_clip_properties), noun_verb (speed_change, color_correct), bare verbs (undo, redo, ping), suffixes like _qe/_uxp/_cep, and many batch/preview/apply variants. The naming is still readable but not predictable enough for 445 tools.
445 tools is an extreme mismatch for a coherent MCP surface, far beyond practical selection and comprehension. Even for a complex application like Premiere Pro, this count creates an unmanageable tool namespace with many redundant, experimental, or unavailable entries.
The surface is exceptionally broad, covering project, sequence, clip, effect, keyframe, marker, export, QC, interchange, and workflow operations. However, some tools are explicitly unavailable or fail by design, and the sheer number of options makes completeness hard to assess without dead ends.