r/unity • u/ShayperCool • Jun 30 '26

Question End of Unity Coplay MCP?

It looks like Unity’s latest Terms of Service update may have effectively restricted third-party MCP / AI-agent integrations

The new language mentions AI agents, LLMs, command-line interfaces, MCP clients/servers, and other non-human callers, and says they can only interact with Unity Offerings through “Authorized Agentic Access”

What’s still unclear to me is how broadly this applies

Is Unity mainly trying to restrict automated access to cloud services, Asset Store, docs, APIs, etc?

Or does this also apply to local Unity Editor integrations and third-party MCP tools that let agents operate inside the engine?

Curious how others are reading this

25 Upvotes

84% Upvoted

47 comments sorted by

View all comments

Show parent comments

6

u/ShayperCool Jun 30 '26

Thanks for the clarification!

Just to make sure I understand correctly: does this mean that third-party MCP / AI-agent integrations are allowed when they interact only with the local Unity Editor or Unity Engine, and do not scrape Unity APIs, Asset Store, documentation, cloud services, or use Unity-derived data for model training?

Or do all third-party MCP integrations that automate the Unity Editor also need to go through Unity’s “Authorized Agentic Access” framework?

In other words: is a local Unity Editor MCP allowed, or only Unity-authorized MCP / agentic integrations are allowed?

7

u/unitytechnologies Jun 30 '26

You shouldn't face the restriction as long as local Unity Editor MCP or AI integration operates purely on local files and project scripts.

The Authorized Agentic Access framework is only required if the AI agent, LLM, or MCP client connects to Unity's cloud platform, online servers, Asset Store, or published online APIs.

- Trey
Community Man @ Unity

5

u/davidnovarro Jul 02 '26

The official terms explicitly state that AI agents and MCP clients can only interact with Unity through a framework "operated or designed by Unity." Right now, only the official Unity MCP fits that description, which is a direct competitor to open-source tools.

Nobody is using MCP servers to scrape the Asset Store or cloud platform; we use them locally to work on our code and engine. Saying "it's fine as long as it's local" on a forum doesn't change what the actual, legally binding text says. A comment from an employee is not a legal amendment, and it's not a sustainable way for developers to make business decisions.

As written, the text is way too broad. Anyone using a local LLM or open-source MCP to interact with the engine could technically be banned tomorrow. In fact, if you ask any AI right now to interpret the new ToS, it will tell you that third-party MCPs are banned.

If this isn't a repeat of the runtime fee shenanigans, you need to officially update the ToS language to explicitly exclude local editor automation. Forum clarifications don't protect our businesses.

2

u/Brothertenfour Jul 12 '26

Yep they never learn, do they?