AnkleBreaker MCP Plugin for Unity

SUPPORTED VERSIONS

• ▸ Unity 6000.0 and newer — officially supported and maintained. That is the version line we develop against, test on, and fix.
• ▸ Earlier versions are outside our scope. The plugin declares 2021.3.18f1 as its floor and the asset does run on 2022.3 LTS today, but those versions are not part of our official target: we make no commitment to keep them working, and version-specific issues there are not prioritised.
• ▸ Windows, macOS and Linux editors alike.

REQUIREMENTS

• ▸ git on the PATH. Unity installs git packages with the git command line client, so without it the one-click install fails with an explanation rather than a silent no-op. Package Manager only reads the PATH at editor startup — install git first, then restart Unity.
• ▸ Node.js 18 or newer for the MCP server, the process your AI client launches. Nothing to clone: npx -y anklebreaker-unity-mcp@latest
• ▸ An MCP-capable AI client. No account with us, no subscription, no key.

WHAT GETS INSTALLED

This asset does not vendor the plugin. It adds com.anklebreaker.unity-mcp through Package Manager, pinned to a published tag, so you can see, audit, update and remove it like any other package.

Why the tag matters. Unity records the resolved commit of a git dependency in packages-lock.json and keeps honouring it, so adding the bare repository URL a second time is a no-op — you press Update and nothing happens. Changing the tag forces a re-resolve, and leaves the project on a version a teammate can reproduce.

ASSEMBLIES

• ▸ AnkleBreaker.MCPForUnity.Editor — the plugin setup and Documentation windows.
• ▸ AnkleBreaker.MCPForUnity.Installer.Editor — identity, presence probe, bridge resolver, update checker and installer. It references nothing, which is what lets it describe a project where the plugin is absent, and keeps its install button alive even if something else in the project fails to compile.

Both are editor-only. There is no runtime assembly, so nothing this asset ships reaches a player build.

EDITOR SURFACES ADDED

• ▸ Tools > AnkleBreaker > MCP For Unity > Dashboard
• ▸ Tools > AnkleBreaker > Dependencies Installer > MCP For Unity
• ▸ Tools > AnkleBreaker > MCP For Unity > Documentation
• ▸ CLICKME.asset at the package root

Three menu items and one asset — that is the whole footprint. Once installed, the plugin adds its own Welcome window (Tools > AnkleBreaker > Unity MCP > Welcome), Dashboard and Action History windows, which the buttons in this asset open for you.

SETUP — ABOUT FIVE MINUTES

1. Import. A setup window opens by itself.
2. Install the plugin — one button.
3. Add one server entry to your AI client. The Documentation window carries the exact block, per client, per OS, with a copy button.
4. Ask your assistant something about the open project. The last step of the plugin's Welcome window opens its Dashboard, which reads the live bridge registry, so it reports the real connection rather than claiming one.

PORTS, AND SEVERAL EDITORS AT ONCE

The plugin assigns itself a free port from 7890-7899, so a second editor never clashes with the first and a restart may land elsewhere. Nothing hardcodes it: both halves read the same shared instance registry — %LOCALAPPDATA%\UnityMCP\ on Windows, ~/.local/share/UnityMCP/ elsewhere — so the server and the editor agree on where an editor is instead of each guessing. Your config entry carries no port at all.

EDITOR SCRIPTING API

Reference AnkleBreaker.MCPForUnity.Installer.Editor from your own editor assembly:

• ▸ MCPForUnityPlugin.IsInstalled and .InstalledVersion — is it here, and which version
• ▸ MCPForUnityPluginInstaller.InstallLatest() — newest release, pinned
• ▸ MCPForUnityPluginInstaller.Install("v1.2.3") — put a whole team on one version through code review
• ▸ MCPForUnityUpdateChecker.Check(force, callback) — cached six hours; force only for an explicit user action
• ▸ MCPForUnityBridge.Resolve() — the live port and ping URL for this editor, never a stored guess

A versionDefines entry only defines its symbol for the assembly that declares it. So if you want to compile against the plugin's own types conditionally, add the same entry to your asmdef — name com.anklebreaker.unity-mcp, define AB_UNITY_MCP — exactly as this package's installer assembly does.

WHAT IT SENDS

The whole package makes exactly one network call: a read of the GitHub API for the plugin's latest release, to learn a version tag. The answer is cached for six hours, so the unauthenticated rate limit is never a problem. Nothing about you or your project is sent anywhere. There is no telemetry and no cloud component in either half.

KNOW THIS BEFORE YOU INSTALL

An assistant connected through the bridge can modify and delete project assets — that is the point of it. Work on a project under version control, and read the plugin's Action History when something surprises you.

LINKS

• ▸ Plugin source — https://github.com/AnkleBreaker-Studio/unity-mcp-plugin
• ▸ MCP server source — https://github.com/AnkleBreaker-Studio/unity-mcp-server
• ▸ Issues — https://github.com/AnkleBreaker-Studio/unity-mcp-plugin/issues