You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: Assets/root/Documentation~/README.md
+20-11Lines changed: 20 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,14 +1,14 @@
1
-
# Unity MCP (Server + Plugin)
1
+
# Unity MCP (AI Connector)
2
2
3
3
[](https://openupm.com/packages/com.ivanmurzak.unity.mcp/)[](https://stand-with-ukraine.pp.ua)
**[Unity-MCP](https://github.com/IvanMurzak/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.
14
14
@@ -20,6 +20,13 @@ The system is extensible: you can define custom `tool`s directly in your Unity p
20
20
21
21
## AI Tools
22
22
23
+
Unity-MCP supports a wide range of tools. Each tool is a small connector between LLM and Unity Engine. You may create your own `tools` by using API, take a look at [add custom tool](#add-custom-tool).
24
+
25
+
Here is the list of default AI tools. All of them are available after installation Unity-MCP into your project.
@@ -233,11 +237,16 @@ public class Tool_GameObject
233
237
234
238
> ⚠️ Not yet supported. The work is in progress
235
239
240
+
# Running PlayMode tests
241
+
242
+
To be able to run Play Mode tests via the TestRunner MCP tool, you should consider configuring Unity to **not** perform a domain reload when entering Play Mode (`Edit -> Project Settings -> Editor -> Enter Play Mode Settings` - set to `Reload Scene only` or `Do not reload Domain or Scene`). Otherwise, starting the Play Mode tests will interrupt the TestRunner MCP tool, leading to a cycle of tests restarting.
243
+
236
244
237
245
# Contribution
238
246
239
-
Feel free to add new `tool` into the project.
247
+
Feel free to add a new `tool` into the project.
240
248
241
249
1. Fork the project.
242
-
2. Implement new `tool` in your forked repository.
243
-
3. Create Pull Request into original [Unity-MCP](https://github.com/IvanMurzak/Unity-MCP) repository.
250
+
2. Clone the fork and open the resulting folder in Unity.
251
+
3. Implement the new `tool` in your forked repository.
252
+
4. Create Pull Request into original [Unity-MCP](https://github.com/IvanMurzak/Unity-MCP) repository.
0 commit comments