Cascadeur MCP
Related Servers
Alternatives to Cascadeur MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables AI clients to control Cascadeur locally for scene and rig inspection, body and finger animation, keyframes, physics actions, camera control, PNG previews, and FBX import/export via stdio MCP.363MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to inspect and control a running WARUDO scene, including assets, character pose and IK, expressions, blueprints, camera, and captures, through an MCP client.183 npm9MIT
- AlicenseNot gradedqualityDmaintenanceConnects MCP-compatible clients to a live Blender scene for AI-assisted 3D workflows, enabling inspection and controlled operations on objects, materials, cameras, lights, render settings, animation, UVs, Geometry Nodes, imports, exports, and Python execution.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to watch and drive a running ResInsight, query reservoir simulation models, and render pictures and plots without touching the GUI.GPL 3.0
- FlicenseNot gradedqualityCmaintenanceEnables remote control of Blender through MCP, allowing code execution, scene manipulation, rendering, and file transfer in a containerized environment.1-
- FlicenseNot gradedqualityBmaintenanceEnables MCP clients to drive Blockbench Desktop locally for Minecraft model, UV, texture, animation, and export workflows. It provides typed operations, high-level task workflows, native controls, and inspection/verification tools over an authenticated loopback connection.3-
TDQS
Scored across 37 tools
Multiple tools overlap heavily in purpose: reading transforms via get_transform, get_local_transform, get_global_transform, get_pose, get_character_pose, and get_semantic_pose all retrieve similar data in different contexts, and writing transforms has many parallel variants. While descriptions distinguish contexts, an agent could easily misselect among this dense set.
Tool names follow a consistent snake_case verb_noun pattern throughout (e.g., get_scene_info, set_pose, save_pose_snapshot, export_fbx). Minor variations in verb choice (e.g., inspect, retime) remain within a predictable convention.
With 37 tools, the set is heavy and exceeds the typical 25+ threshold for 'too many.' While the domain is complex, many tools could be consolidated, and the large count increases cognitive load and selection difficulty.
The toolset covers reading/writing poses, transforms, sequences, snapshots, export, and playback, but notable gaps exist: no deletion of keyframes, objects, or characters; no creation of objects or characters; and no undo beyond snapshots. These omissions may force workarounds for lifecycle management.