Skip to main content
Glama

Related Servers

Alternatives to IlluGen MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      C
      maintenance
      Enables an AI agent to discover Material Maker nodes, validate and build procedural material graphs through an undoable batch, and compare real 3D previews and labeled PBR maps returned as images. It also runs bounded parameter sweeps that restore the source state, and exports maps with manifests listing filenames, channels, sizes, hashes and changed-file state.
      35
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables agents and Blender users to generate game-ready art through a set of Blender tools covering concept image generation, image-to-3D mesh creation, mesh cleanup, PBR material assignment, greybox level layout, camera pathing and still or sequence rendering. Every action runs headless Blender, returns machine-readable JSON with pass/fail self-checks such as triangle budget, scale, pivot and clearance, so agents can verify and fix each step unattended.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to create Material Maker node graphs from natural language, validate them against the node catalog, and render them headlessly to PBR texture maps and editable .ptex files.
      7
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to author node-graph-based procedural graphics as data and render them deterministically via a pinned headless engine, returning validated, hashed image artifacts with full provenance.
      4
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to programmatically control Autodesk Maya via natural language using over 30 tools for 3D modeling, lighting, and animation. It connects through Maya's command port to facilitate procedural scene generation and complex production-ready workflows.
      1
      -

    TDQS

    A4.2/5.0

    Scored across 25 tools

    Disambiguation5/5

    Each tool targets a clearly distinct resource or lifecycle stage (status, catalog lookup, preset listing, project create/read/update/render/validate, node CRUD, link CRUD, curve/gradient/spline setters, annotations, subgraphs). Overlaps are explicitly managed: node_set vs curve_set/gradient_set/spline_set vs node_set_data are delineated in descriptions, and project_render/screenshot/thumbnail/normalize/validate all serve different purposes despite sharing the engine context.

    Naming Consistency5/5

    Tool names are consistently snake_case and follow a predictable resource_action or verb_noun pattern (e.g., node_add, project_render, list_node_types, curve_set, link_remove). Prefixes group related tools logically, and nothing mixes camelCase or wildly different verb styles.

    Tool Count4/5

    At 25 tools the set is on the heavy side of typical MCP servers, but the domain is a full node-graph authoring environment with many distinct data types and lifecycle operations. Each tool appears to earn its place, and no obvious redundant or trivial tool inflates the count.

    Completeness4/5

    Coverage is strong: nodes have create/read/update/delete, links have add/remove, projects have create/read/settings/render/validate/screenshot/normalize/thumbnail, and curves/gradients/splines/annotations/subgraphs are handled. Minor gaps exist (e.g., no update for existing annotations, no direct way to unexpose a subgraph parameter), but agents can work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues