unity-mcp and mcp-unity
These are **competitors** — both provide MCP servers that enable LLM-based code editors to interact with Unity Editor through the Model Context Protocol, offering overlapping functionality for asset management and editor control with no technical dependency between them.
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 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.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work