Visual Production MCP
Related Servers
Alternatives to Visual Production MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables agents to plan, capture, beat-analyze, render, verify and visually inspect deterministic beat-synced trailers and scene programs inside a workspace, including stills, contact sheets, timeline linting, editor interchange exports and authored audio arrangements. It also produces typed on-chain scene bundles with local-only reuse review and browser/offline playback checks.MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to drive an AI video production studio, orchestrating character and scene continuity, text-to-speech, ComfyUI video generation, lip-sync, VLM quality review, provenance tracking, and OpenTimelineIO export.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceLets Claude, Codex, and Cursor users turn scripts or briefs into short-drama episodes, linked storyboards, character looks, and AI-generated images or video, while managing projects, canvas layouts, and hosted agent workflows.5MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI clients to manage video pre-production and production workflows through OAuth-secured tools covering projects, story and scripts, assets, 3D maquettes, storyboards, video generation, writers' room, and scheduling, with user approval and cost confirmation for paid generations.AGPL 3.0
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to create and manage video projects, write story and brief, convert, estimate costs, propose paid actions, run approved proposals, discard and restore assets.3MIT
- AlicenseNot gradedqualityCmaintenanceEnables host coding agents to conduct evidence-first exploratory testing, adversarial review, reproduction, and resumable reporting through immutable job contracts, action budgets, checkpointed ledgers, integrity-checked artifacts, and optional origin-restricted browser automation.MIT
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.