io.github.IvanMurzak/Unity-MCP
MCP100 verdict
Not currently recommended. Promising for supervised Unity Editor workflows when the project is version controlled and agent actions are reviewed inside Unity.
MCP100 Assessment
Editorial verdict
Promising for supervised Unity Editor workflows when the project is version controlled and agent actions are reviewed inside Unity.
Reviewed 2026-08-11 · Next review 2026-09-10
Task Fit
Mapped
Developer workflows
Trust
Status warning
tool_contract; install_supply_chain; advisory_freshness
Maintenance
Activity observed
A dated repository or package update is available; editorial maintenance review is still pending.
Popularity
Signals unavailable
No independently comparable adoption metric is currently stored.
Best for
- Using the publisher-documented Unity MCP integration to inspect and modify scenes, assets, scripts, and Editor state
Not ideal for
- Autonomous game-development decisions or projects that cannot run the documented Unity integration
Avoid if
- The connected model must not see project content or automated Unity changes cannot be tested and reverted
Trade-offs
- Direct Unity integration speeds iteration, but installation spans the Editor and MCP client and generated changes can leave project state invalid.
Evidence scope
Evidence
Popularity
3.9k shared-repository stars · not MCP-specific
No MCP-specific package metric is stored
Stars observed 2026-08-14T18:46:26.000Z · Downloads observation date unavailable
Shared or parent metric is non-comparable.
Exact OCI install artifact is documented; package download evidence is not applicable.
Maintenance
Publisher activity observed 2026-08-10T17:59:31Z
Current source snapshot
Trust review
Source relationship: Community implementation
Reviewed 2026-08-11 · Next review 2026-09-10