Skillget

Unity-Open-MCP

mcp
Security Audit
Warn
Health Warn
  • License — License: MIT
  • Description — Repository has a description
  • Active repo — Last push 0 days ago
  • Low visibility — Only 5 GitHub stars
Code Pass
  • Code scan — Scanned 12 files during light audit, no dangerous patterns found
Permissions Pass
  • Permissions — No dangerous permissions requested

No AI report is available for this listing yet.

SUMMARY

Unity-Open-MCP is a complete set of tools to use AI with Unity. It acts as a bridge between AI agents (like Claude Code, Cursor, ZCode) and Unity providing various tools and senses to control gameObjects, scenes, scripts etc

README.md

Docs


MCP for Unity

Unity Open MCP

Unity Open MCP is a comprehensive set of tools to use AI agents with Unity projects.

The MCP server consists of a total of 229 tools:

  • Typed editor/project tools (core package): 92
  • Core + validation tools: 16
  • Asset intelligence + senses + discovery + diagnostics + meta tools: 34
  • Optional extension-pack tools: 87

Key features

  • Safe mutation workflow with automatic validation, checkpoints, deltas, regression checks, and targeted fixes.
  • Asset intelligence tools including reserialize, structured asset read/search, and reference analysis.
  • Live + fallback routing (live Unity bridge, batch mode for supported tools, offline readers where possible).
  • Typed Unity tool surface for scenes, GameObjects, components, packages, build settings, profiler controls, and project settings.
  • Bundled domain tool groups for Navigation, Input System, ProBuilder, Particle System, Animation, Splines, Lighting, Audio, UI, Constraints & LOD, Terrain, Cinemachine, Timeline, Tilemap, Shader Graph, VFX Graph, and Memory Profiler — embedded in the bridge, compiled in automatically when the matching Unity package is present (or unconditionally for built-in modules like Lighting, Audio, UI, Constraints & LOD, and Terrain; Cinemachine is reflection-gated — its assembly always compiles and detects the supported version at call time), and surfaced per session via tool groups. Shader Graph, VFX Graph, and Memory Profiler auto-activate — their tool groups appear automatically when the matching package is installed, no manual opt-in.
  • Unity Hub Pro wizard for guided setup and maintainer workflows.

For the full catalog and contracts, see docs/api/mcp-tools.md.

Typical Unity MCP issue How Unity Open MCP solves it
AI can mutate project state unsafely Gate-based workflow with validation, checkpoints, deltas, regression checks, and targeted fixes
Weak asset visibility and cross-reference context Asset intelligence tools for structured read/search, reserialize flows, and reference analysis
Tooling breaks when Unity/editor runtime is unavailable Live bridge + batch fallback + offline readers where possible
Generic tools miss Unity-specific workflows Typed tool surface for scenes, GameObjects, components, packages, build settings, profiler, and project settings
Domain workflows require custom setup Domain tools embed in the bridge, compile when the Unity package is present, and surface as per-session tool groups

Quick setup

Requires Unity 2022.3 LTS or newer.

Use any of these options:

  1. Easiest (AI agent): paste this prompt into your AI client (Cursor, Claude, …) and let it install for you:
Install Unity Open MCP in this Unity project by following
https://raw.githubusercontent.com/AlexeyPerov/Unity-Open-MCP/master/docs/setup/agent-setup.md
exactly. Do every agent step yourself; stop and tell me only when a human action is required.
If this monorepo is already open locally, read docs/setup/agent-setup.md from disk instead of fetching.

Full procedure: Agent setup.

  1. If you prefer to edit config yourself: see Manual setup.
  2. If you prefer cloning this repo and working with it directly: see Development setup. Fits contributor workflow.

Guided install via Unity Hub Pro: Wizard setup.

plot

Domain tools (NavMesh, Input System, ProBuilder, lighting, Shader Graph, …) are embedded in the bridge — see Extensions for the catalog and activation steps.

Documentation

  • Agent setup — let an AI agent install MCP + Unity packages.
  • Manual setup — DIY MCP client config and UPM pins.
  • Wizard setup — Unity Hub Pro guided install.
  • Development setup — local checkout and contributor workflows.
  • Architecture — repository boundaries and runtime flow.
  • Dialog policy — startup modal auto-dismiss and UNITY_OPEN_MCP_DIALOG_POLICY.
  • Troubleshooting — bridge start failures, zombie listeners, and connectivity recovery.
  • Skills — agent playbooks (SKILL.md) shipped into a project.
  • API index — contract documentation map.
  • Bridge HTTP API — bridge endpoints and envelopes.
  • MCP resources API — resource URIs and payloads.
  • Code conventions — non-obvious C# decisions (instance IDs, namespace aliasing).
  • Versioning — how the shared server/bridge/verify version and the Hub app version are managed, bumped, and kept in sync; the runtime compatibility check.
  • CI templates — GitHub Actions / GitLab CI templates for health checks, verify scans, and regression gates in standard CI.
  • Contributing — extensions — embedded domain gates, wiring checklist, community packs.

Would like to see other MCP options? See the MCP tools for Unity comparison — a side-by-side feature matrix of Unity Open MCP and the other MCP tools / AI assistants in the space.

Unity Hub Pro

Unity Hub Pro is the desktop companion app for Unity Open MCP. It helps you manage projects, run the AI Setup wizard, and handle maintainer workflows from one UI.
See docs for details.

Contributing

  • Feel free to open issues for bugs, feature requests, and documentation improvements.
  • PRs are welcome. Start with the docs above, then package-level READMEs for local development details.

Helpful resources for contributors or those who would like to work on their own forks:

  • Validation Suite — app for guided manual validation; ships runnable scenario packs.

License: MIT — see LICENSE.

Reviews (0)

No results found