Unity-MCP and unity-mcp
These are complementary tools that serve different roles in the same workflow: IvanMurzak's implementation provides a full-featured MCP server with code generation and debugging capabilities, while wondeks' lighter implementation focuses on direct Editor action execution, allowing them to be used together or chosen based on feature complexity needs.
About Unity-MCP
IvanMurzak/Unity-MCP
AI-powered bridge connecting LLMs and advanced AI agents to the Unity Editor via the Model Context Protocol (MCP). Chat with AI to generate code, debug errors, and automate game development tasks directly within your project.
Implements MCP server architecture running both in the Unity Editor and compiled runtime, supporting stdio-based local execution and HTTP-based remote deployment without vendor lock-in. Generates dynamic "skills" metadata reflecting project state (Unity version, OS, installed plugins) to enhance LLM context, and provides extensible MCP Tools for editor automation alongside in-game runtime capabilities for NPC behavior and live debugging. Compatible across multiple AI clients (Claude, Cursor, GitHub Copilot, VS Code, Rider) and deployable via npm CLI, Docker, or direct UPM package integration.
About unity-mcp
wondeks/unity-mcp
A Unity MCP server that allows MCP clients like Claude Desktop or Cursor to perform Unity Editor actions.
Exposes a comprehensive set of Unity Editor operations—asset management, scene modifications, and game mechanics testing—through MCP's standard protocol, enabling AI clients to autonomously perform complex editor tasks. Acts as a bridge between MCP-compatible AI tools and Unity's Editor scripting API, communicating via the MCP protocol to translate high-level client requests into native Editor commands.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work