Skip to main content
Glama
tro2789

scout-premiere-mcp

by tro2789
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to scout-premiere-mcp

No user-submitted related servers found.

    Related Servers

    • 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,325 npm
      MIT

    • 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,330 npm
      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

    C2.1/5.0

    Scored across 277 tools

    Disambiguation1/5

    There is massive overlap between tools: multiple marker tools (place_markers vs add_marker vs list_markers vs remove_markers vs delete_marker), several sequence-info getters (get_full_sequence_info, get_sequence_structure, get_timeline_summary, get_sequence_settings), and many 'expanded operation' wrappers that duplicate named tools (set_clip_speed_qe vs speed_change, get_qe_clip_info vs get_clip_properties). An agent would frequently misselect.

    Naming Consistency3/5

    Most tools follow snake_case verb_noun naming, but conventions are mixed: list vs get, delete vs remove, add vs place, and odd names like set_clip_speed_qe, get_qe_clip_info, execute_extendscript break the pattern. The naming is readable but not uniform across the set.

    Tool Count1/5

    With 277 tools, the surface is far beyond a coherent scope. Many are redundant auto-generated wrappers ('Premiere Pro expanded operation') that duplicate first-class tools, making selection overwhelming and undermining the server's purpose.

    Completeness3/5

    The tool surface covers a huge range of Premiere capabilities, and the core Scout workflow (transcript, word search, markers, cleanup) is complete. However, several tools are documented stubs (import_edl, read_sequence_captions, get_render_queue_status), leaving some dead ends and making coverage uneven.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources