Skip to main content
Glama
MCP Bridge for Adobe Premiere Pro

MCP Bridge for Adobe Premiere Pro

by takafumi-dev

Related Servers

Alternatives to MCP Bridge for Adobe Premiere Pro

No user-submitted related servers found.

    Related Servers

    • 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
      MIT
    • A
      license
      Not graded
      quality
      B
      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.
      8
      GPL 3.0
    • A
      license
      C
      quality
      A
      maintenance
      Connects 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.
      317
      MIT

    TDQS

    A3.9/5.0

    Scored across 5 tools

    Disambiguation4/5

    The search_tools → get_tool_schema → invoke_tool pipeline is clearly delineated, and verify_premiere_connection is unmistakably a readiness check. The only friction is list_sequences: it is a concrete top-level tool that duplicates something presumably also reachable through the 280-tool catalog, so an agent may wonder whether to use it directly or search for it.

    Naming Consistency5/5

    All five tools use snake_case with a leading verb (list_, search_, get_, invoke_, verify_), so the pattern is predictable and readable. Minor verb-phrase length variation in verify_premiere_connection does not break consistency.

    Tool Count5/5

    Five tools is exactly right for a bridge: a deliberately small always-on surface that fronts a large catalog via search and invoke. Each tool earns its place in the discover-schema-invoke-verify loop.

    Completeness4/5

    The proxy pattern plus empty-query category listing means any of the 280 editing tools is reachable, and connection readiness is covered. The surface is slightly asymmetric — list_sequences is exposed as a lone convenience shortcut with no equivalent shortcuts or a direct 'list all catalog tool names' operation — but agents can work around this.