How can an AI agent control ZBrush?

An MCP-compatible AI agent can use DCC-MCP to inspect documents and automate tools, subtools, sculpting operations, remeshing, and export. The agent selects the correct application instance or integration, discovers available tools, and reads their parameter definitions before acting and checking the result. These typed tools declare their inputs, outputs, and parameter types.

ZBrush MCP and ZBrush CLI

The ZBrush MCP endpoint and ZBrush CLI workflow share the same DCC-MCP adapter and tool catalog. Use dcc-mcp-cli with --dcc-type zbrush to limit tool searches to ZBrush. Tools declare their inputs, outputs, and parameter types so arguments can be checked before a call.

dcc-mcp-cli search --query "inspect active tools, subtools, and mesh state" --dcc-type zbrush

What can an AI agent do in ZBrush?

• inspect active tools, subtools, and mesh state.
• perform one bounded sculpting or remesh operation.
• validate topology, subdivision state, and exported geometry.

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 ZBrush 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 ZBrush 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 "perform one bounded sculpting or remesh operation", then follow every returned next_step. Do not delete, overwrite, or publish existing work. Make the smallest verifiable change, then check the result against this requirement: "validate topology, subdivision state, and exported geometry". Report the instance, tool, result, and evidence path.

Current availability and official source

The current catalog lists zbrush as the adapter identifier. Catalog definitions do not establish host acceptance; run dcc-mcp-cli dcc-types, then discover and describe the live instance's tools before operating.

• ZBrush 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 describes the shared Agent workflow. Each integration's repository owns its installation, API, and compatibility details.