Skip to main content
Glama
OsirisMedici

Osiris Premiere MCP

by OsirisMedici
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Osiris Premiere 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,211 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

    • 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

    B3/5.0

    Scored across 389 tools

    Disambiguation2/5

    With 389 tools there is heavy functional overlap: many near-duplicate read/getters (get_sequence_structure vs get_full_sequence_info vs get_active_sequence vs inspect_sequence_structure), several insertion/edit routes (add_to_timeline, insert_from_source, overwrite_clip, overwrite_from_source, add_to_timeline_batch), and dozens of 'plan_/preview_/review_' tools that blur together. Additionally a large set of tools are explicitly 'Unavailable' (add_text_overlay, apply_lut, speed_change, reverse_clip, nest_clips, set_poster_frame, import_edl, relink_media), which adds further ambiguity about what an agent should actually call.

    Naming Consistency4/5

    Names are overwhelmingly consistent snake_case verb_noun patterns (get_, set_, list_, add_, remove_, create_, delete_, preview_, plan_), and the prefix families (plan_/preview_/review_/inspect_) are used coherently. Minor deviations exist (e.g., speed_change, color_correct, undo/redo as bare verbs) but the convention is largely predictable.

    Tool Count1/5

    389 tools is an extreme mismatch for any coherent surface and far exceeds the 25+ threshold; the breadth guarantees the agent cannot reasonably select among them. Even a rich NLE-automation domain does not justify this many entry points.

    Completeness3/5

    Coverage of the Premiere automation domain is very broad (project, timeline, effects, keyframes, export, captions, markers, review/QC), but several core operations are deliberate dead-ends (masks not supported, speed/reverse unavailable, LUT application impossible, nesting unavailable, EDL import refused). These are notable gaps that agents must work around, though much of the surface is genuinely complete.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources