Agent protocols now share one landlord: A2A joins MCP and AGENTS.md at the Linux Foundation

Yugabyte says it has joined the Linux Foundation's Agentic AI Foundation as a Silver Member, and in explaining why, it noted something more consequential than its own membership: the foundation has accepted Google's Agent2Agent protocol as a growth-stage project ^[1][5]. That puts the two protocols most teams were told to choose between, MCP for tool access and A2A for agent-to-agent communication, under the same governance roof ^[6].

The foundation was formed by the Linux Foundation in December 2025, framed as giving agentic AI standards the neutral governance the Linux Foundation already provides to Kubernetes and PyTorch ^[3]. Its founding projects came from three separate vendors: Anthropic's Model Context Protocol, Block's goose, and OpenAI's AGENTS.md ^[4]. Add A2A and there are four named projects, contributed by four companies that compete directly, sitting inside one standards body ^[14].

For anyone doing procurement or architecture, that changes the shape of the decision. A year ago, picking MCP over A2A or vice versa carried an implicit bet on which vendor's ecosystem would survive. The bet is now largely about technical fit and adoption curve, not about whether the specification's owner will fork it, relicense it, or quietly abandon it when a product strategy shifts. Neutral stewardship does not guarantee good specifications; it removes one class of risk that had nothing to do with engineering.

Yugabyte's own stake is the honest part of the post. It has shipped two products aimed at agents: YugabyteDB AMP, which gives each agent an isolated Postgres database with serverless scale-to-zero for fleets where databases live briefly, and Meko, a context engine holding persistent memory, shared knowledge, conversation history and decision traces ^[7][8]. Agents reach Meko through MCP, and Meko's connector is listed in Anthropic's directory ^[8][12]. The company's stated reason for paying to sit at the table is direct: the protocols matter to its stack, so when they change, it changes ^[9]. That is a vendor with a dependency, not a vendor with a philosophy, and it is a more credible motive.

The company also argues the conventions for how agents store, share and retrieve context are being written right now, and that what the foundation settles will determine whether agent state ends up on durable infrastructure ^[11][15]. That is Yugabyte's framing, from a company that adopted a fully open-source Apache 2.0 model for YugabyteDB in 2019 and has an interest in context being a first-class layer ^[10].

Two limits worth keeping in view. This is a single vendor's membership blog, and it gives no date for the A2A acceptance beyond "recently" and no figure for what Silver membership costs ^[16]. Governance consolidation also says nothing about interoperability in practice: four projects under one foundation can still specify overlapping, awkwardly composed abstractions.

What to watch: whether A2A moves from growth stage to a fuller status and who lands on its technical steering; whether context and memory conventions arrive as a foundation project rather than as competing vendor SDKs ^[11]; and whether membership growth brings in the infrastructure layer or stays weighted toward model labs. Yugabyte is hosting an Agentic AI Foundation meetup at its Sunnyvale headquarters on Wednesday, August 27, with talks on LLM memory and moving beyond context windows ^[13].