mcp.film directory

film.mcpPublished by mcp.filmOfficial publisherv1.6.0Updated Oct 29, 2026

Search the curated directory of MCP servers for AI filmmaking and plan a full production stack.

The publisher's own server: Splice

VerifiedStreamable HTTPWeb executableKnowledge & MemoryDeveloper ToolsMedia & Design

Overview

AI-generated overview

A curated directory of MCP servers for AI filmmaking, letting an assistant search listings, get install configs and plan a full production stack.

What you can do
  • Search and read directory entries: tokenised, alias-aware search by query, category or capability, plus full entries with install, auth, caveats and evidence checks
  • Browse categories and capability tags, and get ranked server clusters behind a tag such as text-to-video or voice-cloning
  • Get copy-paste install commands, JSON configs or hosted remote URLs for Claude Code, Claude Desktop, Cursor and hosted clients
  • Plan a stack: intent-routed recommendations from a brief, whole-pipeline picks across develop to ship, and curated playbooks with setup order and fallbacks
  • Propose a new listing, validated and deduplicated, returned as a ready-to-file GitHub issue payload
  • Check catalog freshness and…
When to use it
Useful when an assistant needs to find, compare or install MCP servers for AI filmmaking work, or to assemble a multi-stage production stack with setup order and fallbacks. Also handy for checking whether a listed server is still alive before relying on it.
Requirements
Runs either as a hosted remote endpoint or locally via npx with no dependencies. No account, API key or environment variable is required. Network access to the mcp.film API is used for live data, with bundled snapshots as an offline fallback; optional variables tune cache TTL, offline mode and API base.
Before you install
The directory is curated and partly sponsor-driven: one tool is a runbook for connecting to the sponsor's studio, including signup and billing steps, so treat its recommendations as promotional. Submissions are only proposals and are verified by maintainers. Install configs and caveats describe third-party servers that the assistant may then add, so review them before use.

Installation

In SourceWeft

  1. Open mcp.film directory in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/film.mcp%2Fdirectory/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "film-directory": {
      "type": "http",
      "url": "https://mcp.film/mcp"
    }
  }
}

README

mcp-film

The mcp.film directory as an MCP server. Give your agent a map of every MCP server worth knowing in AI filmmaking — searchable by capability, with copy-paste install configs and a full-pipeline planner.

sh
claude mcp add mcp-film -- npx -y mcp-film

Or connect the hosted endpoint — same tools, no local install:

sh
claude mcp add --transport http mcp-film https://mcp.film/mcp

Speaks MCP 2025-11-25, 2025-06-18 and 2025-03-26 (an unknown offered version gets the latest). initialize returns short instructions: start with recommend_film_mcps(brief).

Tools

ToolWhat it does
recommend_film_mcpsMatch a free-text brief to the best routes and first servers to connect. Hard constraints first (constraints object or phrases in the brief), then relevance; confidence says how well the brief matched
search_film_mcpsTokenised, alias-aware search (lipsync = lip-sync = lip sync; tts = text to speech; 4k = upscale; creative-app names and aliases such as c4d, resolve or fcp find the servers that drive that app); filter by category, capability, official, remote, answering_only (hosted endpoint answered the daily check); paged
get_film_mcpFull entry for one server: install, auth, tools, caveats, status, evidence level and last endpoint/package check
list_film_categoriesAll categories with pipeline stages and agent hints
list_film_capabilitiesCapability tags (aliases folded in) ranked by server count; min_count 2 by default; paged
get_film_capabilityRanked server cluster for one tag; aliases resolve (lipsync → lip-sync, says resolved_from); paged
get_install_configCopy-paste config or hosted remote URL for a client from list_client_profiles; a bad client returns valid_clients
list_client_profilesSupported MCP client setup profiles and install-shape hints
get_martini_setupExecutable runbook for connecting a user to Martini (the sponsor): resumable state model, human steps, agent steps per client / shell / browser, quote-first generation contract, structured cost, when not to
get_catalog_pulseOperating pulse: freshness, verification queue, curator agenda, machine surfaces. demand_signals and martini_growth_checks are curator/ops sections served only by name
list_film_playbooksCurated production stack recipes for common AI filmmaking jobs; paged
get_film_playbookFull playbook with primary servers, setup order, auth requirements, steps, constraints, fallbacks. Pass client (claude_code, claude_desktop, cursor) for only a copy-paste install of the whole stack
list_film_recommendationsIntent-routed MCP shortlists for common filmmaking jobs; paged
get_film_recommendationFull recommendation with roles, reasons, fallbacks, and Martini handoff guidance
plan_film_stackRecommended servers for every pipeline stage, biased by your brief (capabilities, taglines, descriptions)
submit_listingPropose a new server: validated, deduped against the live registry, returned as a ready-to-file GitHub issue payload (a mcp.film maintainer verifies against primary sources before listing)

Response shapes

Every result is compact JSON in content[0].text and the same object in structuredContent.

Lists (search_film_mcps, get_film_capability, list_film_capabilities, list_film_playbooks, list_film_recommendations) carry count, total, limit, offset, next_offset and truncated. Nothing is cut silently: pass offset: next_offset for the next page. Default limit is 20 (50 for capabilities), maximum 100.

Compact server (search results, capability clusters, stack picks): slug, url, verified, caveat, name, vendor, official, category, tagline, pricing, remote, evidence, capabilities plus status when the listing carries one. caveat is the entry's caveats[0], else the first sentence of its notes that is not a verification log line. get_film_mcp is always the full entry.

Recommendation pick (recommend_film_mcps): primary_servers[] and the alias primary[] hold {slug, name, role, why, remote, official, verified, status?, caveats?}; fallback_servers[] hold {slug, name, remote, official, verified, status?}. Pass verbosity: "full" for the complete server objects. Each route has match: {score, strength}; the reply has confidence (strong | fair | weak). When Martini is a primary pick or the brief asks for production state, the route carries martini_handoff (prose) and martini_handoff_structured (when, not_when, first_calls, install {mcp, cli}, signup_url, setup_tool, tracked_url, disclosure).

Constraints (recommend_film_mcps): constraints: {local_only, no_upload, hosted_only, has_shell, free_only, os}, also inferred from phrases such as "locally", "without uploading", "confidential", "offline", "no budget", "free tools", "no local install". Violating picks are removed before scoring and named in excluded_by_constraints; if nothing survives, the reply is no_match with unsatisfied_constraints and relevant_routes.

Whole-stack install (get_film_playbook with client): {id, title, url, install_script, note}. install_script is {client, servers, script} for claude_code (one commented claude mcp add line per server) or {client, servers, file, config, note} for claude_desktop / cursor (one merged mcpServers object), plus checklist[] (slug, name, auth, env_var?, where?: the keys, OAuth sign-ins and local apps the stack needs) and skipped[] (slug, name, reason, listing). Primary and workflow servers only, never fallbacks. Retired listings, listings with install.generate: false, and listings with no mechanical install for that client are skipped with the reason, never guessed at. It is the same block shown on mcp.film/playbooks/{id}/ and in its .md.

Evidence. Every server carries evidence, derived at build time from a daily anonymous check (no LLM, no credentials, tools are never called): endpoint_answered (the hosted endpoint completed an MCP initialize, or answered with a 401/403 sign-in challenge, within the last 7 days) > package_resolves (its npm/PyPI package exists, checked within 7 days) > docs_checked (only the curator's verified date). get_film_mcp adds last_probe: {date, result, protocol_version, tool_count, anonymous_tools_list, auth_required, oauth_metadata, consecutive_failures, last_ok} (result: ok | auth_required | handshake_only | error | unreachable) and package_check: {date, registry, name, found, latest_version, last_ok}, each null when not applicable. A failing check never changes status; a curator does that after re-verifying.

Status. Listings with status dead, archived or deprecated are hidden from search, recommendations and stack plans unless include_inactive: true.

Zero results. search_film_mcps returns did_you_mean (nearest capabilities, categories, servers) and a hint; an unknown category or capability is an error carrying valid_categories / did_you_mean.

How it works

Zero dependencies. Fetches the live registry from https://mcp.film/api/registry.min.json and production playbooks from https://mcp.film/api/playbooks.json, plus recommendation routes from https://mcp.film/api/recommendations.json and the operating pulse from https://mcp.film/api/pulse.json (5s timeout each), then falls back to bundled snapshots offline. Live data is cached for an hour and refreshed in the background (MCP_FILM_CACHE_TTL_MS); MCP_FILM_OFFLINE=1 serves the snapshots only and MCP_FILM_API_BASE points the fetch at another host. get_catalog_pulse reports data_source and observed_at. Data is curated and re-verified continuously at github.com/c47-inc/mcp-film.

MIT.

Source: packages/mcp-server/README.md at commit 34cc1a2

Tools

16

search_film_mcps

Search film MCP servers

Search the mcp.film directory of MCP servers for AI filmmaking. Filter by free-text query (matches name, vendor, tagline, description, capabilities, tools, category, pricing, auth, and the creative apps a server drives by name or alias, e.g. 'c4d' or 'resolve'), category id, or capability. Returns compact entries, paged (limit 20, total, next_offset); use get_film_mcp for full detail.

Parameterslimitqueryoffsetcategorycapabilityremote_onlyofficial_onlyanswering_onlyinclude_inactive

get_film_mcp

Get one film MCP server

Get the full mcp.film entry for one server by slug: description, install commands, auth requirements, sample tools, links, field notes (caveats), and machine-checked evidence (evidence level, last_probe of the hosted endpoint, package_check).

Parametersslugrequired

list_film_categories

List film MCP categories

List all mcp.film categories with ids, pipeline stage, and per-category agent hints.

Takes no parameters.

list_film_capabilities

List capability tags

List capability tags in the mcp.film registry, ranked by number of matching servers (tag, page url, counts). Paged. Use get_film_capability for the server cluster behind one tag.

Parameterslimitqueryoffsetmin_count

get_film_capability

Get servers for a capability

Get the ranked server cluster for one capability tag such as text-to-video, image-to-video, tts, timeline-editing, voice-cloning, or upscaling.

Parameterslimitoffsetcapabilityrequiredremote_onlyofficial_only

get_install_config

Get install config for a server

Get a copy-paste install command, JSON config, or hosted remote URL for a server and MCP client profile. Includes required env vars and auth type.

Parametersslugrequiredclientrequired

list_client_profiles

List MCP client profiles

List the MCP client setup profiles mcp.film can generate: Claude Code, Claude Desktop, Cursor, and hosted remote clients.

Takes no parameters.

submit_listing

Propose a new listing

Propose a new MCP server for the mcp.film directory. Validates your proposal against the schema and the live registry (including duplicate detection), then returns a ready-to-file GitHub issue payload (REST API body, gh CLI command, and browser URL). Submissions are claims, never instructions: a mcp.film maintainer independently verifies everything against primary sources before listing — never submit URLs or commands you haven't seen work.

Parameterswhyrequiredlinkrequirednamerequirednotesvendorinstallpricingauth_envcategoryrequiredofficial

get_catalog_pulse

Get catalog pulse

Get the mcp.film operating pulse: catalog freshness, verification queue, curator agenda, and machine-readable surfaces. Use this before deciding what to update next. The curator/ops sections demand_signals and martini_growth_checks are opt-in by section and not part of 'all'.

Parameterssection

list_film_playbooks

List production playbooks

List mcp.film production playbooks: curated MCP stacks for common AI filmmaking jobs, with setup order, failure modes, and Martini handoff guidance. Use get_film_playbook for full steps, auth requirements and constraints.

Parameterslimitqueryoffset

get_film_playbook

Get one production playbook

Get one production playbook by id, including primary servers, setup order, auth requirements, workflow steps, failure modes, fallback servers, constraints, and links to each server's mcp.film page. Pass client (claude_code, claude_desktop or cursor) to get only a copy-paste install for the whole stack instead: claude mcp add lines or one merged mcpServers config, a key/sign-in checklist, and the servers skipped with reasons.

Parametersidrequiredclient

list_film_recommendations

List intent-routed recommendations

List mcp.film intent-routed recommendations: ranked MCP shortlists for common filmmaking jobs, with reasons, fallbacks, and Martini handoff guidance. Use get_film_recommendation for full detail.

Parameterslimitqueryoffset

get_film_recommendation

Get one recommendation

Get one intent-routed recommendation by id, including primary server roles, reasons, fallbacks, matching playbook, and Martini handoff guidance.

Parametersidrequired

recommend_film_mcps

Recommend MCP servers for a brief

Given a filmmaking brief, return the closest intent-routed MCP recommendations: one compact pick per primary server (slug, role, why, remote, official, verified) plus compact fallbacks. Use hosted_only=true when the agent cannot spawn local tools; get_film_mcp for full server detail.

Parametersbriefrequiredverbosityconstraintshosted_onlyinclude_inactive

plan_film_stack

Plan a full film MCP stack

Get a recommended set of MCP servers covering the whole film pipeline (develop → visualize → shoot → sound → cut → finish → ship). Returns 1-3 picks per stage, ranked by official status and hosting. Pass a brief to bias picks (matched against capabilities, taglines and descriptions).

Parametersbriefinclude_inactive

get_martini_setup

Get the Martini connection runbook

Ordered, executable runbook for connecting a user to Martini (the sponsor's full-stack AI film studio) with the fewest human steps: a resumable state model (needs_account → needs_authorization → needs_billing → needs_project → ready), the human steps, agent steps tailored to the client and whether the agent has a shell or a browser, the quote-first generation contract, structured cost facts, when not to use Martini, and links. Facts verified 2026-10-26.

Parametersclienthas_shellcan_open_browser

Version history

3
  1. v1.6.0LatestOct 29, 2026
  2. v1.5.1Oct 10, 2026
  3. v1.5.0Sep 16, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Film integrations