Unity-MCP and unity-mcp-server
These are competitors offering overlapping MCP server implementations for Unity integration—both provide LLM-accessible interfaces to the Unity Editor, though the second includes significantly more tools (268 vs. unspecified) and broader scope (Hub access, profiling, shaders).
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-server
AnkleBreaker-Studio/unity-mcp-server
Unity MCP Server — 268 tools for AI-assisted game development. Connect Claude, Cursor, or any MCP client to Unity Editor & Unity Hub. Scene management, GameObjects, components, builds, profiling, Shader Graph, Amplify, terrain, physics, NavMesh, animation, MPPM multiplayer & more. Free & open source by AnkleBreaker Studio.
Implements a two-tier tool architecture (core + advanced proxy) to avoid overwhelming MCP clients, while communicating with Unity Editor via a companion HTTP plugin and Unity Hub through CLI commands. Supports multi-instance editor discovery with automatic port reconnection, enabling seamless workflows across multiple concurrent Unity projects or ParrelSync clones.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work