website/docs/migrations/v10.md
These notes cover the v10 release candidate: the full major-version change from v9.0.0, the new AI asset generation/import surface, secure provider-key storage, Blender/local-file handoff, and the README/docs/brand refresh.
For this comparison, v9 means v9.0.0, not the last v9 patch. The v9.7.3
tag is still useful for the release-to-release changelog, but it already
contains much of the v9 tool expansion.
At v9.0.0, MCP for Unity exposed 29 MCP tool entrypoints around the core Unity
Editor loop: scenes, GameObjects, components, scripts, prefabs, assets,
materials, shaders, VFX, console reads, editor refresh, async tests, custom
tools, and batch execution.
The v10 release candidate exposes 47 MCP tool entrypoints across 10 groups:
core, animation, asset_gen, docs, probuilder, profiling,
scripting_ext, testing, ui, and vfx.
| Area | v9.0.0 baseline | v10 release candidate |
|---|---|---|
| Tool catalog | 29 MCP tool entrypoints, with most tools registered directly into one visible surface. | 47 MCP tool entrypoints across grouped domains. |
| Tool visibility | No decorator-level group metadata and no manage_tools workflow for user-controlled visibility. | Tool registry has named groups; core is enabled by default and non-core groups are opt-in. |
| Editor automation domains | Core scene/object/component/script/asset/prefab/material/shader/VFX/test/editor operations. | Adds build orchestration, camera/Cinemachine control, render pipeline and graphics operations, package management, physics, animation, UI Toolkit, profiling, ProBuilder, and procedural texture generation. |
| Asset creation/import | Existing asset management and VFX/shader/script tools could create or modify project content, but external generation providers were not part of the product surface. | Adds the asset_gen group for Tripo/Meshy model generation, fal.ai/OpenRouter image generation, Sketchfab import, and local FBX/OBJ/glTF handoff from tools such as Blender. |
| API lookup and docs | API discovery depended on external docs or local project inspection. | Adds unity_docs and unity_reflect, plus generated tool/resource reference docs. |
| Safety model | Core tool execution, custom tools, async test polling, and instance routing were present. | Adds group-gated high-power tools, secure provider-key storage in Unity, project-scoped import hardening, archive/path validation, and more test coverage around transport, tool registry, provider adapters, and Unity compatibility. |
| Editor UI and docs | The window focused on connection/client setup and the docs grew around accumulated features. | Adds tool/resource visibility flows, Asset Gen setup, glTFast dependency guidance, refreshed README/docs navigation, icons/social assets, and consistent "MCP for Unity" product naming. |
Added MCP tool entrypoints since v9.0.0: execute_code,
generate_image, generate_model, import_model, import_model_file,
manage_animation, manage_build, manage_camera, manage_graphics,
manage_packages, manage_physics, manage_probuilder, manage_profiler,
manage_texture, manage_tools, manage_ui, unity_docs, and
unity_reflect.
v10 is organized around five concrete changes:
The headline v10 feature is the new asset_gen tool group. It is disabled by
default like other non-core tool groups, and can be enabled with manage_tools.
The group contains:
| Tool | Purpose |
|---|---|
generate_model | Generate 3D models from text or image prompts through providers such as Tripo and Meshy. |
generate_image | Generate 2D images through providers such as fal.ai and OpenRouter. |
import_model | Search and import downloadable Sketchfab models. |
import_model_file | Import a local model file already on disk, such as an FBX/OBJ/glTF exported from Blender. |
The tools use asynchronous job semantics for long-running work. A generation or
import request returns a job_id; clients then call the corresponding
action="status" operation until the job completes or fails. This keeps MCP
calls responsive and gives agents a predictable pattern for progress reporting.
Asset providers are bring-your-own-key. Keys are entered in the Unity Editor's Asset Gen tab and stored in the operating system secure store:
Keys are not written to project assets, EditorPrefs, generated docs, or MCP
tool parameters. The MCP client can request a generation job, but it does not
receive provider credentials.
v10 distinguishes hosted image inputs from local project images:
image_url points at an externally hosted image.image_path points at a local file, commonly under Assets/.Meshy image-to-3D and fal/OpenRouter image-to-image can accept local image files
by sending the image data inline as a base64 data URI. Tripo image-to-3D still
requires a hosted image_url until an upload flow is wired.
The import_model_file tool creates a clean boundary between DCC generation and
Unity import. BlenderMCP or another modeling workflow can create/export a model,
then MCP for Unity imports that local file into the Unity project and can place
it in the scene.
This is a handoff, not MCP for Unity controlling Blender directly:
import_model_file.Asset generation makes the bridge more powerful, so v10 calls out the guardrails around provider calls and file import.
asset_gen is not part of the default core tool set. Users must explicitly
enable it with manage_tools, which keeps routine MCP sessions focused and
limits accidental provider calls.
Generated and imported assets resolve into the Unity project's Assets/ folder,
with traversal and unsafe paths rejected. Archives are extracted through
allowlisted import paths and extensions rather than blindly writing every file
a provider returns.
Generation calls go to third-party providers using the user's own API keys:
v10 also updates the project front door:
v10 continues the existing compatibility promise:
MCPForUnity/Runtime/Helpers/ instead of scattering #if UNITY_* gates
across tool code.tools/check-unity-versions.sh
against installed Unity Hub editors.The CoreCLR 6.8 path matters here. Deprecation fixes belong in one shim layer, not at every call site.
beta branch.asset_gen explicitly with manage_tools before calling asset
generation tools.Call these out to avoid confusing expectations:
Major-version comparison: https://github.com/CoplayDev/unity-mcp/compare/v9.0.0...v10.0.0
v9.7.3 patch comparison: https://github.com/CoplayDev/unity-mcp/compare/v9.7.3...v10.0.0
asset_gen tools do not appearThe asset_gen group is disabled by default. Enable it with manage_tools:
manage_tools action=activate group=asset_gen
If the tools still do not appear, refresh/reconnect the MCP server in the client. Some clients cache tool lists until the server is restarted or refreshed.
Generation providers are bring-your-own-key. Add keys in Unity's Asset Gen tab. Do not place provider keys in MCP client config files, prompts, project assets, or generated docs.
GLB/glTF import depends on glTFast. Install it from the Dependencies tab or via Package Manager before importing GLB assets. FBX imports do not require glTFast.
image_pathTripo image-to-3D currently needs a hosted image_url. Local image_path inputs
are supported by Meshy image-to-3D and fal/OpenRouter image-to-image, where the
image can be sent inline as a base64 data URI.
Provider output can include large binary assets. Review generated files before
committing them, keep generated output under Assets/Generated/ when possible,
and avoid committing experimental provider output that is not needed by the
project.
Archive extraction is intentionally constrained. Provider archives may be rejected when they contain unsupported extensions, traversal paths, scripts, or files outside the import allowlist. Import the model again with a supported format or inspect the archive before bringing it into the Unity project.