Skip to main content
Glama
MikeLi-28

Substance-3D-Designer-MCP

by MikeLi-28

Related Servers

Alternatives to Substance-3D-Designer-MCP

No user-submitted related servers found.

    Related Servers

    • 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
    • A
      license
      Not graded
      quality
      A
      maintenance
      Adapter that runs an MCP server inside Substance 3D Designer, enabling tools to inspect and interact with the active designer session and its packages through natural language.
      254 PyPI
      1
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables agents to observe, batch, script, recover, bake, and export Adobe Substance 3D Painter scenes through a Model Context Protocol server with specialist schemas and persistent tooling.
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to drive Blockbench Desktop locally for Minecraft model, UV, texture, animation, and export workflows. It provides typed operations, high-level task workflows, native controls, and inspection/verification tools over an authenticated loopback connection.
      3
      -
    • F
      license
      A
      quality
      C
      maintenance
      Enables MCP clients to drive ArmorPaint 1.0 through a file-based bridge plugin, letting agents open projects, inspect and edit materials and node graphs, paint, and export textures on an unmodified ArmorPaint installation.
      58
      1
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      A local MCP server that enables MCP-compatible AI clients to inspect and control the currently open scene in a running Autodesk VRED Professional 2027 instance via a secure bridge, supporting read-only inspection and gated mutations like selection, visibility, transforms, and screenshots.
      MIT

    TDQS

    B3.3/5.0

    Scored across 29 tools

    Disambiguation4/5

    Most tools have clearly distinct resource-action pairs (e.g., create_node vs create_instance_node vs create_graph). However, sd_ping, sd_get_application_info, and sd_get_capabilities all report version/status/capability information, creating some overlap that could confuse an agent.

    Naming Consistency5/5

    All tool names follow a consistent 'sd_verb_noun' snake_case pattern (e.g., sd_list_packages, sd_create_node, sd_delete_nodes). The only minor deviation is sd_get_active_graph using an adjective, but it still fits the pattern.

    Tool Count2/5

    With 29 tools, this exceeds the 25+ threshold for 'too many' per the calibration. While the domain is broad, there is noticeable redundancy in info-gathering tools (ping, get_application_info, get_capabilities) and some niche tools (validate/apply_graph_patch) that could be consolidated or omitted.

    Completeness4/5

    The tool set covers the core lifecycle for packages, graphs, and nodes: create, read, update, delete, connect/disconnect, save, and export. Missing operations like package deletion, undo, or copy/paste are minor gaps that don't block primary workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive