Premiere Connector
Related Servers
Alternatives to Premiere Connector
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables Claude to drive Adobe Premiere Pro directly through natural-language requests, supporting import, timeline editing, markers, effects, transitions, and export.6235,090 npmMIT
- 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.-
- 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.5,090 npm39MIT
- AlicenseNot gradedqualityAmaintenanceEnables 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
- FlicenseNot gradedqualityAmaintenanceEnables Claude to read, edit, and generate real Final Cut Pro timelines from exported FCPXML — trimming, splitting, silence removal, markers, roles, keyframes, transcript-based editing, and cross-NLE export — with journaled, undoable writes. It can also push an FCPXML straight into a running Final Cut Pro with zero clicks and render the timeline inline as structured data.-
- 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
TDQS
Scored across 158 tools
Most tools target clearly distinct operations, but with 158 tools there are several confusing clusters: add_captions/import_captions/add_text_captions/add_text, the many mogrt tools (place_mogrt_with_media/replace_mogrt_media/import_mogrt/import_library_graphic), and elevenlabs_generate_speech vs elevenlabs_voice_lines. Descriptions do disambiguate most of these, but the sheer volume of overlapping-sounding high-level tools makes misselection plausible.
Strongly consistent snake_case with verb_noun patterns (get_, set_, add_, remove_, export_). A few noun-first deviations (scene_edit_detection, auto_reframe_sequence) and the elevenlabs_ prefixed tools break the pattern slightly, but overall it is predictable.
158 tools is far beyond an appropriate tool count for any single server; it should be decomposed (e.g. project, timeline, effects, captions, export, integrations) into smaller servers. The extreme number hurts discoverability even when each tool is well-scoped.
Coverage is exhaustive: project lifecycle, sequences, clips (insert/overwrite/trim/slip/slide/ripple), effects, keyframes, transforms, markers, audio mixing, captions, motion graphics, proxies, exports, and even an ExtendScript escape hatch for gaps. Essentially no dead ends remain for Premiere automation.