FFmpeg API
com.ffmpeg-apiPublished by ffmpeg-api.comOfficial publisherv1.0.0Updated Oct 24, 2026
Run FFmpeg and FFprobe in the cloud: convert, compress, trim and analyze video and audio.
Overview
A remote MCP endpoint that lets an assistant run FFmpeg and FFprobe in the cloud to convert, compress, trim and analyze video and audio.
- What you can do
- This server exposes cloud-hosted FFmpeg and FFprobe operations over a remote streamable HTTP endpoint, so an assistant can convert, compress, trim and analyze video and audio files without a local media toolchain. The registry description lists conversion, compression, trimming and analysis as the main capabilities; no individual tool names are published in the manifest.
- When to use it
- Use it when an assistant needs to process or inspect media files and you would rather send them to a hosted service than install and run FFmpeg locally. It suits conversion, compression, trimming and media analysis tasks in a chat or agent workflow.
- Requirements
- A remote MCP client that supports streamable HTTP, pointed at the provider's endpoint. Authentication is OAuth and is required; no environment variables or headers are declared. Network access to the provider is needed, and media files must be uploaded or made reachable for processing.
Installation
In SourceWeft
- Open FFmpeg API in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.ffmpeg-api%2Fffmpeg/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"ffmpeg-api": {
"type": "http",
"url": "https://mcp.ffmpeg-api.com/mcp"
}
}
}Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
56% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
Publish an icon in the registry entry.
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.
