Skip to main content
Glama

Related Servers

Alternatives to HoudiniMCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Connects Claude AI to Houdini via the Model Context Protocol, enabling prompt-assisted 3D modeling, scene manipulation, and rendering within Houdini.
      11
      GPL 3.0
    • A
      license
      B
      quality
      D
      maintenance
      Connects SideFX Houdini to Claude via the Model Context Protocol, enabling node creation, modification, and code execution through natural language.
      3
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Connects Claude AI to Houdini through the Model Context Protocol, enabling direct interaction and control for 3D modeling, scene creation, simulation, and rendering.
      20
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Connects Houdini to Claude AI through Model Context Protocol, enabling AI-assisted 3D modeling, scene creation, simulation setup, and rendering through natural language commands.
      59
      -
    • A
      license
      B
      quality
      B
      maintenance
      Connects Blender to Claude AI through the Model Context Protocol (MCP), allowing Claude to directly interact with and control Blender for AI-assisted 3D modeling, scene manipulation, and rendering.
      21
      30,209
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to control SideFX Houdini 3D software, providing tools for scene management, node operations, rendering, and more through the Model Context Protocol.
      1
      MIT

    TDQS

    A4.5/5.0

    Scored across 20 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, and descriptions explicitly cross-reference alternatives (e.g., cook vs pdg vs render, node_inspect vs scene_overview vs geometry_inspect). Minor overlaps remain: scene_overview lights and stage_inspect lights both read USD stage lights, geometry_inspect image and node_inspect image both inspect COP nodes, and selection/cache data can be obtained from multiple tools. These are edge cases, but they keep the set from being perfectly unambiguous.

    Naming Consistency4/5

    All names use lowercase snake_case or single lowercase tokens, with no camelCase or case-style mixing. The pattern is not strictly verb_noun: there are single verbs (capture, connect, select, cook, render, execute), single nouns (batch, console, docs, hda, pdg, playbar, session), and noun_verb compounds (node_edit, node_inspect, parm_set). Still readable and mostly predictable, with only minor deviations.

    Tool Count4/5

    20 tools is above the typical 3-15 sweet spot and lands in the heavier 16-25 range, so it is mildly over rather than perfectly scoped. However, each tool maps to a distinct Houdini subsystem, and many operations are consolidated into mode-based tools, avoiding an even larger surface. The count is reasonable given Houdini's breadth.

    Completeness5/5

    The surface covers session management, scene files, inspection, node editing, parameter writing, wiring, cooking, simulation, PDG, USD, rendering, capture, HDA editing, docs, execution, undo, and more. No obvious lifecycle gap remains for the stated domain; agents have both high-level and low-level escape hatches where needed.

    Maintenance

    ActivityActive
    ResponsivenessNo issues