unity-mcp and UnityMCP
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 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.
Supports all three MCP handler types (commands, resources, and prompts) with automatic discovery on both C# and TypeScript sides, enabling bidirectional AI-Unity workflows. The framework uses a scalable plugin architecture where custom handlers implement well-defined interfaces and are automatically registered via reflection, with communication serialized as JSON over TCP/IP between the Unity Editor and Claude Desktop. Includes built-in installer tooling for integrating the TypeScript MCP server with Claude Desktop configuration, plus sample handlers demonstrating code execution capabilities.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work