unity-mcp-server
Provides an MCP server that lets AI assistants control Unity Editor and Unity Hub via a bridge (MCP server -> unity-mcp-plugin in the editor via an HTTP bridge, plus Unity Hub CLI). Exposes hundreds of tools for scene/gameobject/component/asset management, builds, profiling/debugging, navigation, animation, multiplayer playmode scenarios, shader graph tooling (and Amplify/UMA when installed), and multi-instance/multi-agent orchestration.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
No auth model is documented for the MCP interface; this increases risk if exposed beyond localhost. Communication to the Unity editor is described as an HTTP bridge, but explicit TLS requirements are not stated. Many operations can modify local project files and run editor/build actions—treat as powerful local automation. Dependency details are limited to @modelcontextprotocol/sdk, so CVE posture cannot be fully assessed from provided data.
⚡ Reliability
Best When
You have a local Unity development environment (Editor + unity-mcp-plugin) and want an MCP-compatible AI assistant to perform editor automation and scene/game workflows.
Avoid When
You need a hosted, multi-tenant SaaS with strong end-user isolation/auditability; or you require a documented, token-based authorization model.
Use Cases
- • AI-assisted creation and modification of Unity scenes and GameObjects
- • Programmatic editing of components/serialized properties and wiring references
- • Running Unity Hub installs/modules and triggering editor-related workflows via CLI
- • Generating and adjusting lighting, terrain, NavMesh, physics queries, and other subsystems
- • Automated profiling/debugging and capturing visual artifacts (scene/game view images)
- • Automating build workflows across multiple target platforms
- • Integrating AI into multiplayer playmode scenario workflows (MPPM)
- • Managing multi-instance Unity editor sessions for parallel work
Not For
- • Production-grade CI/CD without verifying safety/permissions—tools can directly manipulate local editor projects
- • Environments where running arbitrary code in the Unity Editor is not allowed
- • Teams needing strict, documented authn/z boundaries for tool-level actions
Interface
Authentication
The README/config focuses on local process configuration (Node command, env vars, local ports). No user-facing authentication model (API keys/OAuth) is documented for the MCP server.
Pricing
Server/plugin are described as free/open source; costs mainly come from the AI assistant provider (not evaluated here).
Agent Metadata
Known Gotchas
- ⚠ Editor/bridge can be sensitive to port conflicts; selecting the correct Unity instance matters in multi-instance setups
- ⚠ Some features depend on optional Unity packages being installed; missing packages return helpful messages but may break workflows
- ⚠ Large/complex editor operations can involve Unity compile pauses; agents may need to account for editor unresponsiveness
- ⚠ Response size limits are configured (soft/hard limits), so agents should avoid requesting overly large data dumps
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for unity-mcp-server.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-30.