MCP Adobe Premiere Pro
Related Servers
Alternatives to MCP Adobe Premiere Pro
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.2,663 npm1MIT
- 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.-
- AlicenseAqualityDmaintenanceEnables Claude to drive Adobe Premiere Pro directly through natural-language requests, supporting import, timeline editing, markers, effects, transitions, and export.6232,663 npmMIT
- 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
- AlicenseNot gradedqualityDmaintenanceEnables 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.2,663 npm39MIT
- AlicenseNot gradedqualityCmaintenanceControl Adobe Premiere Pro from AI agents via ExtendScript, enabling media import, sequence creation, effect application, media export, and custom scripting.23 npmMIT
TDQS
Scored across 5 tools
Each tool occupies a distinct role in the bridge workflow: connection readiness, catalog search, schema lookup, tool invocation, and sequence listing. The search/schema/invoke tools form a clear sequence with explicit handoffs, so an agent should not confuse them.
All tool names follow lowercase snake_case with a verb_noun structure: verify_premiere_connection, search_tools, get_tool_schema, invoke_tool, list_sequences. There are no mixed conventions or vague overloaded verbs.
Five tools is well-scoped for a server that intentionally exposes a 280-tool catalog through a compact bridge layer rather than flooding the MCP tool list. Each tool is necessary for the discovery-and-invocation lifecycle.
The surface covers the full interaction loop: verify connection, search available tools, get a schema, invoke any cataloged tool, and list sequences directly. Since invoke_tool can execute any Premiere tool, there are no obvious missing operations for the server's stated purpose.