A
licenseC
qualityC
maintenanceEnables Claude to drive an open Adobe Substance 3D Painter session to bake textures, build and tune material layers, inspect renders and channel previews, and export finished assets.
86
MIT
substance-designer-mcp
by PropGon
Related Servers
Alternatives to substance-designer-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceEnables Claude to create and manipulate 3D scenes, objects, materials, lighting, cameras, MoGraph, dynamics, renders, and Redshift materials in Cinema 4D through natural-language prompts.-
- AlicenseNot gradedqualityDmaintenanceEnables AI-assisted 3D content creation by allowing Claude Code to control SideFX Houdini directly, including creating nodes, setting parameters, executing HScript commands, and building complex procedural networks.13MIT
- FlicenseNot gradedqualityAmaintenanceEnables Claude to drive a 3D modeling application through natural-language prompts for scene creation, object modification, materials, lighting, animation, MoGraph, dynamics, and rendering.-
- FlicenseNot gradedqualityAmaintenanceEnables Claude to create and manipulate Cinema 4D scenes through natural-language prompts, including objects, materials, cameras, lighting, MoGraph, dynamics, and rendering.-
- AlicenseNot gradedqualityDmaintenanceEnables conversational control of Adobe Substance 3D Painter for look-dev iteration, including baking, smart materials, and generator parameter tuning.MIT
TDQS
B3.3/5.0
Scored across 22 tools
Disambiguation4/5
Most tools target distinct actions on distinct resources (graphs, nodes, parameters, outputs). A couple of pairs could be momentarily confused—export_sbsar vs cook_sbs (both produce .sbsar, differing only by Designer requirement) and render_outputs vs batch_render—but the descriptions clearly distinguish them. The run_python escape hatch is well-flagged as a last resort.
Naming Consistency4/5
Almost all names follow a clean verb_noun snake_case pattern (list_graphs, create_node, set_node_parameter, save_package, cook_sbs). Minor deviations: batch_render is noun_verb where render_batch would be consistent, and auto_layout uses an adjective as the verb. Still highly readable and predictable overall.
Tool Count4/5
22 tools is on the heavy side of the ideal 3-15 range but justified by a genuinely complex node-graph editor domain with graph, node, parameter, layout, and render lifecycle operations. No tool appears redundant; each earns its place. Slightly over but reasonable.
Completeness4/5
Strong lifecycle coverage: graph open/create/save, node CRUD, connections, parameter get/set, frames/comments, layout, output nodes, and multiple render/export paths plus a run_python escape hatch. Minor gaps exist—no delete_graph/close_graph, no delete_frame/delete_comment, no disconnect_nodes, and no way to list available node definitions for create_node. These are workaroundable via run_python or by overwriting.
Maintenance
ActivityMaintained
ResponsivenessNo recent community issues