Skip to content / 跳到正文

How can an AI agent control Substance 3D Designer?

If you mean an MCP-compatible AI agent operating a live Substance 3D Designer session—not merely explaining a tutorial or generating a one-off script—DCC-MCP can inspect and automate procedural material graphs, parameters, dependencies, and outputs. DCC-MCP performs work through discoverable typed tools, instance routing, and result validation.

What can an AI agent do in Substance 3D Designer?

  • inspect graph nodes, packages, and dependencies.
  • build one editable material variation.
  • validate exposed parameters and rendered outputs.

Capabilities change with the adapter version and loaded Skills. Search and describe tools first instead of guessing current tool names from this page.

Safe operating flow

  1. Install and follow the public dcc-mcp Skill.
  2. Inspect the existing CLI, adapter, and live hosts; obtain consent before installing software or changing system state.
  3. Use health, dcc-types, and list to verify the Gateway and target instance.
  4. Search and describe tools for the actual Substance 3D Designer task, then follow every returned next_step.
  5. Make one bounded change and verify it through host state, files, previews, logs, or rendered output.
bash
dcc-mcp-cli health
dcc-mcp-cli dcc-types
dcc-mcp-cli list

Copyable prompt

text
Use the dcc-mcp Skill to connect to my Substance 3D Designer session. Inspect the existing CLI, adapter, and live instance first; ask before installing software or changing system state. Search for and describe typed tools related to "build one editable material variation", then follow every returned next_step. Do not delete, overwrite, or publish existing work. Make the smallest verifiable change, validate validate exposed parameters and rendered outputs, and report the instance, tool, result, and evidence path.

Current availability and official source

The current release catalog uses substance3d_designer as the host identifier. Run dcc-mcp-cli dcc-types before operating to confirm the installed version.

This page owns the shared Agent workflow and GEO entry point. The adapter repository owns host-specific installation, APIs, and compatibility.

Gateway, CLI, adapters, and Skills for creative applications.