Who Backs MCP, A2A, UCP and ACP, and Which Ones a Merchant Should Support

AI agent integration protocol standards in 2026 come down to five names a merchant keeps hearing: MCP, A2A, UCP, ACP and AP2. They get lined up as rivals, yet most of them stack. MCP connects an agent to tools, A2A connects agents to each other, UCP and ACP describe shopping and checkout, and AP2 covers proof that a buyer authorized a payment. The clearest overlap among them sits on the commerce layer, where UCP and ACP both describe checkout. The map below reflects what each project's own pages said on October 7, 2026, followed by the combination we would support by platform and catalog size.

Who backs each protocol, and what does it specify?

The MCP and A2A rows trace back to one host. The Linux Foundation announced the Agentic AI Foundation on December 9, 2025, with MCP as a founding contribution and Amazon Web Services, Anthropic, Block, Bloomberg, Cloudflare, Google, Microsoft and OpenAI as platinum members. The Model Context Protocol specification stood at version 2026-07-28, marked latest, when we read it. A2A took the same road. The A2A Protocol project wrote on August 27, 2026: "The Agent2Agent (A2A) protocol has officially been accepted as a Growth Stage project at the Agentic AI Foundation (AAIF)."

UCP keeps its own governance. The Universal Commerce Protocol home page shows Google, Shopify, Etsy, Wayfair, Target, Walmart, Amazon, Microsoft, Meta, Salesforce and Stripe as shopping co-developers. The announcements page on ucp.dev records Stripe joining the Governing Council on April 28, 2026 beside permanent members Google and Shopify, four days after the Tech Council grew to 16 seats with new members from Amazon, Meta, Microsoft, Stripe and Salesforce. The Agentic Commerce Protocol site credits Stripe and OpenAI as its developers. Payment authorization has moved to a standards body: the FIDO Alliance announced on April 28, 2026 that "Google has contributed its Agent Payments Protocol (AP2), which introduces a model for secure delegation, verifiable authorization and trusted transaction execution."

Do these protocols compete, or do they stack?

AI agent protocol standardization has delivered interoperability mostly through layering, and the projects say so in their own words. The Linux Foundation release of April 9, 2026 puts it in one sentence: "A2A defines how agents communicate and coordinate with each other across organizational boundaries, while MCP defines how agents connect to internal tools and data sources." UCP sits above both. Its home page lists REST and JSON-RPC transports with AP2, A2A and MCP support built in, and Shopify.dev describes its implementation this way: "Shopify's MCP tools implement UCP at every step of the buyer journey". An agent shopping a Shopify catalog through those tools runs UCP and MCP together.

Formal standards work is arriving at the edges. NIST created its AI Agent Standards Initiative page on February 17, 2026 and updated it on August 14, 2026; its second pillar reads: "NIST engages with the AI ecosystem to identify and reduce barriers to interoperable agent protocols." The method it describes is voluntary guidelines that inform industry-led standardization. The overlap left unresolved is UCP and ACP, since both describe checkout between an agent and a merchant.

How far has adoption of MCP and A2A gone?

Agent protocol standard adoption in 2026 is best documented for MCP and A2A, and both figures come from the Linux Foundation. Its December 9, 2025 release counted "more than 10,000 published MCP servers" and named Claude, Cursor, Microsoft Copilot, Gemini, VS Code and ChatGPT among the platforms that had adopted the protocol. Its April 9, 2026 release reported more than 150 organizations supporting A2A, up from more than 50 in April 2025, with A2A integrated into Azure AI Foundry, Copilot Studio and Amazon Bedrock AgentCore Runtime. These are counts of servers and of supporting organizations. We found no figure on either page for how many agent tasks or purchases ran over the protocols.

Is there a standard marketplace or directory for agents yet?

Agent marketplace standardization trails MCP and A2A protocol adoption by a wide margin. The same April release lists "consolidation of efforts for registry" among A2A's roadmap items, so a shared registry is planned work. MCP already runs one for tools: the Model Context Protocol site calls the MCP Registry "the official centralized metadata repository for publicly accessible MCP servers" and says it is currently in preview. For merchants, the Agentic Commerce Protocol site says: "We're working to create discovery mechanisms for AI platforms to identify businesses that have implemented ACP." We found no single directory where a merchant registers once and becomes visible to every assistant, which leaves each platform deciding which catalogs it reads.

What changed between 2025 and 2026?

AI agent integration standards moved from single-vendor projects into shared governance across 2025 and 2026. Read in date order, agent protocols standardization over 2025 and 2026 went as follows:

• April 2025: A2A's supporter count starts at more than 50 organizations.
• December 9, 2025: the Agentic AI Foundation forms around MCP, goose and AGENTS.md.
• January 11, 2026: the earliest release on UCP's announcements page, v2026-01-11.
• April 9, 2026: the Linux Foundation reports A2A at version 1.0 with more than 150 supporters.
• April 24 to 28, 2026: UCP's Tech Council expands to 16 seats, Stripe joins its Governing Council, and the FIDO Alliance announces Google's AP2 contribution.
• August 25 to 27, 2026: UCP releases v2026-08-25 and A2A announces its move into the Agentic AI Foundation.

Governance has consolidated while the specifications keep moving. MCP's current version label is 2026-07-28 and UCP's latest release is six weeks old, so anything built against either should budget for revisions.

What does UCP ask a merchant to expose?

In agentic commerce, the merchant capabilities that AI shopping agents can call are standardized by UCP in 2026, with MCP as one of the transports that carries them. The Universal Commerce Protocol home page names them: "The protocol supports a range of core capabilities, including: Catalog Search and Lookup, Cart Building, Identity Linking, Checkout, and Order Management." Retail is the most developed part. A draft Lodging booking capability was announced on September 25, 2026, and the site marks Food as coming soon. The same page says businesses remain the Merchant of Record.

What Google and OpenAI have switched on is narrower than what the specifications allow. Google Merchant Center Help limits its article to products with eligibility in the United States, Canada and Australia and adds a note: "The checkout feature enabled by UCP is available for select merchants at this time." OpenAI describes ACP's present role in ChatGPT this way: "Today, it supports product discovery and more accurate, personalized recommendations through shared product data." Its merchant FAQ says the company is moving away from a standalone Instant Checkout experience and states: "Users can discover and evaluate products in ChatGPT, but purchases are completed on merchant-owned websites or apps." The same page says shopping is currently live for ChatGPT users in the U.S.

Protocols or direct integrations?

In the 2026 agent ecosystem, protocols such as MCP and A2A have standardized the plumbing, while getting a catalog in front of shoppers still runs through direct integrations with each platform. Asked whether implementing the protocol means automatic listing, the Agentic Commerce Protocol site answers: "No, each AI platform will manage their own process for how businesses can participate." OpenAI's merchant page takes applications for product feeds, tells earlier applicants they are on the waitlist, and exempts two groups: "If you sell through Shopify or Etsy, your catalog is already integrated, and no additional setup or application is required." Google asks for an interest form and a technical implementation before its UCP checkout appears on a listing.

The practical unit of adoption, then, is the commerce platform. The Shopify Help Center lists ChatGPT, Google AI Mode and Gemini, Microsoft Copilot and Meta as AI channels and says: "Agentic storefronts is active by default for eligible stores." A merchant there inherits the protocol work. Every merchant still depends on basics that predate these protocols: crawlable product pages, covered in How to Get Cited by ChatGPT, and prices and policies that agree across feed, page and profile, which is the subject of our entity consistency audit.

Which combination should a merchant support?

Our recommendation sorts by platform first and catalog size second. The size bands are a working assumption of ours. We found no catalog-size threshold in any specification or platform page we read, although OpenAI's merchant application does ask for a unique SKU count, in bands that begin at 0 to 1M.

Two reasons sit behind the size split, and both are our judgment. A live catalog capability earns its engineering cost when prices and stock change faster than a batch feed can carry them, which gets more likely as SKU counts grow. A checkout integration is a fixed cost that needs order volume to spread across. Smaller merchants off Shopify have one more route to weigh: the Shopify Help Center says its Agentic plan "lets you set up agentic storefronts and keep your existing online store."

A hypothetical example shows the order of work. A home goods retailer that sells to shoppers in the United States runs 40,000 SKUs on a headless storefront with its own checkout. It keeps the Merchant Center feed current, applies for an OpenAI product feed and submits Google's UCP interest form. If Google accepts the store, the team builds UCP checkout and marks eligible listings with the native_commerce(checkout_eligibility) attribute that Merchant Center Help requires for the Buy button. It skips an ACP checkout build, because OpenAI's page says purchases are completed on merchant-owned sites, and it publishes no A2A agent card until a partner asks for one.

MCP and A2A matter more for the agents a company builds for its own operations, which is where our agentic AI automation practice works. For selling through assistants, no protocol on this list decides whether a product gets recommended in the first place. That is a visibility question, the one generative engine optimization addresses and AI share of voice measures. The AI Visibility Checker is a further resource for a first reading, and our AI search optimization team takes on the rest.

Sources

• Linux Foundation: Formation of the Agentic AI Foundation, December 9, 2025
• Model Context Protocol: Specification, version 2026-07-28
• Linux Foundation: A2A Protocol surpasses 150 organizations, April 9, 2026
• A2A Protocol: A New Chapter for A2A, joining the Agentic AI Foundation, August 27, 2026
• Universal Commerce Protocol: Home page, with co-developers, endorsers and capabilities
• ucp.dev: Universal Commerce Protocol announcements, with releases and council changes
• Agentic Commerce Protocol: Home page and frequently asked questions
• OpenAI: Merchants page for shopping in ChatGPT
• Shopify Help Center: Shopify agentic storefronts
• Shopify.dev: Build commerce agents with UCP
• Google Merchant Center Help: About the Universal Commerce Protocol (UCP) and UCP-powered checkout feature on Google
• NIST: AI Agent Standards Initiative
• FIDO Alliance: FIDO Alliance to Develop Standards for Trusted AI Agent Interactions, April 28, 2026
• GitHub: Agentic Commerce Protocol repository, with status and released versions
• Model Context Protocol: The MCP Registry