unity-mcp and unity-editor-mcp
These are competitors offering overlapping functionality—both enable LLM-to-Unity Editor integration via MCP—though the first has significantly more maturity and adoption (6,920 vs 19 stars), making it the more established choice for most use cases.
About unity-mcp
CoplayDev/unity-mcp
Unity MCP acts as a bridge, allowing AI assistants (like Claude, Cursor) to interact directly with your Unity Editor via a local MCP (Model Context Protocol) Client. Give your LLM tools to manage assets, control scenes, edit scripts, and automate tasks within Unity.
Implements a comprehensive Python-based MCP server using HTTP transport that operates locally within the Unity Editor, exposing 40+ tools across physics, animation, graphics, builds, and scene management alongside introspection resources like `unity_reflect` for live API inspection. The architecture supports multi-instance routing, async long-running operations with polling, batch execution for performance optimization, and integrates with popular LLM clients (Claude, Cursor, VS Code Copilot, Windsurf) through configurable connection protocols. Available as a Git-based package in the Unity Package Manager, Asset Store, and OpenUPM with Python 3.10+ and the `uv` package manager as runtime dependencies.
About unity-editor-mcp
ozankasikci/unity-editor-mcp
An MCP server and client for LLMs to interact with Unity Projects
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work