Skip to main content
Glama
Sign In
Houdini MCP

Houdini MCP

by beatreichenbach
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Houdini MCP

No user-submitted related servers found.

    Related Servers

    • houdini

      JUSTDOITzhw
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables language models to inspect the current Houdini scene, create and modify nodes, and run VEX/Python code in the running Houdini session via MCP.
      1
      MIT

    • Houdini MCP

      alexantoshuk
      A
      license
      A
      quality
      C
      maintenance
      Enables MCP-compatible agents to inspect and control SideFX Houdini scenes, including node management, parameter edits, connections, Python execution, and HIP file operations over stdio or Streamable HTTP.
      15
      MIT

    • Houdini MCP Server

      eliiik
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables natural language control of SideFX Houdini for tasks including node management, parameter editing, and geometry inspection. It leverages RPYC to execute Python scripts and manage scene data through an MCP-compatible interface.
      MIT

    • Houdini MCP Server

      Kif11
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to control Houdini by executing Python code, querying scene information, and creating nodes via the Model Context Protocol.
      2
      -

    • Houdini MCP Server

      bamboovfx
      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

    • HoudiniMCP

      JTCHE
      A
      license
      A
      quality
      B
      maintenance
      Drive SideFX Houdini from any agent: build node networks in one all-or-nothing call, cook, render, capture the viewport, and read the offline docs of your Houdini build. 20 tools with modes.
      20
      172 PyPI
      15
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.4/5.0

    Scored across 213 tools

    Disambiguation2/5

    With 213 tools there are many overlapping pairs: get_parameter vs get_parameters, get_usd_attribute vs get_usd_attributes, capture_screenshot vs render_viewport vs render_node_network, create_material vs create_material_network, and several list_* tools that differ only subtly. Descriptions help in places, but an agent will frequently face unclear boundaries among the many read/inspect tools.

    Naming Consistency4/5

    Most tools follow a snake_case verb_noun pattern (get_node_info, create_lop_node, list_usd_prims, set_render_settings). Minor deviations exist, such as playbar_control, log_status, undo/redo, and the misleadingly named create_vex_expression, but the overall convention is predictable.

    Tool Count1/5

    213 tools is an extreme mismatch for a single MCP server, far beyond the typical 3-15 range. The surface spans many Houdini contexts, but the sheer volume makes tool discovery, selection, and maintenance unwieldy.

    Completeness4/5

    The surface is remarkably comprehensive across SOP, DOP, COP, TOP, LOP, CHOP, rendering, HDA, UI, and scene workflows, covering most lifecycle operations. However, there are minor gaps such as no delete_take, no delete_network_box, and some material lifecycle operations only partially exposed.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources