Skip to main content
Glama
ibintec

Premiere Pro MCP

by ibintec
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Premiere Pro MCP

No user-submitted related servers found.

    Related Servers

    • cutroom

      0xpratzyy
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to edit talking-head videos locally by transcribing footage, applying validated edit operations like cutting fillers and silences, adding zooms, captions, looks and branding, and checking results with rendered previews. Agents can also read pinned editor feedback notes with annotated frames, resolve them, and export MP4, SRT or OTIO while the user watches changes live.
      1
      MIT

    • artdaddy

      art-daddy
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to drive a desktop video editor through MCP, providing the same editing operations as the user — placing, trimming, rippling, grading, captioning, and exporting — on the actual project with local rendering.
      7
      GPL 3.0

    • 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.
      5,512 npm
      MIT

    • PremierePilot

      shotbyx-dev
      A
      license
      Not graded
      quality
      B
      maintenance
      A Windows-first MCP server that lets an AI chat client drive Adobe Premiere Pro and After Effects with natural-language prompts, enabling project management, media import, timeline/composition building, animation, effects, and export from anywhere.
      1
      MIT
    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.1/5.0

    Scored across 289 tools

    Disambiguation1/5

    With 289 tools there are many overlapping clusters: multiple info getters (get_clip_properties, get_full_clip_info, get_qe_clip_info, get_project_item_info, get_full_project_overview), selection tools, effect tools, transition/marker/import variants, and generic 'expanded operation' tools whose names give little separation. An agent cannot reliably choose among them, so boundaries are severely unclear.

    Naming Consistency3/5

    Names are broadly snake_case, but consistency breaks down: batch prefix vs suffix (batch_add_transitions vs add_to_timeline_batch/set_clip_properties_batch), noun-first or single-word names (scene_edit_detection, undo, ping, multiple_undo), and many generic expanded-operation names. Still readable, but mixed conventions.

    Tool Count1/5

    289 tools far exceeds any reasonable scoped MCP server and dwarfs the 50+ threshold. The domain is broad, but the count is an extreme mismatch.

    Completeness4/5

    The surface covers project, sequence, clip, effect, marker, track, import/export, and metadata lifecycles comprehensively, with few obvious functional gaps. Some tools are explicit dead ends (caption read, EDL import, render queue status), so minor gaps remain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources