Mcp Ffmpeg Helper

What is Mcp Ffmpeg Helper?

Mcp Ffmpeg Helper is a lightweight Model Context Protocol (MCP) server that exposes FFmpeg’s video processing capabilities to AI assistants. It provides tools for common FFmpeg operations such as format conversion, audio extraction, trimming, watermarking, and frame extraction. It is intended for users who want to control FFmpeg through natural language commands in MCP‑compatible applications like Windsurf.

How to use Mcp Ffmpeg Helper?

Install Node.js (v14+) and FFmpeg (must be in system PATH). Clone the repository, run npm install and npm run build, then add the server configuration to the MCP config file (e.g., mcp_config.json for Windsurf). Alternatively, use the npm package @sworddut/mcp-ffmpeg-helper with npx without cloning. Once configured, users issue natural language commands such as “请帮我查看…视频信息” to invoke tools.

Key features of Mcp Ffmpeg Helper

• Get detailed video file information (format, codec, resolution, framerate).
• Convert videos between formats with optional encoding options.
• Extract audio tracks from video files.
• Create videos from image sequences.
• Trim videos and audio to specified time ranges.
• Add image watermarks with position and opacity control.
• Extract video frames as image sequences (PNG, JPG).

Use cases of Mcp Ffmpeg Helper

• Automate batch video format conversion via an AI chatbot.
• Extract a segment from a long video or audio file for quick editing.
• Create a time‑lapse video from a series of still images.
• Add a logo watermark to a video before publishing.
• Quickly inspect video metadata without running FFmpeg manually.

FAQ from Mcp Ffmpeg Helper

What are the runtime requirements?

Node.js v14+ and FFmpeg installed and accessible from the command line (verify with ffmpeg -version).

How do I configure the server for Windsurf on Windows?

Add to %APPDATA%/.codeium/windsurf/mcp_config.json: either a local node script path or npx @sworddut/mcp-ffmpeg-helper with command cmd and args ["/c", "npx", "@sworddut/mcp-ffmpeg-helper"].

Where does data processing happen?

All file paths refer to the local filesystem. The server runs locally and uses the system‑installed FFmpeg. Video/audio files are accessed directly by their file paths.

Are there any known limitations?

FFmpeg must be correctly installed and added to PATH. Windows paths require backslashes. Permission issues may occur if the application cannot read/write the specified directories.

What transport/auth does the server use?

The server communicates via standard input/output (stdin/stdout), as is standard for MCP servers. No authentication is mentioned.