Skip to main content
Glama
Cascadeur MCP Plus
by Karylcode

Related Servers

Alternatives to Cascadeur MCP Plus

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables 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.
      36
      10
      MIT
    • A
      license
      C
      quality
      B
      maintenance
      Enables 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.
      95
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to control the Blockout previs desktop app for AI filmmaking, allowing staging of 3D worlds, character animation, camera framing, timeline control, and viewport screenshotting through MCP tools.
      7
      Apache 2.0
    • F
      license
      B
      quality
      C
      maintenance
      Enables AI agents to control a live 3ds Max session directly, including creating and editing objects, materials, animation, and scene inspection, with undo support.
      17
      -
    • A
      license
      A
      quality
      C
      maintenance
      Lets agents see and drive a live 3D application session through its addon socket: viewport screenshots, turntable and multi-mode renders, scene and object inspection, arbitrary Python execution, GLB import/export and asset validation, plus rig, pose-deformation and silhouette-likeness checks. This lets an agent visually judge a 3D result instead of guessing.
      25
      MIT

    TDQS

    B3.4/5.0

    Scored across 18 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, and the split between action control, scene introspection, and UI automation is understandable. Minor overlap exists between ui_click vs ui_invoke/ui_set_property and between dialogs vs ui_tree, but the descriptions give enough guidance to choose correctly.

    Naming Consistency3/5

    Most tools follow a readable verb_noun pattern such as call_action, get_scene_info, and ui_click. However, several names are noun-only or resource-like (screenshot, dialogs, ui_tree), and the ui_* prefix mixes action tools with introspection tools, so the convention is not fully predictable.

    Tool Count4/5

    At 18 tools the set is slightly above the typical 3-15 range, but the broad surface (actions, scene introspection, UI automation, Python execution) justifies most tools. No tool is obviously redundant, and the UI family is grouped coherently.

    Completeness4/5

    The set covers action discovery and execution, rig mode setup, scene/object introspection, screenshots, dialogs, and full mouse/keyboard/QML manipulation, with run_python as a broad escape hatch. Direct high-level animation or rig-generation operations are not first-class tools, but they can be composed through actions, UI automation, or Python.