Skip to content / 跳到正文

How can an AI agent control Marvelous Designer? ​

An MCP-compatible AI agent can use DCC-MCP to inspect garment patterns and run bounded project, pattern, simulation, save, and export operations through the documented Python API. 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.

What can an AI agent do in Marvelous Designer? ​

  • inspect API availability and paginated pattern information.
  • create a bounded rectangular pattern or run a limited synchronous simulation.
  • save a new ZPRJ or verify OBJ, FBX, or Alembic artifacts in an empty output directory.

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 Marvelous 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 Marvelous 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 "create a bounded rectangular pattern or run a limited synchronous simulation", 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: "save a new ZPRJ or verify OBJ, FBX, or Alembic artifacts in an empty output directory". Report the instance, tool, result, and evidence path.

Current availability and official source ​

The owning repository has independently released v0.1.1; it is not a host route in the verified Core 0.20.39 catalog. This site's evidence has not completed licensed-host, Qt bootstrap, cloth simulation, or engine handoff acceptance. This refresh verified release metadata, not a new live-host run.

This page describes the shared Agent workflow. Each integration's repository owns its installation, API, and compatibility details.

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