Very Good FFmpeg MCP

Remote MCP configuration for the Very Good FFmpeg API.

Very Good FFmpeg exposes a remote MCP server at:

https://verygoodffmpeg.com/api/mcp

Use it from MCP clients that support remote streamable HTTP servers.

MCP Config

Add this server to your MCP client configuration:

{
  "mcpServers": {
    "verygoodffmpeg": {
      "type": "http",
      "url": "https://verygoodffmpeg.com/api/mcp"
    }
  }
}

This repository includes the same configuration in mcp.json.

Very Good FFmpeg supports OAuth for MCP clients with OAuth flow support.

You can also authenticate with a Very Good FFmpeg API key. Header auth is preferred when your MCP client supports custom headers:

Authorization: Bearer YOUR_API_KEY

If your MCP client cannot set headers, pass the API key as a query parameter:

https://verygoodffmpeg.com/api/mcp?api_key=YOUR_API_KEY

Keep query-parameter URLs private because they may be stored in client history, logs, or screenshots.

Create an API key in the Very Good FFmpeg dashboard.
Add a new remote MCP server in your AI client.
Use https://verygoodffmpeg.com/api/mcp as the server URL.
Add Authorization: Bearer YOUR_API_KEY if your client supports custom headers.
If headers are not supported, use the ?api_key=YOUR_API_KEY URL form.
Save the connector and test a simple FFmpeg job request.

Remote MCP clients that support streamable HTTP.
OAuth clients that support MCP OAuth protected resource discovery.
Header auth through Authorization: Bearer ..., or query auth through api_key.

See the Very Good FFmpeg MCP server docs: