# MCP Moves to the Linux Foundation: An Open, Neutral Standard
Table of Contents
More and more AI programs don’t just answer questions: they read files, query databases, and use external tools on behalf of the people using them, the way an AI assistant that lives in the terminal now does too. For all of this to work, there needs to be a common way to connect those programs to the systems they have to talk to. One of the most widely used standards for that is called MCP. In early December 2025 a change was announced: MCP is no longer governed by a single company but has moved under an independent foundation. The news mainly concerns people who build software on top of the standard, but it’s worth understanding from the outside too, because it touches a simple question: who do you trust when you pick a technology to build your work on.
What MCP is
Let’s start with the terms. MCP stands for Model Context Protocol. A protocol is a set of shared rules that lets two programs talk to each other, a bit like a common language. MCP defines a standard way to connect AI applications - say an assistant like ChatGPT or Claude - to external systems: documents, databases, work tools, online services.
The problem it addresses is concrete. Without a shared standard, every time you want a model to talk to a new tool, you have to write a custom connection. With many models on one side and many tools on the other, the number of integrations to build and maintain grows fast. A common protocol cuts that work down: whoever builds a tool exposes it once following MCP’s rules, and any application that “speaks” MCP can use it without a dedicated integration. The idea is like a standard socket such as USB: one type of connector instead of many incompatible cables.
MCP is about a year old and has spread quickly. According to figures reported in the announcement, the developer packages (the libraries used to integrate the protocol) exceed 97 million downloads a month, and there are more than 10,000 active public MCP servers - that is, tools ready to plug in. Support is present in several widely used products, including ChatGPT, Claude, Cursor, Gemini, Microsoft Copilot, and Visual Studio Code. These are numbers stated by the parties promoting the standard, so best treated as orders of magnitude rather than exact measures; they still signal broad adoption.
What happened
The change concerns governance, meaning who decides how the standard evolves. Until now MCP was led by Anthropic, the company that created it. With the December announcement, the protocol was donated to the Agentic AI Foundation (AAIF), a new effort hosted by the Linux Foundation.
The Linux Foundation is a non-profit organization that acts as a steward for many open, widely used technology projects; among them are the Linux kernel, Kubernetes, and PyTorch. “Hosting” a project means putting a neutral structure around it, with shared rules, that doesn’t belong to any single vendor.
The Agentic AI Foundation is set up to help technologies around agents grow in an open, collaborative way - agents being AI programs that, beyond answering, take concrete actions using external tools. It’s co-founded by Anthropic, Block, and OpenAI, with support from Google, Microsoft, AWS, Cloudflare, and Bloomberg. It launches with three founding projects: MCP, donated by Anthropic; goose, a project from Block; and AGENTS.md, a convention proposed by OpenAI. The fact that companies that often compete with each other are contributing to the same foundation is, in itself, part of the story, in the same vein as other attempts to give shared rules to how AI agents get instructed, such as Anthropic’s Agent Skills.
Why a neutral foundation matters
This is where the practical point of the announcement sits. When a standard is controlled by a single company, whoever builds on it depends on that company’s choices: its priorities, its business model, its strategy. If those changed one day, the standard could follow. That worry holds back many adoptions, especially for infrastructure meant to last.
Handing the standard to a neutral foundation shifts the center of gravity. Decisions no longer answer to a single owner but to a shared structure in which multiple parties have a voice. It’s not an absolute guarantee, but it lowers the risk of the standard being bent to serve just one interest. It’s the same path already taken by projects like Kubernetes and PyTorch, which became common references under the Linux Foundation precisely because no vendor holds exclusive control.
For anyone weighing whether to invest time and code in MCP, this move is relevant. A foundational technology - the kind other tools rest on - is valuable above all for its stability and for the confidence it inspires over the long run. Governance that isn’t tied to a single vendor makes the promise more credible: that the standard will stay open and supported in the future too.
What changes (and what doesn’t) right now
For those already using MCP, little changes on the technical side in the short term. According to the announcement, the governance model introduced earlier continues as it was: decisions about the protocol stay with the same people who look after it, the maintainers - those who keep the project going and evolve it - guided by community input through the process used to propose and discuss changes. Day-to-day development continues uninterrupted. Anthropic, for its part, says it will keep investing in development, maintain core infrastructure, and take part in the community.
In practice, the change is more about form than technical substance: the standard stays the same, what changes is the house that hosts it and the rules of whoever decides its future. That’s exactly the point of the news. There’s no new version of the protocol to adopt and no API to rewrite; there’s a different governing framework, designed to offer stronger guarantees of neutrality.
What remains to be seen
A few caveats are in order, without playing down the announcement. Moving to a foundation is a commitment of direction, not a done deal: the stated neutrality will have to be measured over time, by looking at how concrete decisions get made and how much the community can actually influence them. Having many companies around the same table is a positive sign, but governing a shared standard takes constant balance.
There’s also a broader point. MCP is a young, evolving standard: anyone adopting it does well to follow its updates and not treat everything available today as final. Moving under the Linux Foundation doesn’t freeze the protocol; it hands it to a structure meant to help it mature in the open.
In short
MCP is the standard that lets AI applications connect uniformly to external tools and systems. With the early-December 2025 announcement it was donated to the Agentic AI Foundation, a new foundation under the Linux Foundation, alongside two other founding projects and with backing from several companies in the field. On the technical side little changes: the same maintainers keep looking after it and development goes on. What changes is governance, moving from a single company to a neutral structure. For people building on top of MCP that’s the difference that matters most: an open standard not tied to a single vendor is easier to adopt with confidence. A step in the right direction, whose durability will remain to be checked over time.
