VideoGen MCP server

@videogen/mcp

A Model Context Protocol (MCP) server that exposes the full VideoGen API to any MCP client (Cursor, Claude Desktop, Windsurf, etc.). Your agent can generate videos from scripts, produce images / voiceovers / music / avatars, upload files, export and remix projects, and manage runs — all authenticated with your own API key.

It ships in two transports. Tool surface is the same except for ChatGPT Apps commerce policy (see below):

• Local (stdio) — the client launches @videogen/mcp as a subprocess and reads the key from VIDEOGENAPIKEY.
• Remote (Streamable HTTP) — a hosted, multi-tenant HTTP server. Clients connect over the network and authenticate per request with Authorization: Bearer ; no key lives on the server.

Host surfaces (remote): /mcp (and stdio) is the STANDARD surface: when the user is out of credits or needs a plan feature, tools and guidance walk them into getappdeeplink (OPENUPGRADE / OPENPURCHASECREDITS / OPENENABLETOPUPS). /mcp/chatgpt is the ChatGPT Apps** surface: those commerce deep links are omitted, billing errors are rewritten to “manage your VideoGen account,” and copy never says purchase / buy / upgrade / top-ups (OpenAI Plugins digital-goods policy). See .cursor/rules/chatgpt-mcp-no-commerce.mdc and mcp/src/hostSurface.ts.

This is distinct from the hosted documentation MCP at https://docs.videogen.io/mcp/server, which only lets clients read the API docs. This server actually executes_ the API.

How it works

• Wraps the official @videogen/sdk and calls the live API through the SDK's authenticated passthrough.
• The local transport reads your key from VIDEOGENAPIKEY; the remote transport reads it from each request's Authorization: Bearer header and builds a fresh, per-request server bound to that team (stateless — no session state is shared between requests).
• The key never leaves your machine except in requests to the VideoGen API (local), or is forwarded only to the VideoGen API for the duration of the request and never persisted (remote).
• Long-running operations (workflows, media tools, project exports) use composite tools. The hosted HTTP transport returns the run/execution id immediately; use the corresponding get_* tool to continue polling. The local stdio transport waits for completion by default.

Configuration

Get an API key from app.videogen.io/api. Both transports expose the same tools; the remote server is recommended.

Remote (Streamable HTTP) — recommended

Nothing to install or update. Point any MCP client that supports the Streamable HTTP transport at the hosted endpoint and send your API key as a bearer token:

{
  "mcpServers": {
    "videogen": {
      "url": "https://mcp.videogen.io/mcp",
      "headers": {
        "Authorization": "Bearer sk_videogen_live_..."
      }
    }
  }
}

The remote server:

Shortened. The full README is on GitHub.