Skip to main content
Glama

Related Servers

Alternatives to nuke-mcp

No user-submitted related servers found.

    Related Servers

    • 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
    • F
      license
      C
      quality
      C
      maintenance
      Enables MCP-capable agents to inspect and modify projects, bins, sequences, tracks, shots, tags, soft effects, and exports in a running Foundry Hiero / Nuke Studio 17 session.
      45
      -
    • A
      license
      A
      quality
      C
      maintenance
      Enables MCP-compatible agents to inspect and control SideFX Houdini scenes, including node management, parameter edits, connections, Python execution, and HIP file operations over stdio or Streamable HTTP.
      15
      MIT
    • A
      license
      Not graded
      quality
      C
      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.
      1
      MIT

    TDQS

    B3.4/5.0

    Scored across 17 tools

    Disambiguation4/5

    Each tool maps to a distinct resource+action: node listing/inspection (list_nodes vs get_node) is differentiated by the knobs/dependents detail, and app vs script info are clearly scoped. The only real overlap is execute_python acting as a superset of every other tool, plus mild adjacency between set_knobs and create_node's knob arguments, but these are conventional escape hatches rather than true ambiguity.

    Naming Consistency4/5

    The dominant pattern is verb_noun (get_app_info, list_nodes, create_node, set_knobs, delete_nodes, set_selection), applied consistently with correct singular/plural semantics. Deviations are the bare verbs undo/redo and the noun-ish render/preview_frame, which are idiomatic for a DCC app and remain readable.

    Tool Count4/5

    17 tools is slightly above the comfortable band but each earns its place across session control, node graph editing, selection, and rendering. Nothing looks like a redundant wrapper, though consolidation (e.g. selection get/set) could trim it a little.

    Completeness4/5

    Coverage is strong: script lifecycle (open/save), undo/redo, node CRUD, knob edits, graph wiring, selection, render verification, and a Python escape hatch for anything missing. Minor gaps remain around creating a new script from scratch, cloning/grouping nodes, and closing/reverting the session, all of which execute_python can work around.