Skip to main content
Glama
JTCHE

HoudiniMCP

by JTCHE
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to HoudiniMCP

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 Server

      3dprevis
      A
      license
      B
      quality
      D
      maintenance
      Connects SideFX Houdini to Claude via the Model Context Protocol, enabling node creation, modification, and code execution through natural language.
      3
      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
      -

    • BlenderMCP

      ahujasid
      A
      license
      B
      quality
      B
      maintenance
      Connects Blender to Claude AI through the Model Context Protocol (MCP), allowing Claude to directly interact with and control Blender for AI-assisted 3D modeling, scene manipulation, and rendering.
      21
      28,777
      MIT

    • Houdini MCP Server

      bamboovfx
      A
      license
      Not graded
      quality
      C
      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
    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.8/5.0

    Scored across 168 tools

    Disambiguation3/5

    There are several overlapping clusters, such as set_material/assign_material/assign_material_workflow and render_single_view/render_quad_views/render_specific_camera, which could confuse an agent. However, most tools have clear, distinct purposes targeting specific resources.

    Naming Consistency4/5

    Most tool names follow a consistent verb_noun snake_case pattern, such as list_materials, get_parameter, and create_node. Some domain-prefixed groups like pdg_*, lop_*, and hda_* deviate from the verb-first order, but the overall convention is still predictable.

    Tool Count1/5

    With 168 tools, the server is massively oversized for any practical purpose. This is an extreme mismatch, as even a comprehensive Houdini server could be organized into fewer, more focused tools.

    Completeness5/5

    The tool surface is exceptionally broad, covering node operations, parameters, keyframes, geometry, materials, rendering, PDG, LOP, COP, CHOP, DOP, HDA, viewport control, documentation, and more. No obvious gaps exist that would hinder typical workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources