fxhoudinimcp
Related Servers
Alternatives to fxhoudinimcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to directly control SideFX Houdini, including creating nodes, setting parameters, executing Python, capturing viewports, and rendering frames, via 57 MCP tools.2MIT
- AlicenseNot gradedqualityBmaintenanceAn 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
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to control SideFX Houdini 3D software, providing tools for scene management, node operations, rendering, and more through the Model Context Protocol.1MIT
- AlicenseAqualityBmaintenanceDrive 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.205MIT
- AlicenseNot gradedqualityDmaintenanceEnables 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
- AlicenseNot gradedqualityBmaintenanceEnables 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
TDQS
Scored across 215 tools
The set spans many Houdini contexts and most tools have distinct targets, but the sheer volume creates real overlap: geometry reads (get_geometry_info, get_points, get_prims, get_attrib_values, sample_geometry, get_attrib_stats), USD reads (get_usd_prim, get_usd_attributes, list_usd_prims, find_usd_prims), and parameter tools (set_parameter, set_parameters, set_expression, link_parameters, create_spare_parameter) all sit close together. Descriptions do a good job steering selection with explicit 'prefer X over Y' notes, which keeps it above a 2.
Names are overwhelmingly consistent verb_noun snake_case (set_keyframe, get_usd_prim, create_lop_node, list_dop_objects), with domain prefixes (usd_, cop_, dop_, top_, hda_) used predictably. Minor deviations like playbar_control, build_network, and bare undo/redo exist but remain readable and predictable.
215 tools is far beyond any reasonable single-server surface and well past the 50+ threshold. Even for a domain as broad as Houdini, this forces the agent to navigate an enormous menu where many capabilities are reachable through multiple near-duplicate tools.
Coverage is essentially exhaustive across Houdini's contexts: node CRUD, parameters, keyframes, USD/Solaris, materials, lights, DOP/COP/CHOP/TOP workflows, HDAs, rendering, viewport capture, documentation search, and session management. Lifecycle operations (create, read, update, delete, cook, verify) are present throughout with no obvious dead ends.