Unity-MCP and mcp-unity
These two tools are competitors, as both aim to provide a Model Context Protocol (MCP) plugin or bridge to connect large language models (LLMs) and AI agents with the Unity Editor, differing primarily in their specific target IDEs or stated AI integration goals.
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 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