How can an AI agent control Unity?

An MCP-compatible AI agent can use DCC-MCP to inspect projects and automate scenes, GameObjects, components, assets, tests, and builds. 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.

Unity MCP and Unity CLI

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

dcc-mcp-cli search --query "inventory scenes, assets, and project settings" --dcc-type unity

Vendor-native AI capabilities

For Unity and Tuanjie AI projects, the unity-tuanjie-ai Skill inspects the native Codely CustomTool catalog and only executes a tool from a fresh inspection result. Tuanjie owns sign-in, credits, downloads, and task recovery; DCC-MCP owns typed discovery, routing, and verification around those vendor capabilities.

What can an AI agent do in Unity?

• inventory scenes, assets, and project settings.
• build one small playable interaction.
• enter Play Mode and verify behavior before a build.

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 Unity 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 Unity 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 small playable interaction", 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: "enter Play Mode and verify behavior before a build". Report the instance, tool, result, and evidence path.

Current availability and official source

The current catalog lists unity 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.

• Unity 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.