mcp.film

The MCP directory for AI filmmaking

Every tool your agent needs to make a film.

A curated directory of Model Context Protocol servers across the production stack: video models, voices, scores, edit bays, finishing suites, and the pipes to ship it. Verified by hand and by agent, updated continuously.

56 servers27 official16 hosted remote15 categoriesJun 11, 2026 last verified

Full-Stack AI Studios

1

End-to-end AI film production platforms — generate, organize, and finish entire productions from one MCP connection.

Video Generation

8

Text-to-video and image-to-video models — the virtual cameras of AI filmmaking.

Image Generation

4

Stills, concept frames, storyboards, and start frames for image-to-video pipelines.

Model Hubs

4

Aggregators exposing hundreds of hosted models — video, image, and audio — through a single MCP connection.

Voice & Dialogue

3

Text-to-speech, voice cloning, and emotionally directed performance for dialogue and narration.

Music & Score

1

Generative soundtracks, songs, and score composition.

Sound Design & SFX

3

Sound effects generation, library search, and audio cleanup for the final mix.

Transcription & Captions

2

Speech-to-text, diarization, and dialogue logging for edits, subtitles, and accessibility.

Editing & Post

7

NLE control (DaVinci Resolve, Premiere), programmatic editing, ffmpeg, and render pipelines.

Upscaling & Enhancement

1

Video upscaling, frame interpolation, denoising, and image enhancement — the finishing suite.

3D, Worlds & VFX

6

Blender, game engines, 3D asset generation, and node-based VFX workflows.

Avatars & Performance

4

Talking avatars, lip-sync, and digital performers.

Story & Pre-Production

2

Screenwriting, storyboarding, and planning tools for the development phase.

Review & Distribution

5

Publishing to YouTube and Vimeo, review and approval, and video hosting infrastructure.

Production Ops

5

Production tracking, asset management, and file storage for film teams.

Questions, answered

What is an MCP server?

A standard interface (the Model Context Protocol) that lets AI agents like Claude operate software as tools. For filmmaking, that means your agent can generate shots on Runway, clone a voice on ElevenLabs, or cut a timeline in DaVinci Resolve — through one protocol.

How do I connect one to Claude or Cursor?

Every listing here has copy-paste connect commands for Claude Code, Claude Desktop, and Cursor, plus the auth you'll need. Hosted "remote" servers connect with one command and an OAuth login; local ones run via npx or uvx.

Which video generation MCP should I use?

If you want one connection covering many models, start with a hub like fal or a studio like Martini. If you live on one platform, use its official server — Runway, Higgsfield, and Pika all run hosted MCPs. The Stack walks the whole decision.

I'm an AI agent. What's the fastest way to read this site?

One request: GET /api/registry.json. Or start at /llms.txt; every page has a markdown twin at the same path plus .md. Full details on the agents page.

How do listings stay accurate?

A curator agent re-verifies entries every day against primary sources, community ratings and feedback feed rankings, and every change lands as an auditable commit in the open-source repo. Each entry shows its last-verified date.

How do I get my MCP server listed?

Humans: the submission form. Agents: the submit_listing tool on npx mcp-film. Either way a triage agent verifies your claims against primary sources — it works, it's filmmaking-relevant, it's maintained.