studio-mcp
Enables the MCP server to use OpenAI's models as the LLM backend for planning, QC, and assembly tools.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@studio-mcpPlan 5 shots for a coastal slow-burn film project 'MARÉA'"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
studio-mcp
The block-method film pipeline as agent-callable MCP tools.
An MCP server that lets an LLM agent drive a full brief → shots → render → QC → cut
workflow by calling tools — instead of clicking through generation UIs by hand.
Plan-then-generate, never reverse: every shot is planned (type, move, duration)
before any pixel is made, and every still is QC'd against a locked look so the
piece stays on-model.
Why
Single-tool MCP servers (one model, one call) are common. This is the layer above: it orchestrates across your generation stack with a block-method planner and a style-drift QC gate — the part nobody ships.
Related MCP server: Media-infrastructure
Tools (v1)
Tool | What it does |
| brief → structured shot plan (type · camera move · duration · action) |
| lock the look so every shot stays on-model |
| vision style-drift QC — scores a still vs shot intent + locked look, pass/fail + fix |
| cut manifest — shot order, durations, audio/lip-sync notes |
| what stages exist for a project |
v1.1 (render phase, via Higgsfield CLI):
train_character (soul-id self-clone) · gen_still (Soul) · animate (Seedance/Kling).
Provider-agnostic
The LLM layer talks to any OpenAI-compatible endpoint — Anthropic, OpenRouter, OpenAI, or a local server — chosen entirely through env config. No provider is hard-coded.
cp .env.example .env # set STUDIO_LLM_BASE_URL / _MODEL / _API_KEYInstall
python3 -m venv .venv && source .venv/bin/activate
pip install -e .Run
studio-mcp # stdio MCP serverRegister with an MCP client (e.g. Claude Code / Claude Desktop):
{
"mcpServers": {
"studio": {
"command": "/path/to/studio-mcp/.venv/bin/studio-mcp",
"env": { "STUDIO_LLM_API_KEY": "sk-..." }
}
}
}Example flow
plan_shots("MARÉA — wordless coastal slow-burn, 90s", project="marea")
lock_campaign("marea", aspect="2.39:1", stock="Kodak 500T, soft handheld",
hex_palette=["#1b2a3a","#c8a15a"], elements=["the woman in grey"],
audio="diegetic SFX only, no music")
# render a still (v1.1) → then:
qc_still("marea", image="assets/shot1.png", shot_id=1) # pass/fail + fix
assemble("marea") # cut manifestState lives under STUDIO_ROOT (default ~/studio-projects/<project>/) as plain
JSON — human-inspectable, and a clean contract a future console can read.
License
MIT
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/rishbjain1/studio-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server