How can an AI agent control Material Maker?

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

What can an AI agent do in Material Maker?

• inspect graph nodes and exposed parameters.
• build one editable procedural material.
• verify seamless outputs and exported maps.

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 Material Maker task, then follow every returned next_step.
5. Make one bounded change and verify it through host state, files, previews, logs, or rendered output.

dcc-mcp-cli health
dcc-mcp-cli dcc-types
dcc-mcp-cli list

Copyable prompt

Use the dcc-mcp Skill to connect to my Material Maker 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 procedural material", then follow every returned next_step. Do not delete, overwrite, or publish existing work. Make the smallest verifiable change, validate verify seamless outputs and exported maps, and report the instance, tool, result, and evidence path.

Current availability and official source

This is a public adapter repository, but it may not yet be present in the current CLI release catalog. Check its README and dcc-mcp-cli dcc-types; do not guess a host identifier.

• Material Maker adapter repository: source of truth for installation, compatibility, host-specific capabilities, and troubleshooting.
• All AI + DCC control guides: return to every public application and pipeline integration.
• Agent workflow: shared discovery, call, validation, and diagnostic steps.

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