video-edit-mcp
Related Servers
Alternatives to video-edit-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables local media processing (video/audio) using FFmpeg and FFprobe, allowing frame extraction, audio conversion, and metadata retrieval through natural language.5MIT
- FlicenseBqualityDmaintenanceEnables AI assistants to perform video and audio processing tasks such as format conversion, cutting, merging, and adding effects via FFmpeg, with hardware acceleration support.193-
- AlicenseBqualityDmaintenanceProvides powerful video and audio editing capabilities through FFmpeg, enabling AI assistants to perform professional-grade operations including format conversion, trimming, overlays, transitions, and advanced audio processing.2790MIT
- AlicenseBqualityCmaintenanceProvides Claude Code with local ffmpeg-based tools to probe, trim, concat, transform, overlay, mix audio, render JSON timelines, and run automated QA on video files—no API key required.9Apache 2.0
- AlicenseAqualityCmaintenanceLets AI agents inspect local or remote videos by reading metadata, detecting shots and cuts, extracting frames as images, and checking keyframes for seeking and streaming, all via local FFmpeg without an API key.51MIT
- AlicenseAqualityBmaintenanceEnables vision-capable AI assistants to inspect local videos by returning frames as images, sampling clips, generating contact sheets, detecting scene cuts, auto-picking platform-sized thumbnails, and exporting GIF, MP4, or WebP previews.8MIT
TDQS
Scored across 15 tools
Most tools target a clearly distinct operation (probe, trim, cut, concat, reframe, audio.*, captions.*). There is some overlap: render can burn captions and overlay HyperFrames layers, which partially duplicates captions.render, and compose vs render vs export.package touch adjacent rendering/assembly concerns, but descriptions provide enough guidance to choose correctly.
The set mixes bare verbs (render, transcribe, probe, trim, cut, concat, compose, reframe) with dotted namespace.action names (export.package, audio.measure, captions.generate). The namespacing is readable and groups related tools, but it is not a single consistent convention.
15 tools is well within the ideal range for a media-editing server and each tool covers a distinct pipeline stage (inspect, edit, reframe, caption, audio, compose, package, health). No tool appears redundant enough to be cut.
The surface covers the full edit lifecycle: probing, trimming/cutting/concatenating, reframing, captioning, loudness and mixing, composition, packaging, and environment health. Minor gaps exist, such as thumbnail/poster extraction, speed/scale adjustments, and explicit extract-audio, but these are workaroundable.