Unity MCP — Control Unity Editor from Agents

Practical Notes

• Release notes in README show versioned tool growth (for example v9.6.1 adds build tooling and multi-scene ops)
• Performance tip: README claims batch_execute can be 10–100× faster than individual calls

Treat Unity as an API, Not a GUI

The win is not “an LLM can click buttons” — it’s that your editor workflow becomes a repeatable tool contract:

• Use batch_execute for multi-step operations so you get one atomic-ish plan and fewer round-trips.
• Route requests to the correct Unity instance when you have multiple editors open.
• Keep transports local-first (loopback) unless you truly need LAN binding.

Once connected, you can standardize tasks:

• “Create a new scene from template, add a prefab, set lighting defaults”
• “Scan packages, add a scoped registry, then validate compile”
• “Build a player with a known profile and export artifacts”

That makes AI-assisted Unity work auditable: every change is a tool call you can reproduce.

FAQ

Q: Do I need Python? A: Yes. The README lists Python 3.10+ and uv as requirements for the bridge/server pieces.

Q: Which transport should I start with? A: HTTP localhost is the default and works with many clients; stdio is also available.

Q: How do I speed up multi-step edits? A: Use batch_execute (README claims 10–100× faster).