Skip to main content
Glama

Related Servers

Alternatives to Premiere Pro MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      C
      quality
      B
      maintenance
      Enables Claude to control Adobe Premiere Pro directly, covering project and sequence management, batch timeline assembly with in/out points, transforms and keyframes, effect presets, titles, audio, markers, exports, and frame previews returned as images. It also offers consolidated selectors, media analysis via FFmpeg, and a single batch call for running many operations in one round-trip.
      74
      1
      MIT
    • A
      license
      C
      quality
      B
      maintenance
      Enables Claude to edit Adobe Premiere Pro timelines through natural language, with roughly 150 tools for cutting, trimming, speed changes, effects, keyframes, transitions, titles, captions, audio, markers and exports. It can also render frames so edits can be visually verified, and ships with a skill encoding a working order and rules learned from real projects.
      158
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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

    TDQS

    C2.7/5.0

    Scored across 180 tools

    Disambiguation3/5

    Most tools are context-specific, but with 180 tools there is meaningful overlap: export_sequence vs export_direct, several text/caption/MOGRT insertion tools, and multiple in/out setters across project items, source monitor, sequences, and work areas. Descriptions usually clarify the intended context, but an agent can still hesitate among several plausible choices.

    Naming Consistency4/5

    The surface is overwhelmingly snake_case and mostly follows a verb_noun pattern (get_clip_info, add_marker, remove_effect). There are minor deviations like razor_clip, slip_clip, play, stop, and go_to_* forms, but the convention remains readable and predictable overall.

    Tool Count1/5

    180 tools is far beyond a manageable set for a single MCP server and creates severe discoverability and selection overhead. Even for a complex domain like video editing, this should be decomposed into smaller focused servers or heavily consolidated.

    Completeness5/5

    The surface is extremely comprehensive for Premiere Pro: project/media management, sequences, timeline editing, effects, audio, markers, captions, MOGRTs, export formats, playback, metadata, proxies, and an ExtendScript escape hatch are all covered. There are few obvious lifecycle gaps for core editing workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data