OpenEdit
Related Servers
Alternatives to OpenEdit
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables Claude Desktop, Cursor, and other MCP clients to edit local video through FFmpeg and whisper.cpp, including trimming, silence and retake removal, transcription, captions, undo/redo, and export to Final Cut Pro, DaVinci Resolve, or Premiere Pro.1,067 npm14MIT
- AlicenseNot gradedqualityBmaintenanceValmera, the world’s most advanced AI video editor, edits your recorded footage through Claude, ChatGPT or another MCP client. Place your own B-roll on a spoken word, correct a caption, cut or reframe a shot, review the preview and export an MP4. Watch both four-second edits in the README. Hosted editing requires an eligible paid Valmera plan.MIT
- FlicenseNot gradedqualityDmaintenanceEnables prompt-driven video editing in Adobe Premiere Pro, allowing Claude to transcribe footage, decide cuts, build motion graphics, and assemble timelines via natural language.-
- FlicenseNot gradedqualityAmaintenanceEnables chat-driven video editing by letting an MCP host analyze raw clips and produce finished, beat-synced montages with matched music, subtitles, transitions, and picture-in-picture, all previewed as a timeline digest before rendering. It runs locally through agents such as Claude Code, Codex, Hermes, and OpenCode.-
- AlicenseNot gradedqualityDmaintenanceAn MCP server that gives Claude a conversational video-editing toolkit — trim, crop, color grade, caption, beat-sync, stabilize, and more — built on ffmpeg, faster-whisper, and yt-dlp, with optional DaVinci Resolve and CapCut integration.2MIT
- FlicenseNot gradedqualityNot gradedmaintenanceEnables Claude to read, edit, and generate real Final Cut Pro timelines from exported FCPXML, covering trimming, splitting, silence removal, markers, transcript-based editing, keyframes and speed ramps, cross-NLE export, and pushing edits into a running Final Cut Pro. Every write is journaled with its sha256 and reversible, and timelines can be rendered visually for review before delivery.-
TDQS
Scored across 19 tools
Most tools target a clearly distinct step of the editing pipeline (inspect → transcribe → plan → apply → embellish → render), and descriptions explicitly disambiguate close pairs like add_zooms vs auto_zooms and render vs render_motion. The only mild overlap is around captions (make_captions adds captions in the editor, render_caption_overlay bakes a transparent overlay video), which descriptions mostly resolve but an agent could still pause over.
The dominant pattern is consistent snake_case verb_noun (find_silences, plan_cuts, apply_cuts, add_markers, place_clips, import_media). A few deviations exist — verb-only names (transcribe, render) and noun-only names (editor_status, motion_templates) — but they remain readable and predictable within the set.
19 tools is on the heavy side but each maps to a distinct capability in a genuinely broad workflow (editor selection, analysis, cut planning, captions, zooms, media placement, rendering, motion graphics). Nothing looks redundant enough to be a filler tool, though a couple of render variants push the surface toward the upper bound.
The lifecycle is well covered end-to-end: session/host setup, media probing, transcription, silence/filler analysis, plan review, cut application, captions, markers, zooms, b-roll/music placement, and both editor-queued and standalone rendering. Minor gaps remain: no way to undo/revert an applied cut or remove markers/zooms, and no tool to list or delete previously created plans.