Premiere Pro MCP for Antigravity
Related Servers
Alternatives to Premiere Pro MCP for Antigravity
No user-submitted related servers found.
Related Servers
- 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.5,512 npmMIT
- AlicenseAqualityDmaintenanceEnables Claude to drive Adobe Premiere Pro directly through natural-language requests, supporting import, timeline editing, markers, effects, transitions, and export.6235,512 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to programmatically inspect projects, create compositions and layers, apply effects, animate properties, and manage render jobs in Adobe After Effects through natural language.57 npmMIT
- AlicenseCqualityCmaintenanceGives an AI client local control over Adobe Premiere Pro, letting it inspect footage frame-by-frame to find the best moments, assemble and trim edits on the timeline, render animated title cards, review its own work, and export the finished video. Vision and editing tools run entirely on the user's own computer, with nothing sent to the publisher.289MIT
- FlicenseNot gradedqualityBmaintenanceEnables prompt-driven video editing in Adobe Premiere Pro, allowing Claude to transcribe footage, decide cuts, build motion graphics, and assemble timelines via natural language.-
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to read, edit, and export real video projects with a full multitrack timeline, effects, captions, and export capabilities.2-
TDQS
Scored across 41 tools
Most tools have distinct resource+action targets, but the clip-inspection cluster (read_clip_properties, get_clip_information, list_clip_components, list_component_properties) overlaps heavily, forcing agents to guess which read path to use. The descriptions help but the boundaries between these tools remain fuzzy.
The set predominantly follows a verb_noun snake_case pattern (get_, list_, set_, export_, etc.). Minor deviations like premiere_ping and premiere_health_check, plus read_ vs get_ for similar read operations, keep it from being fully consistent.
41 tools is well beyond the 25+ threshold for 'too many' and feels heavy for the apparent scope. Several capabilities could be consolidated (e.g., five separate motion/opacity/blend setters, six keyframe tools) without losing functionality.
The surface covers project, sequence, media, timeline editing, keyframes, and export workflows quite thoroughly. Minor gaps remain for direct audio operations (volume/pan) and adding/removing effects, but the generic property setter and other tools provide workarounds.