Visual Production MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| STUDIO_HOME | No | Optional absolute path to the workspace .studio directory, e.g. /absolute/workspace/.studio. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| studio_libraryB | Show reusable, versioned canonical character registry and reference hashes without provider credentials. |
| studio_statusA | View locally registered projects, jobs and manually reported account budgets; no live credits are claimed. |
| studio_import_projectC | Import a versioned production manifest with asset hashes, character bible and shots from local disk. |
| studio_register_accountC | Register a separately authorized provider session and a manually reported credit estimate, never a password or cookie. |
| studio_update_balanceC | Refresh manually reported credit balance, without claiming live verification. |
| studio_bind_projectC | Link a canonical production to an account-local provider project, with IDs of uploaded references and created characters. |
| studio_sync_planC | List precisely what is missing to hydrate one provider-local project for a canonical shot; never recreate all episodes. |
| studio_planC | Plan idempotent per-shot assignments across separately authorized accounts, within operator-entered budget; creates no paid generations. |
| studio_preflightA | Read-only per-account production preflight; reports missing references and upstream tool compatibility, never verifies live credits. |
| studio_discover_upstreamB | Read tools and schemas of a locally configured upstream MCP; does not run paid generations. |
| studio_dispatch_jobB | Dispatch only an operator-approved job via a configured local upstream. On uncertain submission, block retries for manual reconciliation. |
| studio_record_failureC | Record a confirmed upstream failure. Unknown submissions remain blocked until operator CLI reconciles them. |
| studio_ingest_resultA | Copy an already generated local media file into content-addressed storage, verify integrity and ffprobe video, then mark complete pending human editorial review. No generation or credit spend. |
| studio_bundleC | Export portable canonical project manifest and original reference assets to a local folder; does not include account credentials. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 14 tools
Most tools map to distinct lifecycle stages, such as importing a project, planning assignments, dispatching a job, recording failure, and ingesting a result. A few planning/inspection tools overlap in phrasing—especially studio_plan vs. studio_sync_plan and studio_preflight vs. studio_sync_plan—so an agent may occasionally hesitate, but the descriptions usually clarify the intended object and scope.
All tools share the studio_ prefix and mostly follow a verb_noun pattern like studio_dispatch_job and studio_register_account. There are minor deviations where the suffix is a noun or gerund-like label, such as studio_library, studio_status, and studio_preflight, but the convention remains highly readable.
Fourteen tools is well within the appropriate range for a multi-stage visual production workflow involving accounts, projects, planning, dispatch, failure handling, ingestion, and export. Each tool appears to cover a specific operational need rather than bloating the surface.
The tool set covers the core production lifecycle from project import and account registration through planning, dispatch, result ingestion, status, and portable export. Some lifecycle gaps remain, such as explicit project/account deletion or editorial review actions beyond marking a result complete pending review, but these are minor workarounds rather than dead ends.