Previs Director MCP
Related Servers
Alternatives to Previs Director MCP
No user-submitted related servers found.
Related Servers
- FlicenseBqualityBmaintenanceEnables guided 3D previsualization planning, camera and action audits, saved-scene inspection, and revision/gate tracking through a local Review Room and reusable articulated mannequin library. It also supports consent-based update checks, while scene creation, animation, and rendering remain in separate Blender tools.32-
- AlicenseCqualityCmaintenanceEnables MCP-capable assistants to inspect, create, measure, and review Blender production workflows for characters, rigs, animation, game meshes, facial performance, secondary motion, and PBR materials with checkpoints and visual QA.2741MIT
- AlicenseBqualityBmaintenanceEnables MCP clients such as Codex and Claude to plan natural-language or timed actions, generate and revise skeletal motion locally through a Kimodo runtime, and review results with diagnostics, candidate comparison, and interactive 3D previews. Provides checked handoffs of verified exports into Blender and Unreal Engine.371MIT
- AlicenseCqualityBmaintenanceEnables inspection and editing of Cascadeur rigs, controller animation, poses, keyframes, motion plans, review images, and FBX exchange through 49 structured tools plus optional Python execution.95MIT
- AlicenseBqualityBmaintenanceEnables models to pose and measure first-person arms and a rifle in Blender, reporting positions in named frames, clearances, visibility, screen placement, and solving rifle moves against goals.1775 PyPI1MIT
- 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
TDQS
Scored across 32 tools
Most tools have clearly distinct purposes: pipeline phases, gate criteria/validation, audits, rig and locomotion constraints, project lifecycle, revision evidence, Review Room snapshots and update handling are separable. There is mild overlap in the validation family (validate_gate vs. record_previs_review vs. validate_human_greenlight) and in the project-state family (inspect_previs_scene vs. get_previs_project_status vs. get_previs_revision), but the long descriptions draw the boundaries well. An agent can pick the right tool in most cases with a careful read.
The dominant pattern is verb_noun (get_gate_criteria, create_previs_project, validate_human_greenlight), but several tools are noun-first or ambiguous (startup_verification, delivery_checklist, check_previs_updates, get_previs_help). The 'previs' domain token appears inconsistently across otherwise parallel tools (create_previs_project vs. inspect_previs_scene vs. set_previs_project_target vs. choose_execution_mode). Still readable, but the convention is not predictable enough to infer names from a description.
32 tools is heavy and sits above the comfortable band, pushing toward a menu that an agent must search rather than recall. The domain is genuinely broad (8-phase pipeline, 7 gates, two audit passes, character physics, project/revision management, Review Room, self-update), so most tools do map to a real workflow step. It is borderline: consolidation into a few parameterized tools (e.g. one gate tool, one constraint-lookup tool) would help.
The surface covers the previs lifecycle well: guidance, gate criteria and validation, audits, physics constraints, project creation/targeting, inspection, immutable revisions, review recording, Review Room import/listing and update preparation. Gaps are modest—no list-projects or delete/archive operation, and the update flow stops at prepare_previs_update with no execute step (likely deliberate). Agents can work around these.