Field-by-field comparison

Compare the evidence before choosing an MCP.

Each signal stays separate, missing facts remain visible, and the column order follows your selection.

MCPs in this comparison

MCP Unity Editor (Game Engine)Windows-MCP

Uncheck an MCP to remove it. Comparing two or three keeps each signal in its own row.

Comparable alternatives

Azure MCP ServerMCP100 RecommendedChrome DevTools MCPMCP100 RecommendedContext7 MCPMCP100 RecommendedGrafana Cloud MCPMCP100 RecommendedGoogle MCP Toolbox for DatabasesMCP100 RecommendedGhidra MCP ServerMCP100 Recommended

Shown only when capability or industry context overlaps.

Side-by-side MCP evidence comparison
Evidence field	MCP Unity Editor (Game Engine)MCP100 Recommended	Windows-MCPMCP100 Recommended
Task fit
Best for	Creating and editing Unity project assets, scenes, scripts, and editor state through supported AI coding clients	Using an AI client to inspect and operate Windows applications when no safer application API exists
Not ideal for	Older Unity projects or game-development tasks that do not require direct Editor control	Deterministic automation that can be implemented through a documented API, CLI, or test framework
Avoid when	You cannot review or revert agent-made project and scene changes	The desktop session contains sensitive applications, credentials, messages, or files outside the task
Provenance
Provenance details	Community implementation github:codergamester · Publisher source ↗	Community implementation io.github.CursorTouch · Publisher source ↗
Maintenance
Maintenance details	Repo: Sep 3, 2026 Package: Not documented	Repo: Sep 23, 2026 Package: Not documented
Popularity evidence
GitHub stars	1,910 GitHub stars · checked 2026-09-24T04:14:16.259000Z	7,140 GitHub stars · checked 2026-09-24T04:14:39.564000Z
Client coverage
Client coverage details	Claude Code✓ Local stdio Claude Desktop✓ Local stdio Codex✓ Local stdio VS Code✓ Local stdio Cursor✓ Local stdio OpenCode✓ Local stdio	Claude Code✓ Local stdio Claude Desktop✓ Local stdio Codex✓ Local stdio VS Code✓ Local stdio Cursor✓ Local stdio OpenCode✓ Local stdio
Client coverage note	Local stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server.
Access and data
Authentication	The WebSocket server defaults to localhost:8090. Remote instructions can bind it to 0.0.0.0; no bearer-token or OAuth mechanism is documented.	Stdio has no network listener. Non-loopback HTTP requires an auth key or OAuth unless insecure access is explicitly allowed; IP allowlists, TLS, CORS, and host validation are documented.
Cost	The publisher describes the MIT-licensed project as free and open source. Unity, Node.js, hosting, client, and model costs are separate.	The MIT-licensed project lists no MCP fee. Windows, Python, hosting, client, and model costs are separate.
Permissions	Executes Unity menus and controls scenes, GameObjects, components, materials, assets, packages, tests, logs, play mode, and project-state resources through a WebSocket bridge.	Runs with the invoking user's full Windows permissions, including PowerShell, files, registry, processes, UI input, screenshots, and web scraping; many actions are irreversible.
Data handling	Unity scenes, assets, project state, and console logs are read or modified locally and returned through MCP. Remote transmission, retention, and telemetry are not documented.	Processing is local. Telemetry excludes screenshots, state captures, arguments, and outputs but includes status, duration, tool and client information, anonymized sessions, and possibly paths in error messages.
Limitations
Tradeoffs	Direct Editor integration speeds iteration, but setup spans a Unity package and Node server and automated changes may leave the project in an invalid state.	General computer-use reaches many applications, but visual automation is brittle and broad input control can produce high-impact unintended actions.
Risk context	Can make destructive project changes, install packages, execute menu items, and control play mode. Keep the bridge loopback-only and supervise all writes and deletions in a version-controlled project.	It is not sandboxed and can delete files, alter registry or system settings, type into applications, and execute PowerShell. Use a VM or low-privilege account, backups, supervision, loopback binding, and disabled high-risk tools.
Evidence date
Editorial review	2026-08-11	2026-08-11
Candidate evidence	2026-09-24T04:25:05.554391Z	2026-09-24T04:25:05.554391Z

Popularity, maintenance, fit, permissions, and client support are independent evidence fields.

Read the evidence method →