Skip to main content
Glama
healkeiser

fxhoudinimcp

by healkeiser
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to fxhoudinimcp

No user-submitted related servers found.

    Related Servers

    • Houdini MCP

      OtakuSquirrel
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to directly control SideFX Houdini, including creating nodes, setting parameters, executing Python, capturing viewports, and rendering frames, via 57 MCP tools.
      2
      MIT

    • houdini-mcp

      bharathadolf
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server for SideFX Houdini that enables AI assistants to interactively control, construct, inspect, and visually verify 3D procedural scenes through tools like node creation, parameter editing, viewport capture, and rendering.
      MIT

    • 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
      360 PyPI
      13
      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

      JUSTDOITzhw
      A
      license
      Not graded
      quality
      B
      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.
      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.9/5.0

    Scored across 216 tools

    Disambiguation2/5

    The set has several overlapping entry points: create_material vs create_material_network, set_expression vs the oddly named create_vex_expression, capture_screenshot vs render_viewport, and get_scene_info vs get_scene_summary. Detailed descriptions mitigate some confusion, but with 216 tools an agent still faces ambiguous selection in multiple areas.

    Naming Consistency4/5

    Names are overwhelmingly snake_case with a verb_noun shape (get_*, set_*, create_*, list_*, delete_*), which is easy to scan. Deviations such as playbar_control, new_scene, undo/redo, and the misleading create_vex_expression name are minor but keep it from perfect consistency.

    Tool Count1/5

    216 tools is an extreme mismatch for a single MCP surface; even for a broad Houdini automation server this is far beyond the 3-15 well-scoped range. The count creates context bloat and makes tool selection the dominant usability problem, regardless of the quality of individual descriptions.

    Completeness4/5

    Coverage is unusually broad: scene/node/parameter management, geometry, USD, materials, simulations, caches, renders, HDAs, TOPs, DOPs, COPs, CHOPs, viewport, shelf tools, and sessions. Some lifecycle gaps remain (e.g., take deletion/rename, direct USD prim removal, material unassignment), but most have workarounds through generic node or LOP tools.

    Maintenance

    ActivityActive
    ResponsivenessSlow

    Resources