Protocols & news

MCP vs A2A vs UCP: AI agent protocols compared

Listen · 11 min

Narrated by an AI voice. Code examples are on the page.

Short answer

MCP, A2A and UCP connect different things. MCP connects an AI app to tools and data, A2A connects one AI agent to another agent, and UCP is a commerce standard that lets an agent shop and check out with a business. They are not rivals: UCP can run over MCP or A2A, and an A2A agent can use MCP behind the scenes.

Key takeaways

  • MCP connects AI apps to tools and data.
  • A2A connects AI agents to other agents.
  • UCP handles shopping and checkout, and can run over either.

What is the difference between MCP, A2A and UCP?

The short version of MCP vs A2A vs UCP: each one connects a different pair of things.

  • MCP (Model Context Protocol) connects an AI application to tools and data. The MCP project calls it "an open-source standard for connecting AI applications to external systems."
  • A2A (Agent2Agent) connects one AI agent to another agent. The Linux Foundation calls it "an open standard that enables AI agents to discover, communicate, and transact with each other."
  • UCP (Universal Commerce Protocol) connects AI agents and platforms to businesses for shopping. Its site calls it "the common language for platforms, agents, and businesses."

MCP and A2A are general-purpose. They work for any kind of task, from booking a meeting to searching a database. UCP is built for commerce: catalog, cart, checkout and orders.

People compare them because all three show up in conversations about AI agents and stores. They are not three competing answers to one question. They answer three different questions, and they are designed to be used together.

What does each protocol actually connect?

Think about who is on each end of the connection.

MCP: an AI app and a tool. On one side is an assistant such as Claude or ChatGPT. On the other is an MCP server that offers tools, such as "search products", plus data and prompts. The assistant asks the server what it offers, picks a tool and calls it. The server does not need to be clever. It just needs to describe its tools clearly. See what MCP is.

A2A: an agent and another agent. Both sides can think for themselves. The A2A specification describes them as "independent, often opaque, AI agents" that "communicate and collaborate with each other as peers." One agent reads the other's agent card, sends it a message, and tracks the task it creates. The other agent decides how to do the work and does not have to explain its internals. See what A2A is.

UCP: a shopping agent and a business. A business publishes a profile at /.well-known/ucp that lists what it supports, such as checkout, and how to pay. A shopping agent reads it and runs a checkout. UCP's site lists "Catalog Search and Lookup, Cart Building, Identity Linking, Checkout, and Order Management" among its core capabilities. See what UCP is.

MCP vs A2A vs UCP: how do they compare side by side?

MCP A2A UCP
Connects An AI app to tools and data An AI agent to another agent A shopping agent or platform to a business
Scope General purpose General purpose Commerce
Introduced Anthropic, 25 November 2024 Google, April 2025 Google with Shopify and others, 11 January 2026
Governed by Agentic AI Foundation (Linux Foundation) Agentic AI Foundation (Linux Foundation) Google, Shopify and co-developers; Apache 2.0 licence
How an agent finds you Connects to your MCP server's URL Reads your agent card Reads your profile at /.well-known/ucp
Main unit A tool call A task A capability, such as checkout
Runs over Streamable HTTP for remote servers JSON-RPC, gRPC or HTTP+JSON REST, MCP, A2A or embedded
Handles payment? No No Checkout uses payment handlers, with AP2 support

A few details behind the table:

  • MCP's 28 July 2026 revision made it stateless. The changelog says it removes "the initialize / notifications/initialized handshake" and adds server/discover, which servers "MUST implement" to advertise their versions, capabilities and identity.
  • A2A reached v1.0, which the Linux Foundation called "its first stable specification," with signed agent cards for "cryptographic identity verification."
  • UCP is versioned by date. The current specification overview's examples use version 2026-08-25.

How do MCP, A2A and UCP work together?

They stack. UCP can travel over MCP or A2A, and an A2A agent can use MCP to get its work done.

UCP over MCP or A2A. Google's developer post says UCP "supports multiple transports including A2A, MCP and APIs." In a UCP business profile, each service entry names a transport: rest, mcp, a2a or embedded. For A2A, the specification says the endpoint "refers to the Agent Card URL for the agent." So a store could offer the same checkout to an MCP client and to an A2A agent.

A2A on top of MCP. The A2A specification calls the two "complementary protocols." Its example: a client agent asks a server agent to do a complex task, and "the Server agent, in turn, might use MCP to interact with several underlying tools, APIs, or data sources." The A2A project puts it as MCP being the "vertical integration layer" and A2A "the horizontal protocol."

AP2 across all three. AP2, the Agent Payments Protocol, adds signed proof of what a shopper approved. Google said when announcing AP2 that it "can be used as an extension of the Agent2Agent (A2A) protocol and Model Context Protocol (MCP)." UCP's site says it has AP2 "support built-in." For how AP2 compares with the other payment standards, see ACP, AP2, UCP and x402 compared.

A simple example: a shopper asks an assistant to reorder printer ink. The assistant might use MCP to search a store's catalog, hand the order to the store's agent over A2A, and complete the purchase through UCP's checkout. In practice, many setups will use only one or two of these steps.

Who governs MCP, A2A and UCP?

MCP and A2A now sit in the same foundation. UCP is led by its co-developers.

MCP. The Linux Foundation formed the Agentic AI Foundation (AAIF) in December 2025, with Anthropic's MCP as a founding project alongside Block's goose and OpenAI's AGENTS.md.

A2A. The Linux Foundation took on A2A on 23 June 2025, calling it "an open protocol created by Google." On 27 August 2026 the A2A project said it had "officially been accepted as a Growth Stage project at the Agentic AI Foundation (AAIF)." So MCP and A2A are now sibling projects. See what the AAIF is.

UCP. Google announced UCP on 11 January 2026 as "a new open standard for agentic commerce." It is published under the Apache 2.0 licence, and its site lists Google, Shopify and many retailers, platforms and payment companies as co-developers and endorsers. We found no statement that UCP has moved to a foundation.

Which one should your store look at first?

It depends on what you want agents to do.

  1. You want agents to buy. Start with UCP. It is the checkout standard behind Google's AI Mode and Gemini, and selling there needs Google's own Merchant Center approval. Our UCP vs ACP comparison helps if you are also weighing ACP.
  2. You want assistants to search, check stock or look up orders. An MCP server gives them structured tools instead of page scraping. See does your store need an MCP server?.
  3. You want other businesses' agents to work with yours. Publish an agent card and an A2A endpoint. For most stores this comes after the other two.

Note. All three standards changed in 2026. Check modelcontextprotocol.io, a2a-protocol.org and ucp.dev for the current versions before you build.

How Sill helps. Sill publishes a signed agent card and runs an MCP server for each verified site, and keeps both current. It supports A2A message/send for your skills, and UCP checkout on sites with a connected Stripe account. Selling in Google's AI Mode and Gemini still needs Google's approval. When an AI agent places an order, your rules approve it, decline it or hold it for a person to review, and every decision is signed and recorded. Run a free readiness scan to see what agents find on your site today.

Questions people ask

Do I need MCP, A2A and UCP all at once?

No. Most stores start with whichever one their platform or a tool already provides. UCP matters most if you want agents to check out, and it can be offered over REST without MCP or A2A.

Is UCP built on MCP?

Not exactly. UCP is its own standard with its own capabilities. MCP is one of the transports it can use, alongside REST, A2A and an embedded option.

Which came first, MCP or A2A?

MCP. Anthropic introduced it on 25 November 2024. Google launched A2A in April 2025, and Google announced UCP on 11 January 2026.

Do MCP, A2A or UCP handle payment?

MCP and A2A do not handle payment themselves. UCP's checkout uses payment handlers and supports AP2, the Agent Payments Protocol, for proof of what the shopper approved. AP2 can also be used as an extension of A2A and MCP.

Sources

  1. Model Context Protocol: What is MCP? · checked 17 Nov 2026
  2. Anthropic: Introducing the Model Context Protocol · checked 17 Nov 2026
  3. Model Context Protocol: Architecture overview · checked 17 Nov 2026
  4. MCP specification 2026-07-28: Key changes · checked 17 Nov 2026
  5. Linux Foundation: Formation of the Agentic AI Foundation · checked 17 Nov 2026
  6. A2A Protocol: Specification (v1.0) · checked 17 Nov 2026
  7. A2A Protocol blog: A new chapter for A2A, joining the Agentic AI Foundation · checked 17 Nov 2026
  8. Linux Foundation: Linux Foundation launches the Agent2Agent protocol project · checked 17 Nov 2026
  9. Linux Foundation: A2A Protocol surpasses 150 organizations in first year · checked 17 Nov 2026
  10. Universal Commerce Protocol (UCP) · checked 17 Nov 2026
  11. UCP specification overview · checked 17 Nov 2026
  12. Google: New tech and tools for retailers to succeed in an agentic shopping era · checked 17 Nov 2026
  13. Google Developers Blog: Under the hood: Universal Commerce Protocol (UCP) · checked 17 Nov 2026
  14. Google Cloud: Announcing Agent Payments Protocol (AP2) · checked 17 Nov 2026

Written by The Sill Signals Team. Last reviewed 17 Nov 2026.

Share this articleLinkedInXBlueskyEmail

Keep reading

See which AI agents visit your site, and decide what they may do.

Scan your site free