Skip to main content
Glama
3dprevis

HoudiniMCP Server

by 3dprevis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to HoudiniMCP Server

No user-submitted related servers found.

    Related Servers

    • HoudiniMCP

      eetumartola
      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

    • HoudiniMCP

      JTCHE
      A
      license
      C
      quality
      B
      maintenance
      Connects SideFX Houdini to Claude via the Model Context Protocol, enabling control of Houdini scenes, nodes, rendering, and more through 166 MCP tools.
      100
      442 PyPI
      4
      MIT

    • HoudiniMCP

      katha-begin
      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

    • HoudiniMCP

      capoom
      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
      -

    • 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
      -
    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

    B3.1/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a distinct purpose: getting scene info, creating a node, and executing arbitrary code. No overlap in functionality, so an agent can easily differentiate them.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern: get_scene_info, create_node, execute_houdini_code. No mixing of conventions or vague verbs.

    Tool Count3/5

    With only 3 tools, the server feels thin for a comprehensive Houdini integration. However, the generic execute_houdini_code tool expands the scope, making the count borderline acceptable.

    Completeness2/5

    The tool surface is severely incomplete for typical Houdini workflows (e.g., no delete, modify, or connect node tools). The execute_houdini_code tool provides a workaround but undermines the purpose of dedicated tools.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources