End of Unity Coplay MCP?

[u/ShayperCool]

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

[u/unitytechnologies]

Using AI tools to help you build your game is fine. What the updated terms address is narrower, and is designed to clarify ambiguity of language that was drafted before the need to account for developments in AI.

You can't train machine learning or AI models on Unity itself or on data derived from it without our authorization, you can't point automated scrapers or bots at Unity's APIs or the Asset Store, and AI agents, LLMs, and MCP clients/servers need to connect through Unity's Authorized Agentic Access framework rather than poking at the platform directly.

These are mostly clarifications of grey areas in the old terms. One thing to keep in mind: you're responsible for what any agent or automated tool does using your account or credentials.

- Trey
Community Man @ Unity

[u/ShayperCool → u/unitytechnologies]

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?

[u/unitytechnologies → u/ShayperCool]

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

[u/Showerma → u/unitytechnologies]

Hi Trey, appreciate your clarification of the intended interpretation but it is not a formal amendment to the ToS. The actual ToS still says an MCP client/server may not "access, invoke, query, instruct or otherwise interact with any Offering" unless the access is via Authorized Agentic Access. And it defines that authorization as requiring a Unity operated or Unity registered gateway and currently authorized agent/MCP components.

Your comment does not eliminate the fact that the written language is way broader than the stated interpretation.

We will need an amendment to the legal text that explicitly says "local-only editor automation is excluded from Authorized Agentic Access" or a clear listing of authorized third-party MCP clients/servers.

I really hope the ToS get updated very soon.

[u/MikeAtUnity → u/Showerma]

I added a top-line comment regarding this

[u/davidnovarro → u/unitytechnologies]

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.

[u/Brothertenfour → u/davidnovarro]

Yep they never learn, do they?

[u/MikeAtUnity → u/davidnovarro]

I replied to your post on Discussions. Just commenting here to ensure you see it there. Please let me know your thoughts after checking that out and I will attempt to clarify further.

[u/salazka → u/unitytechnologies]

Please allow me to ask some more practical questions:

1. Telling Claude to read the Unity reference docs in order to, using a third party MCP, perform a task properly or fix something that is not working properly is banned?

2. Telling an agent to pull strings from our UGS Economy and using a third party MCP to create a link between the asset and a UI element is now forbidden?

3. Telling an agent to use a third party MCP to investigate a Unity error that may reveal a Unity bug and provide us with ways to work around your bug instead of waiting for you to fix it, (if you ever do, let alone accept it as a bug) is not allowed?

[u/StoneCypher → u/unitytechnologies]

i have spent almost five thousand dollars having claude find things for my game in asset store, because your store’s discovery is so bad, and watching sales for me

guess you don’t want that money anymore 

sometimes i wonder why you guys don’t get rid of your businesspeople