Video Editor MCP Server

A powerful video editing MCP server that leverages FFmpeg to perform video editing operations through natural language commands.

Local serverstdioPython

What is the Video Editor MCP MCP server?

A powerful video editing MCP server that leverages FFmpeg to perform video editing operations through natural language commands. Exposed over MCP by the video editor mcp mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

Its toolset

Everything the assistant can do here goes through one of these:

  • execute_ffmpeg — Executes FFmpeg commands with progress tracking
  • Tools — The Tools tool exposed by this server
  • Prerequisites — 1. FFmpeg must be installed and accessible in your system PATH 2. Python 3.9 or higher 3. Required Python packages: mcp httpx
  • Installation — 1. Install FFmpeg if not already installed: bash # On macOS with Homebrew brew install ffmpeg
  • Debugging — The Debugging tool exposed by this server

Adding it to your client

@modelcontextprotocol/inspector on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Configuration

You will need one environment variable: UV_PUBLISH_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

  1. FFmpeg must be installed and accessible in your system PATH 2. Python 3.9 or higher 3. Required Python packages:

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Video Editor MCP's toolset — execute_ffmpeg, Tools, Prerequisites and 2 more — is a fair guide to whether it matches your workflow. It is maintained by Kush36Agrawal; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the video editor mcp mcp server does with a few real requests.

Available tools

ToolWhat it does
execute_ffmpegExecutes FFmpeg commands with progress tracking
ToolsThe Tools tool exposed by this server.
Prerequisites1. FFmpeg must be installed and accessible in your system PATH 2. Python 3.9 or higher 3. Required Python packages: mcp httpx
Installation1. Install FFmpeg if not already installed: bash # On macOS with Homebrew brew install ffmpeg
DebuggingThe Debugging tool exposed by this server.

How to install the Video Editor MCP MCP server

{
  "mcpServers": {
    "video-editor": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/inspector"],
      "env": {
        "UV_PUBLISH_TOKEN": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

  1. FFmpeg must be installed and accessible in your system PATH 2. Python 3.9 or higher 3. Required Python packages:
VariableDescriptionRequired
UV_PUBLISH_TOKENCredential the server authenticates with.Yes

Example prompts to try

  • Use Video Editor MCP to execute ffmpeg.
  • Use Video Editor MCP to Tools.
  • Use Video Editor MCP to Prerequisites.

Frequently asked questions

It connects Video Editor MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 5 tools (execute_ffmpeg, Tools, Prerequisites, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Video Editor MCP directly.