FFmpeg MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| speed_upC | Speed up a video |
| extract_audioB | Extract audio as mp3 from a video |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have completely distinct purposes: one extracts audio from video, while the other modifies video playback speed. There is no overlap in functionality, making it impossible to confuse them.
Both tools follow a consistent verb_noun naming pattern (extract_audio, speed_up), using clear action verbs and descriptive nouns. The naming is uniform and predictable throughout the set.
With only two tools, this server is severely under-scoped for an FFmpeg server, which typically handles a wide range of media processing tasks like format conversion, filtering, and metadata editing. The count feels incomplete for the domain.
The tool surface is extremely incomplete for an FFmpeg server, lacking core operations such as video format conversion, resolution changes, filtering, metadata extraction, or basic CRUD-like media processing. Agents will face significant gaps in functionality.