Substance Painter MCP
Related Servers
Alternatives to Substance Painter MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables conversational control of Adobe Substance 3D Painter for look-dev iteration, including baking, smart materials, and generator parameter tuning.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to control Substance 3D Painter, inspecting projects and exporting texture sets via a secure preset-based tool.37 PyPI1MIT
- 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.-
- AlicenseNot gradedqualityBmaintenanceEnables 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.2MIT
- AlicenseBqualityDmaintenanceEnables Claude AI to directly control Blender for automated 3D modeling, scene creation, and object manipulation. It provides tools for material management, scene inspection, and integration with third-party asset libraries like Poly Haven and Sketchfab.102MIT
- AlicenseBqualityDmaintenanceEnables Claude AI to interact with and control Blender for 3D modeling, scene creation, and manipulation.22MIT
TDQS
Scored across 86 tools
The domain is genuinely large, and most tools state a distinct target (e.g., set_fill_base_color vs set_fill_channels vs set_fill_parameters). However, several clusters overlap heavily — three capture_* tools, set_fill_projection vs set_fill_projection_advanced, insert_content_effect vs insert_mask_effect vs insert_smart_material, and apply_smart_mask vs set_layer_mask — forcing an agent to read long descriptions to choose correctly.
Nearly everything follows a snake_case verb_noun pattern (list_*, get_*, set_*, create_*, plan_*, start_*_job, get_*_job), which is predictable and readable. Minor deviations like painter_status (noun-first) and the mix of plan/start/get_job job-lifecycle verbs are the only friction.
86 tools is far beyond what an agent can reliably navigate in one surface; the plan/start/get_job triples alone multiply the tool count considerably. This is an extreme mismatch for a single server, even given the breadth of Substance Painter.
Coverage is unusually thorough: project lifecycle, layers, masks, fills/generators, baking, mesh reload, export/import, resources, and job polling are all represented with verification and rollback. Gaps like undo/redo, texture-set creation, and resource deletion are minor workarounds rather than dead ends.