The short answer
MCP, ACP, UCP, and A2A sit at different layers of the same agent-commerce stack. MCP (Model Context Protocol, Anthropic) connects an AI agent to tools and data — it's how an agent queries your catalog live. ACP (Agentic Commerce Protocol, OpenAI + Stripe) is a commerce transaction standard — it's how ChatGPT completes a purchase from your store. UCP (Universal Commerce Protocol, Google + Shopify) is Google's equivalent commerce standard for AI Mode, Gemini, and YouTube Shopping. A2A (Agent2Agent, Google, now Linux Foundation) is agent-to-agent interoperability — how one agent delegates a task to another, commerce or otherwise. A merchant doesn't pick one: MCP makes you queryable, ACP and UCP make you buyable on the two biggest AI surfaces, and A2A mostly matters to the platforms wiring agents together.
Status as at July 2026 — this space ships breaking changes quarterly; verify against the specs before building: MCP, ACP, UCP, A2A.
The four protocols side by side
| MCP | ACP | UCP | A2A | |
|---|---|---|---|---|
| Steward | Anthropic (open spec) | OpenAI + Stripe (Meta co-creator) | Google + Shopify, 20+ endorsers | Google, donated to Linux Foundation |
| Launched | November 2024 | September 2025 | January 2026 (NRF) | April 2025 |
| Layer | Agent ↔ tools/data | Agent ↔ merchant checkout | Agent ↔ merchant checkout | Agent ↔ agent |
| Commerce scope | Catalog query, product lookup, quotes — anything you expose as a tool | Discovery through fulfilment since the 2026-04-17 release: feeds, cart, orders, Instant Checkout | Discovery, checkout, post-purchase in AI Mode / Gemini / YouTube Shopping | Task delegation between agents; payments via the companion AP2 protocol |
| Where it runs today | Claude, ChatGPT, and most agent frameworks support MCP clients | ChatGPT Instant Checkout: Etsy live, Shopify merchants rolling out; platform partners include Microsoft Copilot, Anthropic, Perplexity | Eligible US retailers in AI Mode and Gemini; announced for YouTube Shopping (May 2026); Canada/Australia announced | Platform infrastructure; not merchant-facing |
| What a merchant does | Host an MCP server exposing catalog tools | Provide ACP-shaped product feed + checkout endpoints (or let your platform, e.g. Shopify, do it) | Provide UCP feed/endpoints (Shopify merchants largely inherit it) | Usually nothing directly |
The practical read for a merchant
- MCP is the one you can adopt unilaterally, today. No platform partnership required: publish a remote MCP server over your catalog and any MCP-capable agent — Claude, ChatGPT, custom agents — can search products, pull specs, and request quotes against live data. For B2B catalogs with quote-based pricing and compatibility constraints, MCP is currently the only protocol that models "ask, don't just buy" interactions well.
- ACP and UCP are channel enrollments, not integrations you write from scratch. If you sell through Shopify, Etsy, or another major platform, your path into ChatGPT Instant Checkout (ACP) and Google's agentic checkout (UCP) is the platform's enrollment toggles and terms — verify they're switched on before writing any code. Custom-stack merchants implement the specs directly, feed-first.
- The two commerce protocols are rivals in surface, cousins in shape. Both are feed-plus-endpoint architectures; UCP explicitly declares interoperability with MCP and A2A, and payments efforts (Stripe in ACP, AP2 alongside UCP) are converging on delegated-payment patterns. Building your product data once, correctly, is the reusable asset across both.
- A2A you mostly watch. Unless you're building agents, its effect on merchants is indirect: it standardizes how a consumer's agent could hand your sales agent a task. The merchant-side prerequisite is the same as everywhere else — machine-readable, verifiable product truth.
What none of the protocols solve
Being *transactable* is not being *chosen*. All four protocols activate after an agent has decided your product is the answer — none of them influence whether you appear in the recommendation at all. That upstream layer is discovery and trust: buyer-question content on your domain, structured product data agents can cite, and measurement of your recommendation share across providers. Sequence accordingly: discoverable first, then queryable (MCP), then buyable (ACP/UCP).
FAQ
Do I need to implement all four protocols? No. A practical 2026 sequence: (1) structured product data + buyer-intent content — no protocol at all; (2) an MCP server if buyers ask detailed or configurational questions, which is standard in B2B; (3) ACP and UCP via your commerce platform's enrollment if you sell direct-to-consumer where in-chat checkout is live. A2A requires no merchant action today.
Is MCP a commerce protocol? No — MCP is a general standard for connecting agents to tools and data, used far beyond commerce. That generality is its strength for merchants: a catalog exposed over MCP serves search, spec lookup, comparison, and quote requests in one interface, where ACP/UCP model the narrower buy-this-item flow.
What is AP2 and how does it relate? AP2 (Agent Payments Protocol) is the payments companion in the Google-aligned stack — it standardizes how an agent gets authorized to pay on a user's behalf, with verifiable mandates. UCP handles the commerce flow; AP2 handles the payment authorization inside it. Stripe plays the equivalent role in the ACP stack.
If I'm on Shopify, what do I actually have to do? Mostly verify, not build: Shopify is a co-developer of UCP and a launch-scale ACP participant, so eligible merchants inherit both. Check that your agentic sales channels are enabled and terms accepted in the admin, that your product feed data (titles, GTINs, availability, highlights) is complete, and that your public product pages carry full JSON-LD — feed quality is the ranking input the protocols don't fix for you.
Which protocol wins? The honest answer: surfaces pick protocols, merchants pick surfaces. ChatGPT's commerce runs on ACP; Google's runs on UCP; both are open specs with overlapping endorsers (Stripe endorses UCP; Microsoft and Anthropic appear in ACP's partner list), and UCP declares MCP/A2A interoperability. Build the substrate once — verified product truth — and treat each protocol as a projection of it.