MCP

One protocol, no separate app to open.

MCP, the Model Context Protocol, is a standard way for a coding agent to call tools that a separate local process exposes, over stdio rather than an HTTP API. Your agent starts the process, reads the list of tools it offers, and calls them with structured arguments when a task needs one.

openvidstudio ships as one of those processes: a local server with twenty six tools, twenty seven if the Higgsfield tier is on. There is no openvidstudio app to open. Your agent is the interface.

1. Add the server

@openvidstudio/mcp-server is on npm, so npx fetches it on first run and there is nothing to install ahead of time.

mcp.json

{
  "mcpServers": {
    "openvidstudio": {
      "command": "npx",
      "args": ["-y", "@openvidstudio/mcp-server"]
    }
  }
}

2. Restart the client

The client reads mcpServers at startup, launches command with args, and talks to it over stdio from then on. Twenty six tools should appear. If you are working on openvidstudio itself, build from a clone and point command at node with the absolute path to dist/stdio.js instead.

shell, contributors only

git clone https://github.com/AnayDhawan/openvidstudio.git
cd openvidstudio
pnpm install
pnpm --filter @openvidstudio/mcp-server build

3. Point it at a project

Ask your agent to run init_project. It scaffolds src/videos/<name>/ in your repo, copies the pipeline docs into docs/, and writes openvidstudio.config.json at your project root.

openvidstudio.config.json

{
  "hasHiggsfield": false,
  "targetDurationSeconds": 60,
  "videoConfig": {
    "fps": 30,
    "width": 1920,
    "height": 1080
  }
}

The hasHiggsfield gate

import_higgsfield_clip, the tool that ingests an AI generated b roll clip into this pipeline's asset convention, is only registered when hasHiggsfield is true in your project config, read once at server startup. Leave it false, which is the default, and the tool does not appear in your agent's tool list at all. Not present and erroring: absent.

openvidstudio never holds a Higgsfield API key and never talks to Higgsfield itself. Using this tier means you already have a subscription and its own MCP connector enabled in the same agent session, and your agent generates the clip over that connection. This server's tool only takes the finished result and lands it at the right path.

Every tool this server exposes

Plan

init_projectpreflightplan_shotsplan_beatsvalidate_beatswrite_beats_filediff_beats

Capture

capture_screenshotcapture_screen_recordingcapture_desktopcapture_mobilecapture_terminalextract_brand

Build

scaffold_scenevalidate_scenesgenerate_narrationplan_sound_effectsstitch_composition

Render

render_videoexport_renditionreformat_vertical

Check

qc_extract_framescontact_sheetvisual_regressiondocs_driftrelease_diff

Gated

import_higgsfield_clip

How it works covers what each one does, in the order your agent calls them. If you have not run Playwright or ffmpeg on this machine before, start at prerequisites.