A
licenseB
qualityD
maintenanceAn unofficial MCP-compatible server that enables advanced automation, querying, and remote control of Adobe Premiere Pro projects for power users, workflow automation, and AI integration.
15
14
MIT
adobe-premiere-cc-mcp
by MarvelCollin
Related Servers
Alternatives to adobe-premiere-cc-mcp
No user-submitted related servers found.
Related Servers
- AlicenseCqualityCmaintenanceMCP server for controlling Adobe After Effects, enabling AI assistants to create compositions, manage layers, and animate properties.13104 npmMIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that exposes the complete DaVinci Resolve scripting API, enabling AI assistants to control DaVinci Resolve programmatically with over 440 tools for project management, timeline editing, color grading, rendering, and more.8MIT
- AlicenseCqualityCmaintenanceAn MCP server that enables AI assistants to control Adobe After Effects with 70+ tools for compositing, animation, effects, and motion graphics.6813 npmMIT
- AlicenseNot gradedqualityDmaintenanceProvides MCP servers for AI-driven video editing. Enables offline editing of CapCut drafts and remote control of Adobe Premiere Pro via UXP plugin, with shared media analysis for beat detection and transcription.MIT
- AlicenseCqualityFmaintenanceA Model Context Protocol (MCP) server for Adobe After Effects that enables AI assistants and other applications to control After Effects through a standardized protocol.3213104 npm619MIT
TDQS
A3.8/5.0
Scored across 41 tools
Disambiguation5/5
Each tool has a clearly distinct purpose, with detailed descriptions that prevent confusion. Even similar tools like get_clip vs get_timeline operate at different scopes (single clip vs whole sequence), and grade_clips vs set_lumetri target group vs individual clips. No two tools appear to do the same thing.
Naming Consistency4/5
The vast majority of tools follow a consistent verb_noun pattern (get_, set_, list_, create_, delete_, add_, etc.). Minor exceptions like 'ping' and 'contact_sheet' deviate from this pattern, but they are easily recognizable and do not significantly harm overall consistency.
Tool Count2/5
With 41 tools, the server is heavily overloaded. While Premiere is a complex application, this many tools in one MCP server makes it unwieldy and could benefit from being split into focused sub-servers (e.g., editing, effects, export). The number falls well beyond the 'too many' threshold of 25.
Completeness4/5
The tool set covers the core editing workflow well: project management, sequence handling, timeline operations, clip properties, effects, grading, markers, playhead, export, and saving. Minor gaps exist, such as no generic effect property setter (only specific ones like set_lumetri and set_scale) and limited transition editing, but run_script provides an escape hatch for these cases.
Maintenance
ActivitySlowing
ResponsivenessNo issues