← All guides

Video Processing with Claude

Add FFmpeg Micro to the Claude app as a custom connector and process videos right inside your chat. Describe what you want in plain English and Claude picks the FFmpeg options, submits the job, and hands back the finished file. No terminal, no code.

Setup

In the Claude app (web or desktop), open Settings, go to Connectors, and choose Add custom connector. Then enter:

  • Name: FFmpeg Micro
  • Remote MCP server URL: https://mcp.ffmpeg-micro.com

When you first use a video tool, Claude opens a browser window for you to sign in with your FFmpeg Micro account. After you approve, the connection is saved and you won't be asked again.

Adding a custom connector is available on any paid Claude plan (Pro, Team, or Enterprise). You do not need Claude to have FFmpeg Micro in its directory to connect this way.

Example prompts

  • “Crop this video to a 9:16 vertical format for Instagram Reels”
  • “Convert this MOV file to MP4 at 1080p and give me the download link”
  • “Add a text overlay saying 'Episode 12' to the top of my video”
  • “Show me all my transcode jobs from today”

Who is this for?

The Claude app is ideal for anyone who wants video processing power without learning FFmpeg commands or writing code. Content creators, marketers, and social media managers can process videos through the same chat interface they already use for everything else.

This works the same way in the Claude web app and the Claude desktop app. Prefer to work in your terminal or editor instead? See the Claude Code integration.

Troubleshooting

Common problems when running FFmpeg Micro from Claude, and what to do about each.

No sign-in window
Sign-in happens in a browser window the first time Claude uses the server. If no window opens, check that the server from Setup is saved with the URL https://mcp.ffmpeg-micro.com, exactly as written there.
Request timed out
transcode_and_wait and run_blueprint_and_wait hold the request open until the job is done, and a long render can outlast a 60-second client timeout. Ask Claude to start the job and check on it instead: transcode_video then get_transcode, or run_blueprint then get_blueprint_run.
A file with no link
The tools take URLs, so the video has to be reachable at a link Claude can pass along. Put the file somewhere with a public HTTPS address and give Claude that address.
Download link expired
Download links are signed and short-lived. Ask for a new one and Claude calls get_download_url again.
Job failed
Ask Claude what went wrong. get_transcode returns the job's error details, for example a file over your plan's size limit or an empty token balance.

Want to learn more about what you can build? Explore the FFmpeg API for complete documentation, code examples, and workflows.