Cascadeur MCP
Related Servers
Alternatives to Cascadeur MCP
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables MCP clients to inspect and edit animation inside a running Cascadeur instance without Computer Use, including scene/object and skeleton rig inspection, bounded joint and Point-target pose edits, snapshots, playback observation, and FBX export.371MIT
- AlicenseNot gradedqualityAmaintenanceEnables 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.19 npm8MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP-compatible AI clients to inspect Godot project and editor state, observe opted-in running scenes, manage processes, and apply permission-scoped guarded edits. It starts read-only and exposes additional capabilities only through explicit command-line flags.Apache 2.0
- 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
- FlicenseNot gradedqualityDmaintenanceEnables AI clients to control Cocos Creator editor projects, scenes, nodes, components, assets, Prefabs, building, and diagnostics via the MCP protocol.-
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to drive a live Blender session over MCP by creating and transforming primitives, building and assigning materials, inspecting scenes and objects, capturing viewport screenshots, and executing arbitrary bpy Python. Commands are relayed over a local TCP bridge to a Blender add-on and executed on Blender's main thread, supporting multiple simultaneous AI clients.MIT
TDQS
Scored across 36 tools
Each tool targets a distinct resource or action: scene creation vs. opening vs. saving, pose reading vs. writing, viewport vs. camera, FBX import/export, API inspection vs. tool inspection, etc. Even similar-sounding tools like list_objects and get_object differ clearly in scope (list vs. exact). No overlapping purposes that would cause misselection.
All tools follow the same cascadeur_verb_noun pattern with verbs like get, set, list, open, save, import, export, run, inspect, activate, select, capture, etc. The naming is entirely snake_case and verb-first, making it predictable and easy to navigate. No deviations or mixed conventions.
With 36 tools, the count is on the high side but justified given the complexity of a full-featured 3D animation tool like Cascadeur. Each tool serves a distinct function across scene management, rig inspection, posing, animation, timeline, viewport, and FBX. It feels comprehensive rather than bloated, though it exceeds the typical 3-15 range.
The surface covers the core workflows: scene creation/opening/saving, FBX import/export, viewport control, object and rig inspection, selection, keyframe and interpolation editing, pose and batch animation, track management, and motion sampling. Minor gaps exist, such as no explicit scene deletion or object deletion/duplication, but these are not critical for the primary animation-focused purpose and can be worked around via other tools.