video-editor-mcp
Related Servers
Alternatives to video-editor-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables video processing operations (speed adjustment, keyframe optimization, concatenation, and file management) using FFmpeg via Claude Desktop.453 npm4MIT
- 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 gradedqualityCmaintenanceGives coding agents a local FFmpeg video-editing engine exposed over MCP, enabling them to probe, cut, join, reframe, caption, normalize audio, and verify the resulting media without cloud services or API keys. Every operation returns structured JSON and self-checks its own output against delivery specs.14,436 npmMIT
- AlicenseAqualityBmaintenanceEnables coding agents to inspect and manipulate video and audio through ffmpeg-backed tools for probing, trimming, cropping, resizing, extracting audio or frames, generating thumbnails, normalizing loudness, concatenating files, burning captions, and converting formats. Each operation returns concise JSON with output path, size, and verified duration or dimensions.1137 npmMIT
- AlicenseBqualityCmaintenanceEnables AI coding agents to safely inspect, trim, reframe, extract audio from, and burn dynamic subtitles into media files through structured, sandboxed FFmpeg/ffprobe tools with validation and dry-run previews.6MIT
- AlicenseAqualityDmaintenanceEnables local media processing (video/audio) using FFmpeg and FFprobe, allowing frame extraction, audio conversion, and metadata retrieval through natural language.5MIT
TDQS
Scored across 9 tools
Each tool targets a distinct editing operation, and most are easy to tell apart. The only real ambiguity is probe vs qa, since both report duration/resolution/FPS, but qa is clearly a quality gate while probe focuses on codecs and tracks.
Most names are readable lowercase verbs like trim, concat, transform, and render, but the set mixes bare verbs, the underscored compound audio_mix, and noun-style names qa and health. There is no consistent verb_noun or noun_verb convention across the full set.
Nine tools is well within the ideal 3-15 range for a focused server. Each tool earns its place by covering a distinct stage of a video editing pipeline without redundancy or bloat.
The surface covers the full lifecycle: inspect, trim, assemble, transform, overlay, mix audio, render, QA, and environment health. There are no obvious dead ends for a video-editing workflow; render and qa close the loop.