Extensions
Unity MCP extensions add AI support for Animation, Cinemachine, Input System, Navigation, ProBuilder, Splines, Terrain, Tilemap, Timeline and particles.
Extensions are optional Unity packages that teach the AI agent about specific Unity features, such as Cinemachine cameras, ProBuilder meshes or 2D tilemaps. Install only the ones your project uses. This page lists the ten official extensions, what each one adds and how to install it. Each extension also has a detail page in the Unity extensions catalog.
How extensions work
Since Unity MCP 1.0.0 (and extension version 2.0.0) an extension adds no new MCP tools. Instead it contributes an RQL module: new sources, functions and type adapters that the existing rql-query and rql-mutate tools understand. The agent's tool list stays the same size, and the extension's guide is added to the generated unity-rql skill, so the agent learns the new syntax as soon as the package is installed and skills are regenerated.
For example, with AI Tilemap installed the agent can paint tiles through RQL:
objects | get components | where $ is Tilemap | call BoxFill("Assets/Tiles/Grass.asset", -5, -3, 5, 3)Each extension depends on the core plugin, com.ivanmurzak.unity.mcp, and on the Unity package it builds on. Installing it pulls both in. All of them support Unity 2022.3 and newer.
The official extensions
| Extension | Package id | Builds on | RQL additions |
|---|---|---|---|
| AI Animation | com.ivanmurzak.unity.mcp.animation | Animation module | animation source; AnimationClip, AnimatorController and Animator types |
| AI Cinemachine | com.ivanmurzak.unity.mcp.cinemachine | com.unity.cinemachine | cinemachine source; CinemachineCamera, CinemachineBrain |
| AI InputSystem | com.ivanmurzak.unity.mcp.inputsystem | com.unity.inputsystem | input source; InputActionAsset |
| AI Navigation | com.ivanmurzak.unity.mcp.navigation | com.unity.ai.navigation | navigation source; NavMeshSurface, NavMeshLink, NavMeshAgent |
| AI Particle System | com.ivanmurzak.unity.mcp.particlesystem | Particle System module | ParticleSystem and its modules, curves and gradients |
| AI ProBuilder | com.ivanmurzak.unity.mcp.probuilder | com.unity.probuilder | probuilder source and functions; ProBuilderMesh |
| AI Splines | com.ivanmurzak.unity.mcp.splines | com.unity.splines | splines source; SplineContainer |
| AI Terrain | com.ivanmurzak.unity.mcp.terrain | Terrain modules | terrain source; height functions; Terrain, TerrainData |
| AI Tilemap | com.ivanmurzak.unity.mcp.tilemap | Tilemap module and 2D Tilemap Extras | tilemap source and functions; Tilemap, RuleTile |
| AI Timeline | com.ivanmurzak.unity.mcp.timeline | com.unity.timeline | timeline source; TimelineAsset, tracks, clips, PlayableDirector |
The exact sources, functions and calls of each module are on its catalog page and, inside the Editor, in rql-schema.
Install from the AI Game Developer window
- Open Window > AI Game Developer — MCP.
- Scroll to Extensions.
- Click Install next to the extension you want.
The window adds the OpenUPM scoped registry and the package to Packages/manifest.json, at the latest version on OpenUPM. Unity then resolves and imports it.
Install with unity-mcp-cli
unity-mcp-cli install-extension --list
unity-mcp-cli install-extension Tilemap ./MyUnityProjectThe id can be the catalogue name (Tilemap, Cinemachine, ProBuilder, …) or the package id (com.ivanmurzak.unity.mcp.tilemap), matched case-insensitively. The path defaults to the current folder. The command resolves the latest OpenUPM version, never downgrades a higher installed version, and does nothing if the extension is already up to date. Pin a version with --extension-version <version> (not --version, which prints the CLI version). Open or focus Unity afterwards so the Package Manager resolves it.
Install with OpenUPM
openupm add com.ivanmurzak.unity.mcp.cinemachineEach extension's README in the Unity-MCP repository also links a .unitypackage installer for that extension, which works like the core installer.
Install with the desktop app
The AI Game Dev app can install Unity extensions into the open project as well. It uses each extension's own OpenUPM version, which is independent of the core plugin version. See the app documentation.
After installing
- Regenerate skills (Skills > Generate in the window, or
unity-mcp-cli setup-skills <agent>) so the agent'sunity-rqlskill includes the new module. - Ask the agent to start from
rql-schemaif it seems unaware of the new types, for example "Use rql-schema to see what the cinemachine source offers, then add a follow camera for the Player." - Tool names from older tutorials, such as
tilemap-set-tileorcinemachine-camera-create, no longer exist. Each extension's README maps them to the RQL equivalent.
Updating and removing
Extensions are versioned separately from the core plugin. Update them in the Package Manager or by re-running install-extension. Remove one in the Package Manager like any other package. Keep the core plugin and the extensions on current versions together: extensions declare the minimum core version they need.
Writing your own
Your project code can add tools directly (see Custom tools) or teach RQL about your own types with custom RQL adapters. The repository's extension guide describes how the official extensions are built and tested.