Integrations
Utilizes .NET 9.0 as the foundation for the server component, enabling communication between the Unity plugin and external AI clients, with support for custom tool development in C#.
Acts as an AI-powered gateway between Unity Editor and LLM, allowing manipulation of GameObjects, Components, Assets, and Scenes. Supports creating and managing Unity objects, instantiating prefabs, searching assets, and viewing scene hierarchies with an extensible tool system.
Unity MCP (Server + Plugin)
Unity Version | Editmode | Playmode | Standalone |
---|---|---|---|
2022.3.61f1 | |||
2023.2.20f1 | |||
6000.0.46f1 |
Unity-MCP is a bridge between LLM and Unity. It exposes and explains to LLM Unity's tools. LLM understands the interface and utilizes the tools in the way a user asks.
Connect Unity-MCP to LLM client such as Claude or Cursor using integrated AI Connector
window. Custom clients are supported as well.
The project is designed to let developers to add custom tools soon. After that the next goal is to enable the same features in player's build. For not it works only in Unity Editor.
The system is extensible: you can define custom tool
s directly in your Unity project codebase, exposing new capabilities to the AI or automation clients. This makes Unity-MCP a flexible foundation for building advanced workflows, rapid prototyping, or integrating AI-driven features into your development process.
AI Tools
GameObject
- ✅ Create
- ✅ Destroy
- ✅ Find
- ✅ Modify (tag, layer, name, static)
- ✅ Set parent
- ✅ Duplicate
GameObject.Components
- ✅ Add Component
- ✅ Get Components
- ✅ Modify Component
- ✅
Field
set value
- ✅
- ✅
Property
set value
- ✅
- ✅
Reference
link set
- ✅
- ✅ Destroy Component
- 🔲 Remove missing components
Editor
- ✅ State (Playmode)
- ✅ Get
- ✅ Set
- 🔲 Get Windows
- 🔲 Layer
- 🔲 Get All
- 🔲 Add
- 🔲 Remove
- 🔲 Tag
- 🔲 Get All
- 🔲 Add
- 🔲 Remove
- 🔲 Execute
MenuItem
- 🔲 Run Tests
Editor.Selection
- ✅ Get selection
- ✅ Set selection
Prefabs
- ✅ Instantiate
- 🔲 Create
- ✅ Open
- ✅ Modify (GameObject.Modify)
- ✅ Save
- ✅ Close
Package
- 🔲 Get installed
- 🔲 Install
- 🔲 Remove
- 🔲 Update
Assets
- ✅ Create
- ✅ Find
- ✅ Refresh
- ✅ Read
- ✅ Modify
- ✅ Rename
- ✅ Delete
- ✅ Move
- ✅ Create folder
Scene
- ✅ Create
- ✅ Save
- ✅ Load
- ✅ Unload
- ✅ Get Loaded
- ✅ Get hierarchy
- 🔲 Search (editor)
- 🔲 Raycast (understand volume)
Materials
- ✅ Create
- ✅ Modify (Assets.Modify)
- ✅ Read (Assets.Read)
- ✅ Assign to a Component on a GameObject
Shader
- ✅ List All
Scripts
- ✅ Read
- ✅ Update or Create
- ✅ Delete
Scriptable Object
- 🔲 Create
- 🔲 Read
- 🔲 Modify
- 🔲 Remove
Debug
- 🔲 Read logs (console)
Component
- ✅ Get All
Legend: ✅ = Implemented & available, 🔲 = Planned / Not yet implemented
Installation
- Open command line in Unity project folder
- Run the command
Usage
- Make sure your project path doesn't have a space symbol " ".
- ✅
C:/MyProjects/Project
- ❌
C:/My Projects/Project
- ✅
- Open Unity project, go 👉
Window/AI Connector (Unity-MCP)
.
- Install MCP client
- Install Cursor (recommended)
- Install Claude
- Sign-in into MCP client
- Click
Configure
at your MCP client.
- Restart your MCP client.
- Make sure
AI Connector
is "Connected" or "Connecting..." after restart. - Test AI connection in your Client (Cursor, Claude Desktop). Type any question or task into the chat. Something like:
Add custom tool
⚠️ It only works with MCP client that supports dynamic tool list update.
Unity-MCP is designed to support custom tool
development by project owner. MCP server takes data from Unity plugin and exposes it to a Client. So anyone in the MCP communication chain would receive the information about a new tool
. Which LLM may decide to call at some point.
To add a custom tool
you need:
- To have a class with attribute
McpPluginToolType
. - To have a method in the class with attribute
McpPluginTool
. - [optional] Add
Description
attribute to each method argument to let LLM to understand it. - [optional] Use
string? optional = null
properties with?
and default value to mark them asoptional
for LLM.
Take a look that the line
MainThread.Run(() =>
it allows to run the code in Main thread which is needed to interact with Unity API. If you don't need it and running the tool in background thread is fine for the tool, don't use Main thread for efficiency purpose.
Add custom in-game tool
⚠️ Not yet supported. The work is in progress
Contribution
Feel free to add new tool
into the project.
- Fork the project.
- Implement new
tool
in your forked repository. - Create Pull Request into original Unity-MCP repository.
This server cannot be installed
Seamless automation and intelligent control over your Unity projects. By integrating with the MCP server and client, it allows AI agents or external tools to interact with your Unity environment—creating, modifying, and managing GameObjects, Components, Assets, Scenes, and more.
Related MCP Servers
- AsecurityAlicenseAqualityMCP Unity Server to integrate Unity Editor game engine with different AI Model clients (e.g. Claude Desktop, Windsurf, Cursor)Last updated -5449MIT License
- -securityAlicense-qualityAn MCP server implementation that standardizes how AI applications access tools and context, providing a central hub that manages tool discovery, execution, and context management with a simplified configuration system.Last updated -9PythonMIT License
- -securityAlicense-qualityA Unity Master Control Protocol implementation that allows AI agents to control and interact with Unity, enabling them to execute code, query editor state, modify GameObjects, and capture screenshots through a WebSocket-based communication system.Last updated -7MIT License
- -securityAlicense-qualityA server that enables AI assistants to understand and interact with Unity projects in real-time, providing access to scene hierarchy, project settings, and the ability to execute code directly in the Unity Editor.Last updated -40MIT License