Control Unity Editor from AI agents. 200+ MCP tools for GameObjects, Scenes, Assets, Materials, Prefabs, Terrain, Physics, Lighting, and more. Works with Claude, Cursor, Windsurf, VS Code Copilot — any MCP client. Zero config: just npx and go.
Overview
Control Unity Editor from Any AI Agent
uac-mcp-server bridges AI agents to Unity Editor via the Model Context Protocol. Create GameObjects, build scenes, manage assets, configure materials — all from natural language.
200+ Tools
- GameObjects — Create, delete, transform, clone, tag, layer, add/remove components
- Scenes — Open, save, create, close, list loaded scenes
- Assets — Create, delete, rename, move, search
- Materials — Set colors, textures, shaders, floats
- Prefabs — Create, instantiate, apply overrides, unpack
- Build — Switch platform, configure player settings, start builds
- Terrain — Heightmaps, paint, trees, grass, layers
- Physics — Rigidbodies, colliders, raycasts, joints
- Lighting — Create lights, reflection probes, bake lightmaps
- Animation — Animators, controllers, states, clips
- UI — Canvas, buttons, text, layout elements
- Camera — Create, configure, take screenshots
- Console — Read logs, errors, clear output
- And more: Navigation, Particles, Audio, Timeline, Addressables...
Quick Setup
npx -y uac-mcp-serverWorks with Claude Desktop, Claude Code, Cursor, Windsurf, VS Code Copilot, and any MCP-compatible client.
How It Works
The server auto-discovers all endpoints from the Unity API Communicator plugin running in your Unity Editor. 54 core tools have fully typed Zod schemas for precise parameter handling. All other endpoints are registered with generic schemas — the AI figures out the parameters from tool descriptions.
Prerequisites
- Unity API Communicator plugin installed in Unity Editor
- Node.js 18+
Links
Server Config
{
"mcpServers": {
"unity": {
"command": "npx",
"args": [
"-y",
"uac-mcp-server"
]
}
}
}