ffmpeg-mcp-server
Related Servers
Alternatives to ffmpeg-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server exposing headless ffmpeg operations for video, audio, and image processing via auto-generated typed tools, enabling agentic media file manipulation.GPL 3.0
- AlicenseAqualityDmaintenanceA lightweight server that exposes FFmpeg's video processing capabilities to AI assistants through the Model Context Protocol (MCP), supporting operations like video format conversion, audio extraction, and adding watermarks.853 npm25MIT
- AlicenseAqualityDmaintenanceEnables LLMs to perform FFmpeg operations like clipping, merging, extracting audio, adding subtitles, and transcoding videos via a set of tools exposed as an MCP server.58MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that exposes FFmpeg as structured tools for AI-agent-driven video editing, enabling operations like trimming, subtitling, and transcoding via natural language.19,326 npm1MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that exposes FFmpeg as a structured tool set for AI agents, enabling timeline-based video editing, preview, rendering, and analysis with an optional LLM autopilot.MIT
- AlicenseBqualityCmaintenanceEnables AI agents to programmatically edit videos via FFmpeg, providing tools for probing, trimming, concatenating, timeline composition, LUT generation/application, rendering, and edit verification over MCP.162MIT
TDQS
Scored across 19 tools
Most tools have clearly distinct purposes, with descriptions making the soft-subtitle vs. burned-subtitle split explicit. The only real overlap is between trim_silence and trim_media, and extract_thumbnail vs. extract_keyframes, but the descriptions clarify those boundaries well.
The set is almost entirely verb_noun snake_case (trim_media, extract_audio, compress_video, burn_subtitles), which is predictable. The exceptions are media_probe and media_convert, which use noun_verb ordering and mildly break the pattern.
19 tools is on the heavy side but each maps to a distinct, commonly needed ffmpeg operation (probe, convert, trim, concat, mux, overlays, subtitles, normalization). Nothing feels redundant enough to remove, though the surface is larger than ideal.
Coverage is broad across the media lifecycle: inspection, conversion, compression, trimming, concatenation, muxing, overlay, subtitles, speed, aspect ratio, split-screen, keyframes, waveform, and loudness normalization. Minor gaps like rotate/flip, frame-rate changes, and audio fade/volume adjustment are workable gaps rather than dead ends.