Unity Terms update raises concerns over a ban on third-party AI and MCP; Unity denies it

Unity updated its Terms of Service on June 30, 2026, local time. The developer community has raised concerns that the new terms could prevent developers from using third-party AI agents and MCP.
Developers can read Unity’s new Terms of Service as restricting integrations with unofficial MCP servers, including Unity CLI Loop and Unity Skills, as well as third-party AI agents.
On Reddit, Unity’s support account said the new restrictions do not apply to MCP or AI integrations that work only with the local Unity Editor and project files. Unity has not issued an official statement as of publication, and some MCP projects have removed their repositories.
Table of Contents
Unity updates its Terms of Service
Unity updated its Unity Terms of Service on June 30, 2026, local time. In the developer community, section 17.2, “Use Restrictions,” has drawn the most attention.
Developers have focused on the newly added clauses (ff) and (gg). They can read those clauses as banning the use of AI agents, command-line interfaces, MCP, and similar tools that Unity has not approved to control Unity, as well as the development or use of plugins that interface with Unity without Unity’s prior approval.
(ff) Access, invoke, query, instruct or otherwise interact with any Offering (or cause any Offering to be accessed, invoked, queried or instructed) by means of any AI agent, autonomous or semi-autonomous software system, large language model, command line interface, model-context-protocol (MCP) client or server, agentic framework, or any other automated, machine or non-human caller, unless the such access is via Authorized Agentic Access. To clarify, Authorized Agentic Access will not be construed as a waiver of any other obligation or restriction set forth in these Terms.
(gg) Develop, distribute, or use any plugin, extension, add-on, module, or third-party integration that interfaces with, accesses, or integrates into any Offering without Unity’s prior written authorization, including through any Additional Terms, Commercial Terms, Offering Identification, Documentation or Policies.
These changes have fueled concerns that developers may no longer be able to use unofficial MCP servers such as Unity CLI Loop and Unity Skills, or control Unity through third-party AI agents.
Clauses (dd) and (ee) also ban the use of Unity data for machine learning purposes.
Unity denies that it is shutting out third-party AI agents and MCP
In response to these concerns, Unity’s support account replied on Reddit that “Using AI tools to help you build your game is fine.” It said Unity made the Terms of Service update “to clarify ambiguity of language that was drafted before the need to account for developments in AI”
Unity also said that Authorized Agentic Access is required only when an AI agent, LLM, or MCP client connects to Unity’s cloud platform, online servers, Asset Store, or public online APIs. It added that developers may use local Unity Editor MCP or AI integrations. Unity denied concerns that developers would no longer be able to use third-party AI agents or MCP.
These comments, however, came from Unity’s support account on Reddit. The Terms of Service text does not appear to state that local use is allowed, so the concern remains.
Developers have posted similar concerns on Unity’s official forum, but Unity has not issued an official statement as of publication.
My analysis
Game developers have started using AI in recent years, and more developers now connect Unity with coding agents such as Claude Code and Codex through MCP to automate parts of their workflow.
I have used Unity Skills and Codex in personal projects to automate parts of the development process.
These tools allow coding agents to retrieve hierarchy state, including Unity Play mode, as well as console logs. That makes them useful for feature development and debugging.
Against that backdrop, Unity updated its Terms of Service in a way that developers can read as banning third-party coding agents and MCP servers in Unity. The developer community has responded with confusion.
In 2024, Unity announced the Runtime Fee, which would have charged developers additional fees based on the number of installs of applications built with Unity. Unity later withdrew the policy after criticism.
That episode damaged Unity’s trust with the developer community, and this Terms of Service update may weaken that trust further.
Unity provides an official MCP through Unity AI, which costs $10 per month.
I had already lost trust in Unity after the Runtime Fee controversy but had little choice except to continue using Unity after weighing the overall situation. When I learned about this Terms of Service update, I wondered whether Unity intended to ban third-party AI-related tools so it could generate revenue through Unity AI.
According to Unity’s Reddit comments, local AI use is fine. Developers now need an official statement from Unity.
Verification details and sources
Last verification date
Reference links
Share this article
Follow us for updates
Adding us to your preferred sources on Google makes it easier to find our articles on Google. Also, be sure to follow us on X and our RSS feed.
Next articles
- X rolls out X Money to paid users in the U.S., with Grok integration and revenue payouts
- GitHub removes manual model selection from Copilot Free and Student plans, leaving Auto as the sole option
- GitHub Copilot is moving to credit-based billing with a full breakdown of what changes in June
- GitHub Copilot pauses new sign-ups: why you can’t register and what alternatives exist
- GitHub temporarily suspends new free trials for Copilot Pro as it steps up measures against increasing abuse
-1.png&w=1080&q=75)
I've been using JavaScript more than my native language since birth. I am nowhere and everywhere on the internet.
I build web apps and browser extensions in TypeScript as a web frontend programmer. I released Shadowban Scanner, a tool that detects shadowbans on X, and Restore Link Card, a tool that brings back link cards. Media outlets in Japan and abroad covered both tools. For iGEM 2023, I built the Wiki for Team Japan-United and helped the team win the Grand Prize. On my blog, I cover news about X and social media, test and troubleshoot bugs, and share frontend development insights.










![スマートフォンのホーム画面の[Social]フォルダーを表示した写真。フォルダー内にはFacebook、Instagram、Threads、X、LinkedIn、TikTok、YouTubeのアイコンが配置されている](/_next/image/?url=%2Fapi%2Fmedia%2Ffile%2Ffacebook-instagram-threads-x-twitter-linkedin-tiktok-youtube-mobile-app-unsplash.jpg&w=3840&q=75)

