MCP Server

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.

Authentication

Use either OAuth (for MCP clients with OAuth flow) or your Very Good FFmpeg API key.

OAuth clients can connect to:

https://verygoodffmpeg.com/api/mcp

Alternatively, use API key auth. Header auth is preferred:

Authorization: Bearer YOUR_API_KEY

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

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

Keep the query-param form private. URLs can be stored in client history, logs, and screenshots.

Generic Setup

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

Client Guides

• ChatGPT developer mode and MCP connectors
• Claude custom connectors with remote MCP

Compatibility

• 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.