An assistant that can describe a scene and an assistant that can change it need different checks. Establish that boundary before opening a valuable Unity project.
What changed in version 1.5.0
The October 24 release of AI Game Developer, also called Unity MCP, adds a standalone CLI and App skills metadata. It includes fixes for generating executable commands appropriate to the host platform.
This is IvanMurzak’s community project. It should remain distinct from Unity Technologies’ official Agent Plugin, which serves a different integration path.
The pinned release license is Apache 2.0. License availability does not establish that a particular editor connection is configured correctly.
Resources and tools have different effects
The release documentation distinguishes read-only MCP resources from tools that perform actions. Resources can expose project context; tools can change the editor’s state.
Inventory the capabilities offered to the assistant before choosing a task. A request to inspect an object should not silently become permission to alter its components or scene.
The documentation also describes authentication and transport options. Review the actual configuration rather than assuming that an authentication feature implies a suitable default.
Use a disposable scene for the first trial
I would create a small test project with one scene and a known starting state. Save that state before connecting an agent.
- Ask for a read-only inventory of the scene.
- Compare the reported objects and components with the editor.
- Authorize one small, reversible scene change.
- Inspect the actual change and save the resulting diff.
- Disconnect the integration and verify its access state.
Choose an edit with a clear acceptance condition, such as moving a named object to an agreed position. Keep package installation and external publishing outside that initial trial.
Record the host and the project result
A host-specific command fix reminds you to retain the operating system, package version, and generated command in the test record. The same instructions can behave differently on another machine.
Check the saved scene as well as the editor’s current view. A visible edit may remain unsaved, while an unexpected serialized change can persist after the session ends.
We have not installed or tested this release. Its release notes establish the published changes; your integration result needs its own editor and project evidence.
Our official Unity Agent Plugin article explains the separate Unity-supported workflow. The Agent Skills portability guide covers host dependencies that can affect imported instructions.
Sources
- Version 1.5.0 release and change list
- Resources, tools and integration configuration
- Pinned Apache 2.0 license
Which scene change would give you a clear, reversible test of the editor connection?
Checked October 25, 2026. Prepared with AI-assisted research and drafting, with claims checked against the linked sources. MustHave.ai has not performed the proposed product tests.
