mcp.film

mcp.film / Story & Pre-Production / studio-state

studio-state

Communityby Community (DKF2 Studios)freeverified Jun 28, 2026

Keeps AI-film characters, locations, shots, and lock status grounded in project files.

Rate it: no ratings yet

What it does

A stateless MCP server for long-running AI film and episodic projects: it reads a file-based show folder and tells an agent where the production stands. Its tools orient the session, report per-shot status, and write only a small sidecar when a shot is fired, locked, or needs rework.

Connect

Claude Code
claude mcp add studio-state -e STUDIO_ROOT=/abs/path/your_show -- python3 /abs/path/studio-state-public/server.py
Claude Desktop (claude_desktop_config.json)
{
  "mcpServers": {
    "studio-state": {
      "command": "python3",
      "args": [
        "/abs/path/studio-state-public/server.py"
      ],
      "env": {
        "STUDIO_ROOT": "YOUR_KEY_HERE"
      }
    }
  }
}
Cursor (.cursor/mcp.json)
{
  "mcpServers": {
    "studio-state": {
      "command": "python3",
      "args": [
        "/abs/path/studio-state-public/server.py"
      ],
      "env": {
        "STUDIO_ROOT": "YOUR_KEY_HERE"
      }
    }
  }
}
Auth: local-app · env STUDIO_ROOT — Requires a local project folder containing _pipeline/STATE.json and episodes/

Tools you'll see

orientget_shot_statusupdate_shot

Field notes

MIT, pushed Jun 2026, tiny adoption so far (0 stars) but unusually film-native. It is a state shim, not a generator: it expects your production to follow its folder convention and the paid Studio Method pack is upsold in the README. The useful bit is safe by design — only `update_shot` writes, and only to a per-scene `shot_status.json` sidecar.

Pairs well with