
FFMPEG API
- Updated June 13, 2026
- hifarrer/ffmpegapi-agent-docs
FFMPEG API is a hosted Model Context Protocol server that wraps FFMPEG API video and audio processing endpoints so agents can trim, merge, convert, caption, and compress media without local FFmpeg.
About
FFMPEG API is a hosted MCP server that exposes FFMPEG API media-processing endpoints as tools for agents and MCP clients like Cursor and Claude Desktop. It covers trimming, merging, compression, captions, GIF conversion, and job-status polling over Streamable HTTP with API-key authentication. Use it when you want agents to edit video or audio through a managed cloud API instead of installing and shelling out to local FFmpeg.
- Hosted Streamable HTTP MCP at mcp.ffmpegapi.net
- Tools include trim_video, merge_videos, compress_video, and youtube_to_mp4
- API-key auth via X-API-Key header shared with REST billing
- Read-only OpenAPI and docs resources for agent discovery
- No local FFmpeg install required on the client machine
FFMPEG API by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
claude mcp add --transport http ffmpegapi https://mcp.ffmpegapi.net/mcp --header "X-API-Key: YOUR_X_API_KEY"Add your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| Transport | HTTP |
|---|---|
| Auth | Required |
| Last updated | June 13, 2026 |
| Repository | hifarrer/ffmpegapi-agent-docs ↗ |
How can an AI agent perform reliable FFmpeg media operations without managing binaries, flags, and brittle shell commands on every machine?
Trim, merge, convert, caption, and compress video or audio through hosted FFmpeg API MCP tools.
Who is it for?
Developers building agent-driven video pipelines who prefer a billed hosted API with MCP tool schemas and shared REST credentials.
Skip if: Offline-only media workflows, teams that cannot send media URLs to a third-party API, or use cases needing custom FFmpeg filters absent from the public tool list.
What you get
The agent submits media jobs through MCP tools and receives processed outputs or job-status results from the hosted FFMPEG API.
Recommended MCP Servers
FAQ
How do I authenticate MCP requests?
Send your FFMPEG API key in the X-API-Key header; MCP uses the same keys, limits, and billing as the REST API.
What is the MCP endpoint URL?
Connect clients to https://mcp.ffmpegapi.net/mcp using Streamable HTTP transport.
Do I need FFmpeg installed locally?
No—the server runs processing in the hosted FFMPEG API; clients only need MCP connectivity and an API key.