Skip to content

Working with clients? Stay ahead of what they ask for.

CommunityDev Tools

MCP Unity Editor

by CoderGamester

Community-built Unity Editor MCP bridge. Combines a Unity package (runs inside the editor) with a Node.js MCP server (translates between MCP clients and the editor) to give agents access to scene, GameObject, and component operations.

★ 1,626·7 listed tools·Released MAR 2025·MIT
See README for two-part install: Unity package + Node.js bridge
Share:

“MCP Unity Editor is the community-built bridge between AI coding agents and the Unity game engine. The architecture is two parts: a Unity package that runs inside the editor exposing scene and component operations, and a Node.js MCP server that translates between MCP clients and the Unity package over a socket. The combination lets agents like Cursor, Windsurf, Claude Code, Copilot, and Google Antigravity execute editor operations: select GameObjects, update components, run tests, install packages, send console logs. The standout feature is the IDE integration that automatically adds Unity's `Library/PackedCache` to the workspace, giving the agent better autocomplete and type information for Unity packages. The community-maintained nature is the biggest caveat: this is a single-developer project at the time of review, with active development but no formal Unity Technologies endorsement. For Unity-focused teams using AI agents, this is the best available bridge; for teams considering Unity MCP integration as a strategic dependency, scope expectations against the maintainer's bus factor.”

Reviewed by M. Nouriel · APR 2026

INSTALL THIS SERVER

Access optionsAnonymous. Operates on the local Unity Editor instance via socket bridge.
{ "mcpServers": { "mcp-unity": { "command": "node", "args": [ "/path/to/mcp-unity/Server~/build/index.js" ], "env": { "UNITY_PORT": "8090" } } } }
PrereqTwo-part install. (1) In Unity: Install the MCP Unity package via Package Manager (Add package from git URL: https://github.com/CoderGamester/mcp-unity.git). (2) On host: Clone the repo, run `npm install && npm run build` in the Server~ directory. Update the path in args to your local clone. Path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS).
{ "mcpServers": { "mcp-unity": { "command": "node", "args": [ "/path/to/mcp-unity/Server~/build/index.js" ], "env": { "UNITY_PORT": "8090" } } } }
{ "mcpServers": { "mcp-unity": { "command": "node", "args": [ "/path/to/mcp-unity/Server~/build/index.js" ], "env": { "UNITY_PORT": "8090" } } } }
{ "mcpServers": { "mcp-unity": { "command": "node", "args": [ "/path/to/mcp-unity/Server~/build/index.js" ], "env": { "UNITY_PORT": "8090" } } } }
{ "mcpServers": { "mcp-unity": { "command": "node", "args": [ "/path/to/mcp-unity/Server~/build/index.js" ], "env": { "UNITY_PORT": "8090" } } } }

7 SELECTED TOOLS

execute_menu_item
Execute Unity menu items (functions tagged with the MenuItem attribute)
Admin
select_gameobject
Select game objects in the Unity hierarchy by path or instance ID
Write
update_gameobject
Update a GameObject's core properties; creates the GameObject if it does not exist
Write
update_component
Update component fields on a GameObject; adds the component if missing
Write
add_package
Install new packages in the Unity Package Manager
Admin
run_tests
Run tests using the Unity Test Runner
Read

OUR ASSESSMENT

Community-built Unity Editor MCP bridge. Combines a Unity package (runs inside the editor) with a Node.js MCP server (translates between MCP clients and the editor) to give agents access to scene, GameObject, and component operations. Supports execute_menu_item, select_gameobject, update_gameobject, update_component, add_package, run_tests, send_console_log. Auto-adds Unity Library/PackedCache to VS Code-like IDEs for improved autocomplete. MIT-licensed.

Strengths
  • Two-part architecture (Unity package + Node.js MCP server) provides clean separation between editor-side execution and MCP protocol handling.
  • IDE integration adds Unity `Library/PackedCache` to VS Code-like workspaces for better Unity package autocomplete and type information.
  • Tool coverage spans GameObject manipulation, component updates, package installation, and Unity Test Runner integration.
  • Multi-language README (English, Chinese, Japanese) signals international community adoption.
Weaknesses
  • Single-developer maintained; bus factor risk is real for teams making this a strategic dependency.
  • Community project; Unity Technologies endorsement is absent, and integration with future Unity versions depends on the maintainer's release cadence.
  • Two-part install (Unity package + Node.js) adds friction compared to single-binary MCP servers.
Security Notes

The Unity package runs inside the Unity Editor with the same permissions as the editor process. Operations like `execute_menu_item` execute Unity menu commands directly, which means destructive operations (delete scene, clear console) are within scope. The Node.js server bridges via a local socket; ensure firewall rules restrict the port to localhost only. Project-level git hygiene matters: the agent can modify scenes, components, and project settings, so commit cadence and human review checkpoints are the safety net.

Best For

Unity developers using AI coding agents (Cursor, Windsurf, Claude Code, Copilot, Google Antigravity) who want the agent to drive editor operations alongside C# code.

TECHNICAL DETAILS

Language
typescript
Transport
stdio
Clients
Claude DesktopClaude CodeCursorVS CodeWindsurf
License
MIT
GitHub
Last Release
1.3.0APR 26, 2026
First Released
MAR 8, 2025

RECORDED ADOPTION METRICS

Saved directory snapshots. Record last checked APR 28, 2026. The review date above does not refresh these figures.

// GitHub Stars
1,626

// Recorded note1.6k stars from the Unity developer community signal real workflow adoption. The community-maintained status places long-term continuity on a single maintainer.

// Popularity Rank
#13
Recorded directory rank · #5 in Dev Tools

// Recorded noteTop-ranked Unity MCP bridge in the directory. The IDE integration with Library/PackedCache is the architectural differentiator that other Unity MCPs miss.

SOURCES & RECORDED CHECKS

These are the directory listings and check details held in this record. Client compatibility, directory listings and installation testing are separate signals. Recorded client names describe the scope of a check; they do not establish a security assessment or a recurring test schedule.

01
Discovered
Source not recorded
First indexed APR 28, 2026
02
Directory listings
5 directories
PulseMCP, Official MCP Registry, Awesome MCP Servers, Smithery, MCPMarket
03
Recorded client testing
Cursor, Windsurf, Claude Code, Codex CLI, GitHub Copilot, Google Antigravity
Check current setup against the provider documentation
04
Record last checked
APR 28, 2026
Record date; functional retest scope may differ
// How other directories see it

The same server, 5 different lenses. We reconcile these signals into our editorial score, which is why our number sometimes diverges from a directory-aggregate star count.

SourceTheir ratingTheir star countTheir downloadsLast synced
AutomationSwitch This page4editorial1,626—APR 28, 2026
PulseMCP— unratedunavailableunavailableAPR 28, 2026
Official MCP Registry— unratedunavailableunavailableAPR 28, 2026
Awesome MCP Servers— unratedunavailableunavailableAPR 28, 2026
Smithery— unratedunavailableunavailableAPR 28, 2026
MCPMarket— unratedunavailableunavailableAPR 28, 2026

// Counts are directory-reported; we don't adjust them. Discrepancies usually come from different snapshot times or star-caching.

// Get in touch

DISCUSS YOUR
MCP REQUIREMENTS.

Evaluating a server, scoping an internal deployment, or working out whether MCP is the right fit at all. Start the conversation and we will point you at the right piece of the ecosystem.

Discuss Your MCP Requirements →