MCP Unity Editor
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.
“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.”
INSTALL THIS SERVER
{
"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"
}
}
}
}
{
"mcpServers": {
"mcp-unity": {
"command": "node",
"args": [
"/path/to/mcp-unity/Server~/build/index.js"
],
"env": {
"UNITY_PORT": "8090"
}
}
}
}
7 TOOLS AVAILABLE
OUR ASSESSMENT
- 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.
- 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.
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.
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
ADOPTION METRICS
// Reading this1.6k stars from the Unity developer community signal real workflow adoption. The community-maintained status places long-term continuity on a single maintainer.
// Reading thisTop-ranked Unity MCP bridge in the directory. The IDE integration with Library/PackedCache is the architectural differentiator that other Unity MCPs miss.
SOURCES & VERIFICATION
We don't take any single directory's word for it. Before scoring, we cross-reference 5 public MCP sources, install the server ourselves against the clients we cover, and record when we last re-verified.
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.
| Source | Their rating | Their star count | Their downloads | Last synced |
|---|---|---|---|---|
| AutomationSwitch This page | 4editorial | 1,626 | — | APR 28, 2026 |
| PulseMCP | — unrated | unavailable | unavailable | APR 28, 2026 |
| Official MCP Registry | — unrated | unavailable | unavailable | APR 28, 2026 |
| Awesome MCP Servers | — unrated | unavailable | unavailable | APR 28, 2026 |
| Smithery | — unrated | unavailable | unavailable | APR 28, 2026 |
| MCPMarket | — unrated | unavailable | unavailable | APR 28, 2026 |
// Counts are directory-reported; we don't adjust them. Discrepancies usually come from different snapshot times or star-caching.
OTHER DEV TOOLS MCP SERVERS
GitHub
Codebase awareness layer for accessing repositories, pull requests, issues, code search, and GitHub Actions. Fine-grained PAT scopes keep access minimal.
OpenSpec
The leading spec-driven development workflow for AI agents. Implements the /opsx:propose → /opsx:apply → /opsx:archive cycle that scaffolds proposals, specs, design docs, and task checklists, then applies them and archives once shipped.
Chrome DevTools for Agents
Vendor-official Chrome DevTools MCP server from the Chrome DevTools team at Google. Lets agents control and inspect a live Chrome browser for automation, debugging, and performance analysis.
Terraform MCP Server
Vendor-official Terraform MCP server from HashiCorp. Integrates with the public Terraform Registry (providers, modules, policies) and HCP Terraform / Terraform Enterprise (workspace management, organisation listing, run management, private registry access).
Browserbase MCP Server
Vendor-built Browserbase MCP server combining cloud browser automation (Browserbase) with natural-language-to-action mapping (Stagehand). 6 tools: start, end, navigate, act, observe, extract. Available as a hosted endpoint at https://mcp.browserbase.com/mcp (LLM costs covered for Gemini) or self-hostable via @browserbasehq/mcp.
AWS Infrastructure as Code MCP Server
AWS Labs server for Infrastructure as Code lifecycle. Validates CloudFormation templates with cfn-lint, checks compliance via cfn-guard against AWS Guard Rules and Control Tower controls, troubleshoots failed deployments with pattern-matched analysis, searches CloudFormation and CDK documentation.
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.