A2A moves under the Agentic AI Foundation, next to MCP

Two protocols run most of the agent tooling you'll touch this year. MCP describes how an agent reaches a tool or a data source. A2A describes how one agent talks to another. Until now they lived under different governance. That is changing: Google's Agent2Agent protocol is moving under the Agentic AI Foundation, the same body that already holds MCP.

What actually happened

Axios reported on August 17 that A2A is becoming a hosted project of the Agentic AI Foundation (AAIF), moving out of the Linux Foundation's general portfolio and into the foundation scoped specifically to agents.

The path A2A took is worth knowing, because it explains why this is a consolidation and not a launch. Google announced A2A in April 2025, then donated the specification, SDKs, and tooling to the Linux Foundation in June 2025. The Linux Foundation said in April 2026 that more than 150 organizations had backed the project.

AAIF is the newer body — formed in December 2025 around MCP, goose, and AGENTS.md. It counted 247 member organizations as of August 12, with Google, Microsoft, Amazon, Anthropic, OpenAI, Shopify, and Block among the backers.

So the two halves of the agent interop story now answer to the same board. That's the whole news. No spec changed this week.

Why agent interoperability standards matter for your business

One governance body is one place to read. If you're deciding what your integrations commit to, you now track one roadmap instead of two, and the odds of A2A and MCP drifting into incompatible identity or auth models go down. That is a real reduction in the amount of future rework you're exposed to.

A2A is the half most small teams skip. Almost everyone has wired up MCP. Far fewer have thought about what happens when a customer's agent — or a vendor's — wants to talk to yours. A2A's signed agent cards give you a way to answer "who is calling" that isn't a shared secret in a config file. That's the same shift MCP is making with agent identity.

Neutral governance is the portability argument. A protocol controlled by one vendor is a migration bill waiting to happen. A protocol governed by a foundation with 250 members that compete with each other is one you can build against for years.

Nothing here is urgent. No version bump, no deprecation, no migration. Read this as a signal about where to place a bet, not as work in your sprint.

Sources: Axios, Google Developers Blog, Linux Foundation.