Osiris Premiere MCP
Related Servers
Alternatives to Osiris Premiere MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables 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.54,494 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to perform validated, authenticated project, timeline, media, marker, and export-queue operations in Adobe's video editor through a local UXP panel. It supports safe previews and explicit approval for destructive actions.5,090 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables 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,090 npm1MIT
- AlicenseNot gradedqualityAmaintenanceEnables 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.7GPL 3.0
- AlicenseCqualityAmaintenanceConnects 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.317MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP-compatible clients to control a local video editor through authenticated stdio commands for clips, effects, text, subtitles, camera, graphics, keyframes, audio, and export.MIT
TDQS
Scored across 389 tools
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.
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.
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.
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.