unity-mcp and UnityMCP
One project, CoplayDev/unity-mcp, is a robust implementation of the Model Context Protocol acting as a bridge for AI assistants to interact with the Unity Editor, while the other, isuzu-shiranui/UnityMCP, is a smaller, likely experimental or personal integration that also enables AI interaction via MCP but focuses on a TypeScript server and C# Unity plugin with extensible commands.
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.
This project lets you control your Unity Editor using plain language commands through AI assistants like Claude or Cursor. You can tell your AI to manage game assets, manipulate scenes, modify scripts, and automate various tasks within Unity. It's designed for game developers, 3D artists, and Unity creators who want to streamline their workflow with AI assistance.
About UnityMCP
isuzu-shiranui/UnityMCP
Unity Editor integration with Model Context Protocol (MCP) enabling AI assistants like Claude to interact with Unity projects. Features a TypeScript MCP server and C# Unity plugin with extensible command handler architecture, TCP/IP communication, and dynamic plugin discovery.
This framework allows game developers using Unity to integrate AI assistants like Claude directly into their Unity Editor workflow. It enables AI to understand and manipulate Unity projects by translating AI commands into actions within the editor. Developers can feed instructions or queries to the AI and receive direct modifications or information about their Unity scenes, assets, and game logic.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work