unity-mcp and unity-mcp-plugin

The Unity MCP Plugin (UPM) is an ecosystem sibling that acts as a client library for AI-assisted game development, designed to interact with a Unity MCP server like the one provided by wondeks/unity-mcp to control Unity Editor actions.

unity-mcp
50
Established
unity-mcp-plugin
45
Emerging
Maintenance 13/25
Adoption 6/25
Maturity 16/25
Community 15/25
Maintenance 13/25
Adoption 8/25
Maturity 11/25
Community 13/25
Stars: 17
Forks: 5
Downloads:
Commits (30d): 0
Language: C#
License: MIT
Stars: 50
Forks: 7
Downloads:
Commits (30d): 0
Language: C#
License:
No Package No Dependents
No Package No Dependents

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.

About unity-mcp-plugin

AnkleBreaker-Studio/unity-mcp-plugin

Unity MCP Plugin (UPM) — Editor bridge for AI-assisted game development. Enables Claude, Cursor & MCP-compatible AI to control Unity Editor with 268 tools: scenes, GameObjects, components, builds, profiling, Shader Graph, Amplify Shader Editor, terrain, physics, NavMesh & more. Free & open source.

Implements a stateful HTTP bridge on `localhost:7890` that persists across Play Mode domain reloads via SessionState, enabling real-time bidirectional control between MCP-compatible AI and the Unity Editor. Supports multi-instance editor discovery with automatic port affinity tracking and heartbeat-based session management to distinguish active from crashed editors. Conditionally exposes 268 tools across shader editors (Shader Graph, Amplify), multiplayer frameworks (MPPM), and profiling systems (Memory Profiler, Frame Debugger) based on installed packages.

Scores updated daily from GitHub, PyPI, and npm data. How scores work