MCP Server

@ffmpeg-micro/mcp-server

A Model Context Protocol server that lets AI agents — Claude Code, Claude Desktop, Cursor, Windsurf, VS Code, and any other MCP-compatible client — create, monitor, and download video transcodes through the FFmpeg Micro REST API.

What it does

Exposes tools that map onto FFmpeg Micro's public API:

Blueprints

Blueprints are pre-built workflows behind POST /v1/blueprints/{slug}/runs. The tool descriptions document each blueprint's input fields. Notes:

• Most blueprints run on the FFmpeg lane and meter plan compute minutes (no tokens). Generative blueprints (product-ad) charge tokens; a 402 insufficient_tokens response means the account needs a token pack (dashboard).
• caption-video pauses in awaitingreview with the transcript (srttext) so the agent can review/edit before rendering; resume with continueblueprintrun.
• Multi-output blueprints (listing-kit, hook-variants) return an outputs array of {label, url} — prefer it over output_url when present.
• Output URLs are signed with a 10-minute TTL; re-fetch the run for fresh links.

Uploading a local file

The requestuploadurl + confirm_upload pair lets an MCP host upload a local file to the FFmpeg Micro storage bucket without dealing with raw API keys or gs:// URLs:

1. Host calls requestuploadurl with {filename, contentType, fileSize} → receives a short-lived presigned HTTPS URL.
2. Host PUTs the file bytes to that URL with the same Content-Type.
3. Host calls confirm_upload with {filename: , fileSize} → receives the final gs://... fileUrl.
4. Host passes that fileUrl to transcribeaudio / transcodevideo / transcodeandwait.

Quick start

Add this to your project's .mcp.json (or your MCP client's config):

{
  "mcpServers": {
    "ffmpeg-micro": {
      "type": "http",
      "url": "https://mcp.ffmpeg-micro.com"
    }
  }
}

Shortened. The full README is on GitHub.