mcp-unity and unity-mcp-plugin
These are **competitors** offering overlapping MCP server implementations for Unity Editor integration—both enable AI assistants to control Unity through the Model Context Protocol, but they differ in scope (the former appears more focused while the latter claims 268 tools) and maturity (indicated by their star count disparity).
About mcp-unity
CoderGamester/mcp-unity
Model Context Protocol (MCP) plugin to connect with Unity Editor — designed for Cursor, Claude Code, Codex, Windsurf and other IDEs
Provides AI agents with 25+ tools for scene manipulation, asset management, and testing—including GameObject modification, prefab creation, scene loading, and script recompilation—via a Node.js MCP server that communicates with Unity Editor through stdio transport. Automatically surfaces Unity's PackedCache to IDE workspaces for improved code intelligence on engine dependencies, bridging the gap between AI coding assistants and real-time game development workflows.
About unity-mcp-plugin
AnkleBreaker-Studio/unity-mcp-plugin
Unity MCP Plugin (UPM) — Editor bridge for AI-assisted game development. Enables Claude, Cursor & MCP-compatible AI to control Unity Editor with 268 tools: scenes, GameObjects, components, builds, profiling, Shader Graph, Amplify Shader Editor, terrain, physics, NavMesh & more. Free & open source.
Implements a stateful HTTP bridge on `localhost:7890` that persists across Play Mode domain reloads via SessionState, enabling real-time bidirectional control between MCP-compatible AI and the Unity Editor. Supports multi-instance editor discovery with automatic port affinity tracking and heartbeat-based session management to distinguish active from crashed editors. Conditionally exposes 268 tools across shader editors (Shader Graph, Amplify), multiplayer frameworks (MPPM), and profiling systems (Memory Profiler, Frame Debugger) based on installed packages.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work