# studio-state

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

- **Category:** Story & Pre-Production
- **Vendor:** Community (DKF2 Studios) (community)
- **Pricing:** free
- **Verified:** 2026-06-28

## 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`
- Local: `python3 /abs/path/studio-state-public/server.py`

**Auth:** local-app (env `STUDIO_ROOT`) — Requires a local project folder containing _pipeline/STATE.json and episodes/

## Capabilities

`production-state` · `shot-tracking` · `continuity` · `session-orientation` · `render-status`

## Sample tools

`orient` · `get_shot_status` · `update_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.

## Verification

- Status: Freshly checked (1 days old)
- Added: 2026-06-28
- Last verified: 2026-06-28
- Machine JSON: https://mcp.film/api/mcps/studio-state.json

## Links

- Site: https://dkf2studios.gumroad.com/l/flplx
- Docs: https://github.com/dkf2studios/studio-state-public/blob/main/INSTALL.md
- Repo: https://github.com/dkf2studios/studio-state-public

---

Structured data: https://mcp.film/api/mcps/studio-state.json · Directory: https://mcp.film