Mcp.film directory

What mcp.film directory MCP server does

The mcp.film directory MCP server gives agents access to a curated directory of MCP servers for AI filmmaking. The catalog covers the film workflow from screenplay breakdown through publishing, including video models, voice services, scoring tools, edit bays, finishing software, and delivery services.

Each listed server can include its installation command, authentication requirements, pricing information, sample capabilities, and operational caveats. Those notes are intended to help an agent distinguish between a useful option and one with important constraints, such as a required software edition, missing official API, or usage quota.

The directory also supports production planning. An agent can use the catalog to identify components for a complete filmmaking stack rather than evaluating isolated servers without regard to the rest of the workflow.

How it works

The directory publishes several agent-oriented representations of its catalog. These include an llms.txt index, a full structured registry, a registry-compatible API, per-server JSON and Markdown pages, capability indexes, client setup profiles, playbooks, recommendations, and a pipeline guide.

The local MCP package is available from the repository’s packages/mcp-server/ directory and can be launched with npx -y mcp-film. This makes the catalog available as an MCP endpoint for a compatible client. The public site provides the same underlying directory through machine-readable routes such as /api/registry.json and /api/mcp-registry.json.

Catalog maintenance is editorial and verification-based. The project describes daily re-checking of links and servers, while rankings consider factors such as official status, maintenance recency, hosted availability, and documented caveats. Changes are retained in the project history, so the directory’s data can be audited through its repository.

Setup and configuration

Install the local server with the following MCP command:

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

The command uses Node package execution and does not list any required environment variables in the provided material. Client setup guidance is published for Claude Code, Claude Desktop, Cursor, hosted remote clients, and the directory’s own meta-server. The repository also states that Node 20 or newer is sufficient for local development and provides separate commands for validation, building, and previewing the site.

Tools and capabilities

The mcp.film directory MCP server is suited to agents that need to:

• Search a catalog of filmmaking-related MCP servers.
• Compare entries using installation, authentication, pricing, capability, and caveat metadata.
• Plan a production stack across multiple stages of film creation.
• Read structured registry data or agent-focused Markdown and text indexes.
• Consult playbooks describing stack recipes, setup order, authentication gates, and failure modes.
• Check client setup profiles and capability-specific directory pages.

The repository also exposes catalog pulse data, recommendations, a new-server feed, and per-server records. These surfaces let clients choose between broad discovery and more targeted retrieval.

Limitations and notes

The directory describes and organizes other MCP servers; the provided material does not claim that it supplies the underlying video, voice, music, editing, or hosting services itself. Availability and requirements belong to the individual listings and may include authentication, paid usage, software-edition restrictions, or unavailable official APIs.

The catalog is curated and re-verified, but its entries are still subject to change. Feedback is recorded for maintainers and is not automatically incorporated into rankings. The project is MIT licensed, and its public ranking process is editorial rather than an automatically generated quality score.