A
licenseC
qualityA
maintenanceOperates local Adobe Premiere Pro projects through MCP, exposing 284 tools for AI-driven video editing including timeline editing, effects, exports, and guided assembly workflows.
284
12 npm
MIT
scout-premiere-mcp
by tro2789
Related Servers
Alternatives to scout-premiere-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityAmaintenanceEnables AI assistants to fully control Adobe Premiere Pro through 269 tools across 28 modules for video editing tasks like importing media, editing timelines, applying effects, and exporting.3822,468 npm282MIT
- 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.3GPL 3.0
- AlicenseBqualityCmaintenanceEnables AI agents to programmatically edit videos via FFmpeg, providing tools for probing, trimming, concatenating, timeline composition, LUT generation/application, rendering, and edit verification over MCP.16MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI models to fully automate and control the OpenCut Video Editor through a comprehensive set of MCP tools for timeline manipulation, scene management, media handling, and rendering.43 npm7MIT
- 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
C2.1/5.0
Scored across 277 tools
Disambiguation1/5
There is massive overlap between tools: multiple marker tools (place_markers vs add_marker vs list_markers vs remove_markers vs delete_marker), several sequence-info getters (get_full_sequence_info, get_sequence_structure, get_timeline_summary, get_sequence_settings), and many 'expanded operation' wrappers that duplicate named tools (set_clip_speed_qe vs speed_change, get_qe_clip_info vs get_clip_properties). An agent would frequently misselect.
Naming Consistency3/5
Most tools follow snake_case verb_noun naming, but conventions are mixed: list vs get, delete vs remove, add vs place, and odd names like set_clip_speed_qe, get_qe_clip_info, execute_extendscript break the pattern. The naming is readable but not uniform across the set.
Tool Count1/5
With 277 tools, the surface is far beyond a coherent scope. Many are redundant auto-generated wrappers ('Premiere Pro expanded operation') that duplicate first-class tools, making selection overwhelming and undermining the server's purpose.
Completeness3/5
The tool surface covers a huge range of Premiere capabilities, and the core Scout workflow (transcript, word search, markers, cleanup) is complete. However, several tools are documented stubs (import_edl, read_sequence_captions, get_render_queue_status), leaving some dead ends and making coverage uneven.
Maintenance
ActivityMaintained
ResponsivenessNo issues