mcp.film

mcp.film / Video Generation / invideo MCP Server

invideo MCP Server

OfficialRemoteby invideofreemiumverified Sep 23, 2026

Official remote MCP that turns a prompt into a scripted, narrated, subtitled cut.

What it does

invideo's official hosted MCP hands an agent the whole assembly-line version of video: write the script from a prompt, pull clips from a stock library, lay in AI voiceover, and burn subtitles in 50+ languages, returning a full-length edit rather than a single shot. The entire surface is one tool — send a script plus topic, vibe, audience and platform, get a video URL back — so it is a blocking tool, not a finishing one: animatics, pitch reels, explainer inserts, and social cutdowns where speed beats frame-level control. Unlike almost every other server here it needs no key or account to connect, which makes it the cheapest thing to try and the hardest to reason about at scale.

Connect

Remote endpoint (Streamable HTTP)
https://mcp.invideo.io/mcp
Claude Code
claude mcp add --transport http invideo https://mcp.invideo.io/mcp
Claude Desktop (claude_desktop_config.json)
{
  "mcpServers": {
    "invideo": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.invideo.io/mcp"
      ]
    }
  }
}
Cursor (.cursor/mcp.json)
{
  "mcpServers": {
    "invideo": {
      "url": "https://mcp.invideo.io/mcp"
    }
  }
}
Auth: none — None — an unauthenticated initialize and tools/list both succeed against the endpoint

Sample tools

generate-video-from-script

Field notes

invideo pulled its MCP documentation some time between 17 Aug and 23 Sep 2026: help centre article 11316042 now 404s, the landing page at invideo.io/ai/mcp/ still links to it, and no replacement exists — the help centre's agent collections now cover the invideo Editor and its model line-up instead, with no MCP article among them. So `docs` is null: there is no published quota, credit model or transport guidance left to point at. The server outlived its docs and is in better shape than in August: on 23 Sep 2026 an unauthenticated POST to https://mcp.invideo.io/mcp completed a full handshake — Streamable HTTP, protocol 2024-11-05, serverInfo `invideo-ai` 0.0.2 — and returned tools/list, so the fields above now point there rather than at the deprecated /sse form, which still answers 200 if your client insists on SSE. That tools/list is the headline caveat: exactly one tool, `generate-video-from-script`, taking five required strings (script, topic, vibe, targetAudience, platform) and returning a video URL. No status tool, no shot control, no asset upload, no way to feed it your own footage. No auth also means no account linkage — expect anonymous rate limits, watermarking, or invideo-hosted output URLs whose lifecycle you do not own. Output is a templated stock-and-voiceover assembly; for shot-level generative control stay with the model servers in this category.

Also in Video Generation

Pairs well with