Transloadit MCP Server
transloaditLABSCO SUMMARY
FFmpeg without a machine to keep running.
The command string is still yours to write — nothing here guesses at filters — but the queue, the GPU workers and the hosting of the output are not your problem, and a finished job announces itself over a webhook instead of being waited on.
What it is
A remote MCP server in front of Very Good FFmpeg, a service that runs FFmpeg commands behind an API. You give it input URLs, output names and the command string; it queues the job and returns URLs for the files it made.
What you get
- Any FFmpeg command run as a queued job, with a per-job timeout you set
- Inputs read from public URLs; media that is not already hosted goes through the temporary files route first
- Several commands chained in sequence on one machine, for pipelines that should not round-trip between steps
- Jobs routed to CPU workers or to NVIDIA workers when the work wants a GPU
- A webhook when the job finishes, so nothing has to sit and poll
- The same account reachable from the TypeScript and Python SDKs, Make and n8n, if part of the pipeline lives outside the chat
Requirements
A Very Good FFmpeg API key from the dashboard, or OAuth if your client supports the flow. It is a remote server over streamable HTTP: the key goes in an Authorization header, and clients that cannot set headers pass it as a query parameter instead — a form the vendor asks you to keep private, since URLs end up in client history, logs and screenshots.
Setup effort
Paste a URL with a key — add the endpoint to your client
USE CASES
01
Trimming or converting a file that already lives on a URL
Point at the input, name the output, give the FFmpeg command, and take back the URL of the result when the job clears the queue.
02
Running a multi-step pipeline
Chain the commands so they run in sequence on the same machine, instead of pulling each intermediate file down and pushing it back up.
03
Sending a long encode to a GPU
Route the job to NVIDIA workers and give it a longer timeout, then let the webhook say when it landed.
04
Working on media that is only on your laptop
Upload through the temporary files route first, then submit the job against what you just uploaded.
BEFORE YOU INSTALL
What to know first
Requires
A client that can reach a remote MCP server over HTTP
Where it runs
The documented client connects to a hosted endpoint.
INSTALLATION
Connect your client
Add the endpoint to your client.
Server setup
ENDPOINT URL
https://verygoodffmpeg.com/api/mcpMCP Clients
Any MCP client — remote
ANY MCP CLIENT — REMOTE · JSON
{
"mcpServers": {
"verygoodffmpeg": {
"type": "http",
"url": "https://verygoodffmpeg.com/api/mcp"
}
}
}
