Which organization governs MCP, A2A, and ACP as of 2026?
MCP, A2A, and ACP each have separate governance in 2026: MCP under Anthropic, A2A under the Linux Foundation, ACP under IBM Research / BeeAI. No single umbrella body; interop comes from working groups.
Think of three companies that each invented their own kind of electrical plug. At first, each company controlled its own design. That worked fine alone, but devices could not mix and match. Eventually they all agreed to hand their designs to a neutral standards body so the plugs would play nicely together. The agent protocols followed the same arc. MCP came from one company, the agent to agent protocol from another, and a third interop effort from elsewhere. By 2026 they sit under a shared, vendor-neutral home so any tool, agent, or host can interoperate without picking a single vendor's side.
Detailed answer & concept explanation~7 min readEverything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example. Click to expand.
Everything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example. Click to expand.
Everything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example.
Everything important, quickly.
5 min: what each of the three protocols solves, the vendor to neutral governance lifecycle, why the Linux Foundation is the canonical host, and how to hedge on exact names and figures.
| Protocol | Problem it solves | Original vendor |
|---|---|---|
| MCP | Connect one agent to tools, resources, and prompts | Anthropic (open spec, modelcontextprotocol working group) |
| A2A | Let separate agents discover and message each other | Google -> donated to Linux Foundation (2025) as Agent2Agent |
| ACP | Broader agent interoperability, REST-oriented | IBM Research / BeeAI project |
| Governance (2026) | Three independent tracks; no single umbrella body | Anthropic + Linux Foundation + IBM/community |
Real products, models, and research that use this idea.
- Anthropic continues to publish MCP spec revisions through the modelcontextprotocol working group on GitHub, with no donation to a neutral foundation as of 2026.
- Google donated A2A to the Linux Foundation in 2025 as the Agent2Agent project, following the same vendor to neutral foundation pattern as Kubernetes under the CNCF.
- IBM Research's BeeAI project continues to develop ACP as a REST-based agent communication protocol, independent of the Anthropic and Google governance tracks.
What an interviewer would ask next. Try answering before peeking at the approach.
QWhy does vendor-seeded then neutrally governed beat a standard born inside a committee?
QHow do MCP and the agent to agent protocol differ in what they connect?
Don't say thisRed flags and common mistakes that signal junior thinking. Click to expand.
Red flags and common mistakes that signal junior thinking. Click to expand.
Assuming all three protocols converged under one umbrella foundation. They have not. Each remains under its originating organization, with only A2A having moved to neutral Linux Foundation stewardship.
The night-before-the-interview bullets. Scan these on the way to the call.
Primary sources. Skim if you want the original framing.
Same topic, related formats. Practice these next.