Skip to main content
Glama
ChengZiiii

opera-houdini-mcp

by ChengZiiii
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to opera-houdini-mcp

No user-submitted related servers found.

    Related Servers

    • 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

      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

    • substance-designer-mcp

      MikeLi-28
      A
      license
      A
      quality
      A
      maintenance
      A security-focused MCP server for Adobe Substance 3D Designer that reads application state, creates and manipulates nodes, and saves packages, with the runtime isolated outside Designer.
      29
      1
      MIT

    • nuke-mcp

      joshw051
      A
      license
      B
      quality
      D
      maintenance
      A production-grade MCP server for Foundry Nuke that enables AI assistants to understand and manipulate compositing environments, including AOVs, deep workflows, distortion, tracking, OCIO/ACEScct, and CopyCat ML.
      45
      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.7/5.0

    Scored across 174 tools

    Disambiguation2/5

    Many tools have overlapping purposes, such as get_geo_summary vs get_geometry_info, verify_hou_api vs get_houdini_help, and get_scene_info vs get_scene_summary. The sheer number of similarly named get_* and create_* tools makes it difficult for an agent to select the correct one without reading extensive descriptions.

    Naming Consistency2/5

    Tool names follow no single consistent pattern: some use verb_noun (set_parameters), some use prefix-based conventions (hda_list, pdg_cook, lop_prim_get), and others mix forms (uninstall_hda vs hda_install). This inconsistency increases cognitive load and makes predictions about tool names unreliable.

    Tool Count1/5

    With 174 tools, this server vastly exceeds the typical well-scoped range of 3-15 tools. The extreme count overwhelms agents and likely degrades selection accuracy, making it an extreme mismatch for a coherent MCP surface.

    Completeness5/5

    The server provides extensive CRUD/lifecycle coverage across Houdini's major domains: nodes, parameters, geometry, rendering, DOPs, COPs, CHOPs, LOPs, PDG, materials, HDAs, takes, caches, and even a knowledge base. No obvious dead ends or significant missing operations were found.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources