Skip to main content
Glama
mike7418

MCP Bridge for Adobe Premiere Pro

by mike7418
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to MCP Bridge for Adobe Premiere Pro

No user-submitted related servers found.

    Related Servers

    • Osiris Premiere MCP

      OsirisMedici
      A
      license
      B
      quality
      B
      maintenance
      Connects an MCP client to a locally installed Adobe Premiere Pro so editors can inspect projects and run structured editing operations—project creation and opening, linked audio/video insertion and trimming, cutting, SRT caption rendering, and native MP4 export—instead of navigating the UI repeatedly. Capability profiles limit access to inspection, editing, export, or filesystem authority as needed for each task.
      389
      2,663 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

    • 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
    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

    A4.1/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a distinct purpose: search_tools for discovery, get_tool_schema for detailed inspection, invoke_tool for execution, verify_premiere_connection for readiness, and list_sequences as a direct convenience operation. The only slight overlap is list_sequences being reachable via search/invoke, but it's clearly a shortcut and not ambiguous.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern: search_tools, get_tool_schema, invoke_tool, verify_premiere_connection, list_sequences. No deviations in style or convention.

    Tool Count5/5

    Five meta-tools are well-scoped for a bridge that wraps 280 underlying Premiere tools. The small set avoids overwhelming the agent while covering discovery, inspection, invocation, and connection checks.

    Completeness5/5

    The surface covers the full lifecycle: verify connection, search tools, inspect schema, invoke tools, and list sequences. No obvious gaps for the stated purpose of bridging to Premiere Pro's tool catalog.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources