# invideo MCP Server

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

- **Category:** Video Generation
- **Vendor:** invideo (official)
- **Pricing:** freemium
- **Verified:** 2026-08-17

## 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. For a filmmaker-agent it is a blocking tool, not a finishing one — useful for 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: `https://mcp.invideo.io/sse`
- Claude Code: `claude mcp add --transport sse invideo https://mcp.invideo.io/sse`
- Local: `npx mcp-remote https://mcp.invideo.io/sse`

**Auth:** none — None — invideo's help centre says the remote MCP requires no authorisation

## Capabilities

[text-to-video](https://mcp.film/capabilities/text-to-video.md) · `script-generation` · `stock-footage` · [voiceover](https://mcp.film/capabilities/voiceover.md) · `subtitles` · [localization](https://mcp.film/capabilities/localization.md)

## Field notes

invideo labels this Beta in its own help centre and publishes no tool names, no quota, and no credit model, so plan on reading tools/list rather than hard-coding anything. Two transport wrinkles found on 17 Aug 2026: the documented endpoint is the deprecated SSE form at /sse — a GET holds the stream open rather than returning headers, consistent with a live server but not a completed handshake — while an undocumented https://mcp.invideo.io/mcp answers 405 to a GET, the POST-only signature of Streamable HTTP, which is the path to try if your client refuses SSE. The vendor documents only Claude Desktop, Cursor and Windsurf, all via `npx mcp-remote`; the CLI form above is the generic Claude Code SSE syntax, not a command invideo publishes. No auth means no account linkage: expect anonymous rate limits, watermarking, or invideo-hosted output URLs you do not own the lifecycle of, and do not build a paid pipeline on it until the beta label comes off. Output is a templated stock-and-voiceover assembly — for shot-level generative control stay with the model servers in this category.

## Verification

- Status: Freshly checked (checked today)
- Added: 2026-08-17
- Last verified: 2026-08-17
- Machine JSON: https://mcp.film/api/mcps/invideo.json

## Links

- Site: https://invideo.io/ai/mcp/?utm_source=mcp.film&utm_medium=referral&utm_campaign=directory&utm_content=invideo%3Asite
- Docs: https://help.invideo.io/en/articles/11316042-invideo-model-context-protocol-server?utm_source=mcp.film&utm_medium=referral&utm_campaign=directory&utm_content=invideo%3Adocs

---

Structured data: https://mcp.film/api/mcps/invideo.json · Directory: https://mcp.film