What is Vibevideo Mcp

vibevideo-mcp is an MCP server designed for agentic video editing, facilitating the processing of media through FFmpeg. It includes a front-end editor for human users and is maintained by HYE Partners.

Use cases

Use cases for vibevideo-mcp include editing videos for social media, creating educational content, and automating media processing tasks in professional settings.

How to use

To use vibevideo-mcp, run the React front-end and Node.js back-end in development mode using ‘npm run dev’. The Python back-end can be started with ‘python main.py’, and the Python agent can be launched with ‘python ollamarun.py’.

Key features

Key features include a user-friendly React front-end for video editing, a Node.js back-end for handling API requests, and a Python back-end for executing FFmpeg commands. It supports natural language media edits through a simple Python agent.

Where to use

vibevideo-mcp can be used in various fields such as video production, content creation, and media processing, making it suitable for personal, research, or commercial projects.

VibeVideo-MCP

Overview

This monorepo contains an MCP server for agentic video editing. It also powers a front-end human user editor. It’s built and maintained by HYE Partners.

---

Installation

You’ll need Node.js, npm (or pnpm/yarn), and Python 3.12+ (with pip).
These instructions assume a Unix-like OS (Mac/Linux), but should be adaptable for Windows.
Docker instructions below.

• Start the Python backend first (main.py)
• Then start the Node backend (npm run dev in ffmpeg-frontend)
• Then run the Python agent (ollamarun.py) for natural language jobs

---

Clone the Repo

• From your root coding project directory
• git clone https://github.com/hyepartners-gmail/vibevideo-mcp.git
• cd vibevideo-mcp

Install the ffmpeg-backend components

• cd ffmpeg-backend
• python3 -m venv .venv
• source .venv/bin/activate
• pip install -r requirements.txt

If you don’t have ffmpeg installed

• pip install ffmpeg

Install the ffmpeg-frontend components

• cd ffmpeg-frontend
• npm install

---

Structure

The project includes three main servers:

1. React Front-End (Vite)

• URL: http://localhost:8080/
• Dev: Runs on Vite
• For: User front-end that gives you access to all of the video editing tools
• Run: (This launches both the React front-end and Node back-end in dev mode)
• npm run dev

---

2. Node.js Back-End (Express)

• URL: http://localhost:8300/
• Dev: MCP Server, handles API requests from Python agents

---

3. Python Back-End (FFmpeg Command Runner)

• URL: http://127.0.0.1:8200
• For: Flask App handles all ffmpeg-powered media processing jobs
• Run:
• python main.py

---

4. Python Agent (Ollama Runner)

• A simple Ollama agent running locally, for making one request at a time, media edits in natural language
• Run:
• python ollamarun.py

Suggested Models (must have function calling/tools):

• command-r7b:latest
• devstral:latest
• qwen3:latest
• phi4-mini:latest
• mistral-nemo:latest
• llama3.1:8b
• llama3.3:latest
• qwen2.5-coder:latest
• firefunction-v2:latest
• llama4:scout

---

Running with Docker (Optional)

If you want everything to “just work” via Docker:

Build and run both back-end servers with Docker Compose (from repo root):

docker-compose up --build

The following ports will be available:

Frontend (Vite): http://localhost:8080/
Node API server: http://localhost:8300/
Python FFmpeg backend: http://localhost:8200/

You can still use npm run dev/python main.py for local dev if you prefer.
Note: The Docker setup mounts local source code, so edits will live-reload in most setups.

---

Roadmap Items

June 3rd 2025

1. Better Timeline editing, Get Render working
2. Dashboard Metrics / Run counts
3. Connector to CrewAI
4. MCP for some of the non-ffmpeg filters

---

Usage

• Free for any use: personal, research, or commercial.
• If you use this or build on top of it, a shout-out to HYE Partners is appreciated!
• If you fix bugs please submit PRs so everyone can benefit

License

Open use. Attribution requested, not required.

For issues, improvements, or collaboration, visit www.hyepartners.com.

---

Common Problems & Fixes

1. Can’t find requirements.txt or Dockerfile?

• These files are present in the repo under ffmpeg-backend/ and ffmpeg-frontend/.

• If you don’t see them, make sure you’ve done a fresh git pull or git clone from the latest branch.

• If issues persist, check your local .gitignore or .git/info/exclude for accidental blocks.

2. Flask or Other Python Dependency Errors?

• If pip install -r requirements.txt fails with missing modules (like Flask), open requirements.txt and manually add any missing packages.

• Run pip install -r requirements.txt again.

3. Node.js Import Error with JSON Files?

• If you get SyntaxError: Unexpected identifier ‘assert’, you need “type”: “module” in your package.json, and Node.js >= 17.5+.

• For maximum compatibility, use require() instead of import for JSON in server files, or convert the file to CommonJS if needed.

4. Order of Startup

• Python Backend (main.py) — must be running before the Node.js server.

• Node.js Frontend/Backend (npm run dev) — launches both client and API server.

• Python Agent (ollamarun.py) — optional, for natural language commands.

• Docker Compose — launches all together.