CoderGamester/mcp-unity
Model Context Protocol (MCP) plugin to connect with Unity Editor — designed for Cursor, Claude Code, Codex, Windsurf and other IDEs
What it solves
MCP Unity provides a bridge between the Unity Editor and AI coding assistants. It allows AI agents to directly interact with a Unity project, enabling them to manipulate the scene, manage assets, and control the Editor's state without the developer needing to manually copy-paste code or descriptions of the scene hierarchy.
How it works
The project implements the Model Context Protocol (MCP), using a Node.js server that communicates with the Unity Editor. It provides a set of tools and resources that AI assistants (such as Cursor, Windsurf, and Claude Code) can call to execute operations within Unity. It also integrates with IDEs by adding the Library/PackedCache folder to the workspace to improve code intelligence for Unity packages.
Who it’s for
Unity developers who use AI-powered IDEs or agents to accelerate their game development workflow by allowing the AI to directly manage GameObjects, components, and scene settings.
Highlights
- Scene Manipulation: Tools to create, select, move, rotate, scale, and delete GameObjects, as well as reparenting and duplicating objects.
- Asset & Package Management: Ability to install packages via the Unity Package Manager and create/assign materials and prefabs.
- Editor Control: Tools to execute Unity menu items, run tests via the Unity Test Runner, and retrieve console logs.
- Play Mode Control: Ability to start, pause, stop, or step through Unity's play mode.
- Batch Execution: Support for executing multiple operations in a single request to reduce round-trips and allow atomic operations.
- Contextual Resources: Provides AI agents with access to the scene hierarchy, menu items, and asset database via MCP resources.
Related
- Project
- Project
- Project
- Project
- Project