This skill should be used when the user asks about "MCP tools", "Unity MCP", "enable tool groups", "which MCP tools", "create GameObject", "add component", "run Unity tests", "check scene hierarchy", "spawn agent for Unity", "MCP not working", or needs to coordinate Unity Editor operations via MCP.
Expert knowledge for coordinating Unity MCP operations, including tool enablement, agent orchestration, and direct MCP tool usage.
CRITICAL: The MCP Resource is ALWAYS enabled and never disabled - no tool enablement needed. This is the primary way agents inspect Unity.
How to Access (works for all agents including subagents):
Tool: ReadMcpResourceTool
Server: ai-game-developer
URI: unity://gameobject/{scene}/{path}
Example:
{
"server": "ai-game-developer",
"uri": "unity://gameobject/GameplayScene/TileManager"
}
Returns: Transform, components, properties, children
Resource vs Tools Decision Table:
| Need | Use |
|---|---|
| Inspect scene structure | MCP Resource (always available) |
| Read component values | MCP Resource (always available) |
| Create/modify objects | MCP Tools (require enablement) |
| Run tests | MCP Tools (require enablement) |
Most agents should use this resource for read operations before enabling any tools.
Run /unity-mcp-enable [groups] before instructing agents that need MCP to fulfill a task.
Include unity-mcp-tools skill for agents doing MCP work:
| Task | Enable Groups | Spawn Agent |
|---|---|---|
| Create/modify GameObjects | gameobject, component | scene-builder |
| Add UI elements | gameobject, component | ui-ux-developer |
| Run tests | testing | test-engineer |
| Work with scripts | script | code-architect |
| Create prefabs | prefab, gameobject | scene-builder |
| Deploy build | (none) | deployment-specialist |
Run /unity-mcp-reset to disable tools and save context.
Subagents cannot use these commands, but claude code can trigger them or ask the user to use them.
| Command | Purpose |
|---|---|
/unity-mcp-status | Show enabled groups |
/unity-mcp-enable [groups] | Enable tool groups |
/unity-mcp-enable-all | Enable all tools |
/unity-mcp-reset | Disable all tools |
/unity-mcp-scene-info [path] | Query scene via Resource |
Spawn the mcp-advisor advisory agent when:
Example prompt: "What MCP tool groups do I need to add a health bar UI?"
The mcp-advisor returns recommendations - it does not execute commands.
When spawning agents, include these skills:
| Agent | Skills to Include |
|---|---|
| scene-builder | unity-mcp-tools, layout-sizing, visual-style-guide |
| test-engineer | unity-mcp-tools, unity-testing |
| ui-ux-developer | layout-sizing, visual-style-guide |
| input-developer | board-sdk, unity-mcp-tools |
| code-architect | project-architecture |
| game-designer | zero-day-rules |
| deployment-specialist | (none - uses Bash) |
| project-producer | documentation |
| mcp-advisor | unity-mcp-tools |
Subagents can use MCP tools directly when:
AI-Game-Developer-Config.jsontools: field in frontmatter)To give MCP access, omit the tools field:
---