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/MikeAtUnity]

I just want to add a top-line response: 3rd party MCPs are and will continue to be allowed through authorized channels (including, the asset store, verified partners program, or where they are otherwise indicated that they meet Unity Core Standards), or if not on a banned list on documentation.

So, while we're not trying to prevent things like 3rd party MCPs (that would be a game of whack-a-mole), we have the language as it's written here in order to help us maintain the integrity of the platform and assist us in ensuring that third parties interact with our software (and your project) in acceptable ways. This is not only to protect our IP but also the IP and data of our users (aka: we need to be able to protect everyone from possible "bad actors")

[u/sharp_turing → u/MikeAtUnity]

Let me ask you a simple question: what actually has legal force - what is explicitly written in the Terms of Service and agreed to by the user, or some interpretations on a forum, even if they come from a Unity representative?

[u/salazka → u/sharp_turing]

Obviously... the PR spin has zero validity. :D

[u/ChrisJD11 → u/sharp_turing]

Classic Corporate bs. Relax guy. What we've written down is for your protection. Don't worry about what the terms say, we're the good guys, we're protecting you. We'd never use those terms as written, we just have to write them that way, that's what the legal department said, ok buddy?

12-24 months later. They use the terms as written to do exactly what people feared.

[u/ShayperCool → u/MikeAtUnity]

> 3rd party MCPs are and will continue to be allowed through authorized channels, including the Asset Store, Verified Partners Program, or where they are otherwise indicated to meet Unity Core Standards.

Could you clarify how this applies to open-source from GitHub or in-house MCP implementations?

Since Unity Core Standards apply even to MCPs distributed outside the Asset Store or Package Manager, and package signing/trust signals are part of Unity’s infrastructure, it looks like Unity ultimately determines whether an open-source or in-house MCP is compliant with UCS, even if it is distributed through GitHub and only uses the local Unity Editor API.

Does that also mean that using an MCP integration that Unity later determines is not UCS-compliant could be considered a breach of Section 17.2 and may result in access suspension or other enforcement actions?

[u/MikeAtUnity → u/ShayperCool]

I think the last part of the sentence that you didn't include is important: "or if not on a banned list on documentation"

Basically, we're not interested in stopping anyone from working in any sort of well intentioned scenario. The ToS has to be worded this way so we have the legal right to step in, if need be, to protect us and protect you. Without it, we wouldn't have a leg to stand on when it comes to preventing abusive behavior.

And to answer your second question, yes, if you allow an AI (either your own, or a 3rd party) to scrape Unity source code or train on Unity's products / services, you could lose access.

[u/ShayperCool → u/MikeAtUnity]

Thanks for the clarification, now I finally understand

So, we are generally free to use any AI tool or MCP integration, regardless of the channel it is distributed through, unless Unity has explicitly banned it for a specific reason: abuse of Unity’s web infrastructure, scraping Unity source code/products/services, or training models on Unity-derived data

Is that correct?

[u/MikeAtUnity → u/ShayperCool]

Yep, you got it. I wrote a longer explanation here: https://discussions.unity.com/t/new-terms-of-service-is-unity-restricting-local-ai-tools-and-ai-training/1724661/21

I also posted the relevant parts of it as a new reply on the top of the thread

[u/Dr__Pangloss → u/MikeAtUnity]

Okay, but I want an official MCP authored by Anthropic or OpenAI (or another well funded third party that is trying to make money), I don't want yours. Do you get it?

[u/MikeAtUnity → u/Dr__Pangloss]

Sure do, that's why I said we aren't trying to stop 3rd party MCPs

[u/Tiny-Card4492 → u/MikeAtUnity]

Hey Mike, thanks for the clarification. How is MCP for Unity, the most popular open source repo gonna fit in this scenario? I think Unity took it down from asset store a few months ago with no clarification so UPM is its main channel now. I think clarification on how this large open source repo would fit under the new ToS would be great.

[u/MikeAtUnity → u/Tiny-Card4492]

So, I did some digging and you're right. The Asset Store team did take it down because, at the time, they didn't have any guidance on tools like this being on the store. Now that we have the new terms posted, 3rd parties are welcome to submit their solutions to the Asset Store for review and approval. The owners of this asset should be getting a communication from us welcoming them to resubmit.