Scripts Compile but Hierarchy Is Off? Game Dev UI Handoff and MCP Checklist

In indie and small-team dev, the usual blocker is not “I cannot write C# / GDScript”—it is scripts compile, open the Scene, and nothing lines up: buttons miss hits.

The root cause is rarely a weak AI model. It is mixing UI shell handoff and gameplay logic on the same toolchain. Below: common failure modes, an acceptance checklist, and where Engine MCP (Unity MCP / Godot MCP / Cocos MCP) should enter the pipeline.

---

Two jobs—do not force one AI tool to do both

Job	Typical output	Better tool
UI shell	Canvas / Control tree, Prefab, anchors, slice naming	Structured design import (PSD / Figma → engine)
Gameplay logic	Button events, stats, state machines, Play debugging	Cursor / Claude Code + Engine MCP

Cursor, Copilot, Claude Code by default see repo text. They do not see:

• Unsaved scene edits in the editor
• Current selection, broken prefab references
• Console and transient UI state in Play mode

So AI fixes .cs while Btn_Start still has no OnClick in Hierarchy—that is not a prompt problem, it is missing editor bridge. MCP fills that gap. Category map: AI tools for Godot / Unity.

---

After UI import: 10 engineering checks

After design or Studio exports a Prefab, run this before first Play (Unity UGUI examples; Godot / Cocos map similarly):

#	Check	Common failure
1	Root Canvas / Control and resolution policy	Wrong Canvas Scaler; portrait Safe Area clipped
2	Hit area separate from decoration	Transparent image blocks Raycast
3	Button normal / pressed / disabled	Single static image only
4	Text maps to TMP / Label	Full-screen display type, no localization
5	Node names script-friendly (Btn_*, Panel_*)	Layer 47 copy
6	Anchor / 9-slice and stretch rules	Layout drifts on resolution change
7	Atlas and draw calls acceptable	One oversized PNG per control
8	Import paths match project conventions	MCP cannot find Prefab path
9	Commit before binding logic	AI edits script; references drop
10	Play once at 16:9 and target portrait	Only tested Editor window aspect

Structured import vs manual slice: Figma → Unity without manual slicing, in-place UI split.

---

When to install Engine MCP

Situation	Recommendation
Daily gameplay changes, frequent Play / Console	Install the matching Engine MCP
UI still rebuilt by manual slice every week	Fix shell first (Studio / spec handoff), then MCP
Scripts only, rarely touch Scene	Limited MCP benefit
Game Jam, playable same day	Studio for UI + MCP for buttons (walkthrough)

Godot MCP is open source—good for validating workflow first: install · when manual vs MCP. Unity / Cocos: official Pro packages—Unity MCP install · Cocos 3.x.

Three-engine pick: Godot MCP vs Unity MCP vs Cocos MCP.

---

Recommended split (engineering view)

Design file / full-screen UI art
 → AI Studio: import · split · export Prefab (Unity / Godot / Cocos)
 → Engineering runs the 10 checks above
 → Cursor + Engine MCP: bind OnClick, HUD, stats, Play debug

Change type	Route
Theme swap / localized copy / full-screen reskin	Studio re-export (reskin, translate)
Feel, collision, AI, saves, bugs	MCP + hand-reviewed code
Damage numbers, pixel type	Bitmap font or TMP

Rule of thumb: Studio for shell, MCP for wiring. Do not ask MCP to build an entire HUD from scratch; do not write combat FSM inside the canvas tool.

---

After MCP is wired: 3 practices

1. Prompts must be verifiable—Prefab path.
2. Small commits—one change at a time: “Start button → load level,” then enemy AI.
3. MCP does not replace QA—model-generated node edits still need Play; it saves clicks.

Cursor and Claude Code with Unity: Unity MCP workflow guide, Claude Code connect Unity MCP.

Tool combo and one-week rollout: 2026 game dev AI efficiency.

FAQ

Cursor is enough—do I need MCP? Enough for scripts; when you touch Scene tree.

Can MCP replace UI slicing? No. MCP manages in-editor objects; UI structure still needs Prefab-level handoff (Studio or spec PSD / Figma flow).

One engine only—still learn Studio? Worth it if UI revisions eat time rebuilding Canvas; if UI is minimal.

Godot small project—install what first? Try Godot MCP (open source) first; add AI Studio when UI handoff hurts.

Conflict with Unity AI UI Generator? No conflict. Unity AI leans editor sprites; for multi-engine or structured PSD/Figma import.