Skip to main content
Glama
compimprove

Adobe Premiere Pro MCP

by compimprove
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Adobe Premiere Pro MCP

No user-submitted related servers found.

    Related Servers

    • MCP Bridge for Adobe Premiere

      mike7418
      A
      license
      A
      quality
      B
      maintenance
      Enables MCP clients to operate local Adobe Premiere Pro projects, covering media ingest, bins, sequence and timeline editing, transitions, effects, keyframes, captions, markers, metadata, proxies, multicam, color, audio, and exports through 283 discoverable tools, 13 context resources, and 10 guided prompts. A bundled CEP panel provides the supported production bridge, with read-only connection verification and higher-level workflows for assembling product spots and motion-graphics demos.
      5
      1,433 npm
      MIT

    • PremiereProMCP

      au-yong
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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 npm
      1
      MIT

    • YoloCut

      Hhz0823
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents and MCP clients to programmatically edit video projects on a local desktop editor, with 119 tools for multitrack editing, effects, captions, audio, and batch auto-editing, producing reviewable and reversible real timeline edits.
      AGPL 3.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.2/5.0

    Scored across 284 tools

    Disambiguation2/5

    With 284 tools there is substantial overlap: check_offline_media/get_offline_media, add_track/add_tracks, import_sequences/import_sequences_from_project, set_clip_properties and the many set_clip_* granular tools, plus multiple get_clip_info/get_item_info variants. An agent would struggle to reliably pick the intended tool for many editing operations.

    Naming Consistency4/5

    The vast majority of tools follow a clean snake_case verb_noun pattern like list_sequences, create_sequence, set_clip_opacity, and export_frame. A few oddballs like ping, undo, redo, and get_premiere_state break the pattern, but overall naming is predictable.

    Tool Count1/5

    284 tools is an extreme count for a single MCP server, far beyond the 3-15 tool range that keeps an agent's tool-selection surface manageable. The server would be much more coherent split into focused servers for project management, timeline editing, effects/color, audio, captions, and export.

    Completeness4/5

    The domain coverage is remarkably broad: project lifecycle, media import, sequence creation, timeline editing, effects, transitions, audio, color, captions, markers, and export are all represented. Minor gaps exist, such as unsupported EDL import, no real caption reading API, and render queue status being only guidance rather than live telemetry.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources