Skip to main content
Glama
tmdag

houdini-mcp

by tmdag
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to houdini-mcp

No user-submitted related servers found.

    Related Servers

    • nscr-houdini-mcp

      nscrdev
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to connect to multiple SideFX Houdini 22 sessions, including GUI and headless, to build, render, cache, and verify scenes against reference images.
      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

    • Houdini MCP Server

      Kif11
      F
      license
      Not graded
      quality
      B
      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

      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

      bennyjoel
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to connect directly to a live Houdini session and act as a technical director by creating nodes, wiring networks, querying scene data, running Python/HScript, and modifying parameters in real time.
      -
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    C2.5/5.0

    Scored across 82 tools

    Disambiguation3/5

    Many tools have clearly distinct purposes (node CRUD, USD inspection, docs search), but there are overlapping clusters: set_viewport_renderer vs set_hydra_renderer vs set_hydra_display vs set_viewport_display, four frame_* variants, and lop_prim_get vs get_usd_attribute. Descriptions mitigate most confusion, but an agent could easily misselect within these clusters.

    Naming Consistency4/5

    Names overwhelmingly follow snake_case verb_noun (get_parameter, create_node, list_children, set_viewport_camera), with domain prefixes like lop_*, lookdev_*, frame_*, and import_*/attach_* used fairly predictably. A few single-word tools (batch, ping) and mixed prefixes are minor deviations from an otherwise consistent scheme.

    Tool Count1/5

    82 tools is far beyond what an agent can reliably navigate for a single application-control server; the description even admits overlap (e.g. viz/flipbook variants, parameter get/set families). This forces the agent to choose among many near-siblings rather than a coherent, curated surface.

    Completeness4/5

    The surface covers an impressive breadth: node lifecycle, parameter access, USD/LOP inspection and editing, viewport/render control, KineFX character workflows, lookdev, scene persistence, and offline docs. Only minor gaps remain (e.g. no explicit undo/redo, limited PR-like review of scene changes), which agents can work around.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources