Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for Unity teams that want AI-assisted scene building and editor automation from Claude, Codex, VS Code, local LLMs, or other MCP clients without inventing a custom bridge first.
Where this stands now
CoplayDev/unity-mcp ranks #41 of 2770 tracked Radar items by composite score (8.7 against a section median of 4.9). The section currently carries 1659 Bronze, 645 Gold, 466 Silver. RepoRadar has retained observations for this record since 2026-07-01 (94 days in the current window). Signal extremes versus the section: momentum at the 91th percentile; novelty at the 83th percentile.
Who should use it
Who should skip it
Skip CoplayDev/unity-mcp if the source link, documentation, or setup requirements do not align with your current workflow or stack.
About this signal
CoplayDev/unity-mcp is tracked by RepoRadar as an MCP server in the Radar section. First seen 2026-07-01; the source record was last checked on 2026-07-01. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. Across RepoRadar's eight signals, CoplayDev/unity-mcp is strongest on workflow potential (10.0) and practical usefulness (9.0) and weakest on setup ease (6.4) — a profile worth weighing against your own priorities. This page summarizes the public evidence on the linked source page and states where additional review is still needed.
How this item is evaluated
The CoplayDev/unity-mcp record combines a 8.7/10 composite score with separate popularity (1.0), risk (conditional), and setup (moderate) signals. See the scoring methodology for the current weights and evidence definitions.
Questions worth asking before you adopt this
Putting this into practice? Read How to vet an AI agent or MCP server before you wire it in for the checklist behind this score.
Risk explanation
It can create scenes, edit scripts, manage assets, run tests, and build inside a real Unity project, so first-run use should stay in a disposable branch or sandbox project; If you expose it to multiple MCP clients or a remote-hosted server, scope credentials and project access narrowly before sharing a live editor.