MCP for Unity is CoplayDev’s MIT-licensed Model Context Protocol bridge for connecting AI assistants to the Unity Editor. It gives compatible clients a Unity-aware tool surface instead of treating a game project as only a collection of text files. The upstream project is community maintained and explicitly states that it is not affiliated with Unity Technologies, so this page uses the product name only to describe the editor it integrates with and does not present the server as an official Unity offering.
Its tools can manage assets, inspect and control scenes and GameObjects, edit scripts, run tests, profile editor activity, and automate other game-development tasks exposed by the package. That structured editor context can help an agent coordinate code changes with scene and asset state, but it does not guarantee that generated scripts, scene edits, builds, or tests are correct. Developers should review changes in a copy or version-controlled branch, run the project’s own test and play-mode checks, and keep backups for asset or scene operations that are difficult to reverse.
Current upstream requirements cover Unity 2021.3 LTS through Unity 6.x plus Python 3.10 or later through the documented uv-based server setup. The package can be installed through Unity Package Manager or OpenUPM and configured for common MCP clients from the editor. Availability and compatibility can vary by Unity release, package version, client, and local project configuration; teams should follow the tagged release instructions rather than assuming that a main or beta branch is stable for every production project.
