Before you begin
invideo MCP connected to your AI assistant, a base cut made from your own footage just by chatting, and an editable project exported to Premiere Pro, Final Cut Pro or DaVinci Resolve (or a finished rendered video).
Tools used
- invideo MCP (https://mcp-v2.invideo.io/mcp)
Claude, ChatGPT, Claude Code, Codex, Cursor, VS Code or Gemini CLI- Optional: Premiere Pro, Final Cut Pro or DaVinci Resolve for finishing
Requirements
- An invideo account (you sign in during the connection, no API key needed)
- An MCP client that supports remote servers: Claude (web or desktop), ChatGPT, Claude Code, Codex, Cursor, VS Code or Gemini CLI
- For ChatGPT: access to custom MCP plugins under your account/workspace policy
- Some footage to edit (a brand shoot, talking-head clips or B-roll)
On this page · 9 steps
Your progress
0 of 9 steps
The walkthrough
Step 01 / 09
What invideo MCP actually is
MCP (Model Context Protocol) is the standard that lets AI assistants use outside tools. invideo MCP is a remote MCP server that gives your agent a real, professional video timeline to work on. Once it is connected, your agent can edit an NLE timeline, color correct footage, mix audio, import and manage media, and generate images, video and audio. You and the agent can work on the same project at the same time. When you are done, you export either a rendered video or an editable project for Premiere Pro, Final Cut Pro or DaVinci Resolve. invideo's own line for it sums it up: bring your own agent into the edit. Watch the Reel first to see it in action. The linked TECH4SSD Reel is the published demonstration. Its caption credits the footage to invideo's launch film; the site links to that Reel rather than redistributing the launch footage.
Official invideo MCP setup and capabilitiesStep 02 / 09
Connect it to Claude (web or desktop)
Continue from here