video-audio-mcp
Provides an MCP (Model Context Protocol) server that exposes FFmpeg-backed tools for common video and audio editing tasks such as format conversion, trimming, resizing/aspect changes, codec/bitrate/frame-rate adjustments, overlays (text/images), subtitle burning, concatenation/transitions, and audio operations like silence removal and format/property conversion. Includes a health_check tool.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Security model appears to be local/server-run with no documented authentication. FFmpeg processing of untrusted media may pose risks (e.g., codec/input parsing vulnerabilities); no sandboxing or input validation beyond basic file existence/format support is documented. TLS/rate limits are not applicable/undocumented. Dependency hygiene cannot be verified from provided content; the manifest suggests commonly used libraries but does not include vulnerability attestations.
⚡ Reliability
Best When
You want local, scriptable media transformations accessible to an MCP-capable agent/client via a defined set of editing tools powered by FFmpeg.
Avoid When
You cannot install/run FFmpeg locally, or you need strong network authentication, auditability, and multi-tenant isolation guarantees.
Use Cases
- • Convert and re-encode video/audio files to target formats/codecs/bitrates
- • Trim clips with precise timing
- • Resize or change aspect ratio with padding/cropping
- • Add text overlays, image watermarks, and burn subtitles
- • Concatenate multiple clips with fade/crossfade transitions
- • Extract audio from video and convert audio formats (e.g., to MP3/AAC/WAV)
- • Remove silent segments from recordings/podcasts
- • Automate batch media processing workflows via MCP clients
Not For
- • Running untrusted media processing in a highly sandboxed environment without additional controls (FFmpeg can be risky with hostile inputs)
- • Use as a hosted multi-tenant SaaS with strong authentication/authorization guarantees (appears to be local/server-run)
- • Cloud-scale distributed processing without documented queueing/limits
- • As a replacement for a dedicated editing suite with GUI-centric workflow needs
Interface
Authentication
No authentication/authorization mechanism is documented in the README. Assumes the operator runs the server locally and controls access via filesystem/process permissions and client configuration.
Pricing
No pricing model described for a hosted service; appears to be self-hosted/open-source tooling. A Smithery registry link is mentioned, but no usage pricing is provided in the README excerpt.
Agent Metadata
Known Gotchas
- ⚠ FFmpeg is required; missing FFmpeg will fail operations (documented as a common issue)
- ⚠ Behavior and output determinism depend on FFmpeg availability and codec support on the host
- ⚠ Large media inputs may be slow/compute-heavy; no explicit timeouts/quotas documented
- ⚠ Output path collisions/overwrites are possible if the agent reuses output filenames (not explicitly documented
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for video-audio-mcp.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-30.