Comparison
UCP vs MCP: they are not competitors.
They are often set against each other because both carry the word "protocol." In reality, the Model Context Protocol (Anthropic) and the Universal Commerce Protocol (Google, Shopify) work at two different layers: one connects the agent to its tools, the other carries the purchase. Here is how they fit together, with a diagram, a worked example and a quiz.
The essentials in 30 seconds
- MCP (Anthropic, Nov 2024): how an agent connects to tools and data. A context layer, with no commerce or payment.
- UCP (Google/Shopify, Jan 2026): how an agent discovers and buys from a merchant. A transactional layer.
- They do not compete: different layers. UCP can even be exposed over an MCP transport.
- For a merchant: MCP does not replace UCP. UCP (or ACP) carries the transaction; MCP is a way to reach it.
Where MCP and UCP sit in the agentic stack
The simplest way is to see them as layers. An agent first connects to tools (transport), then discovers and triggers a purchase (commerce), then settles (payment). MCP is a standard of the bottom layer; UCP, of the middle one. Established
MCP and UCP are not on the same line: one transports, the other describes commerce.
The dimension-by-dimension comparison
| Dimension | UCP (commerce) | MCP (context / tools) |
|---|---|---|
| Nature | Agentic commerce protocol: discovery and purchase at a merchant | Agent-to-tools connection protocol: access to tools, data and systems |
| Creator | Google and Shopify, with Etsy, Wayfair, Target, Walmart and 20+ partners | Anthropic, open source (later donated to a foundation) |
| Introduced | January 2026 (NRF) | November 2024 |
| Question it answers | "How does an agent discover and buy from a merchant?" | "How does an agent access the tools and data it needs?" |
| Scope | Vertical: the commercial transaction | Horizontal: any tool or data source |
| Discovery | Standardized /.well-known/ucp merchant manifest | MCP server exposing resources, tools and prompts to a client |
| Payment | Modular payment handlers (Google Pay, Shop Pay...) | Out of scope: MCP does not process payments |
| Merchant of record | The merchant | Not applicable (MCP does not transact) |
| Relation to the other | Can be exposed over an MCP transport | Can act as a transport for a UCP catalog or capability |
| Code | Open source: spec, Python SDK, samples on GitHub | Open source: open spec and multiple SDKs (Python, TypeScript...) |
The confusion comes from one word: "protocol"
MCP and UCP are both open standards, backed by major players, arriving a few months apart. Hence the temptation to pit them against each other. But they do not describe the same thing. Established
MCP is a context layer. It answers a question of access: how does an agent plug in its tools, files, databases, APIs? Released by Anthropic in November 2024, it defines a client-server architecture where the agent (the client) discovers and invokes resources exposed by servers. By 2026 it had become the standard way to connect an agent to the outside world.
UCP is a transactional layer. It answers a question of commerce: how does an agent discover a merchant, read its up-to-date catalog, and trigger a purchase for which the merchant stays merchant of record? It is a vertical, specialized standard, where MCP is horizontal and generic.
A concrete, end-to-end scenario
Picture an agent asked to buy a pair of running shoes in size 43, budget 120 €.
- Connection (MCP). The agent connects to the merchant's MCP server and discovers the exposed tools: search a product, read a listing, check stock.
- Commerce discovery (UCP). Through those tools, it reads the merchant's UCP manifest and catalog: available models, sizes, up-to-date prices, return policy.
- Decision. The agent selects a size 43 model at 110 €, within the constraints.
- Transaction (UCP). It triggers the order per UCP. The merchant stays merchant of record: billing, support and legal liability remain with it.
- Payment (AP2 / handler). Settlement goes through a payment handler or a mandate authorization (AP2), within the limits set by the user. MCP is not involved here.
At no point did MCP and UCP "clash": MCP opened the door, UCP described the sale, a payment layer settled. Emerging
Three misconceptions
"MCP will replace UCP"
No: they do not cover the same need. MCP standardizes access to tools and data; it describes neither a merchant catalog, nor an order, nor a settlement. A merchant that only exposes MCP is not "sellable" by an agent until a commerce layer (UCP or ACP) describes the transaction.
"You must choose MCP or UCP"
A false dilemma. A tool vendor often needs only MCP; a merchant, often only UCP; a platform, both. And when both are present, they stack: MCP transports, UCP describes the commerce.
"MCP is used to pay"
No. Agentic payment is handled by dedicated standards: UCP payment handlers, Instant Checkout / Visa on the ACP side, or AP2's authorization via cryptographic mandates. MCP stays upstream, on access to capabilities.
What they share
- Open source as an adoption strategy: public specifications on both sides, to become de facto standards rather than closed products.
- The same underlying bet: the agent becomes a first-class usage surface, and standards are needed for it to act without a bilateral integration every time.
- The same merchant prerequisite: accurate data and explicit capabilities. Whether exposed via MCP or UCP, a poor catalog stays poor.
To prepare that foundation, the readiness audit methodology scores your state layer by layer, and the UCP implementation guide details the path on the commerce side. The note on UCP, Catalog MCP, and WebMCP on Shopify shows how those layers map to a current implementation.
Understanding MCP in video
Anthropic revisits why MCP was built and its move to open governance.
Source: official Anthropic channel (YouTube, no-cookie mode).
Test your understanding
-
1. Who released MCP?
-
2. Agentic purchase payment is carried by…
-
3. UCP and MCP are…
-
4. In UCP, a merchant becomes discoverable via…
-
5. Can an MCP server expose a UCP catalog?
Frequently asked questions
01 Are UCP and MCP competitors?
Are UCP and MCP competitors?
No. They operate at two different layers of the agentic stack. MCP answers "how does an agent access tools and data?"; UCP answers "how does an agent discover and buy from a merchant?". You can use both at once: they do not replace each other, they stack.
02 Is MCP used to pay for a purchase?
Is MCP used to pay for a purchase?
No. MCP is a context and tools protocol: it standardizes the connection between an agent and external resources, not the settlement of a transaction. Agentic payment relies on other standards: UCP (via its payment handlers), ACP on the OpenAI side, or AP2's mandate-based authorization.
03 Can an MCP server expose a UCP catalog?
Can an MCP server expose a UCP catalog?
Yes, and that is where the two meet. The UCP specification supports four transports (REST, MCP, A2A and embedded). A merchant can therefore expose its UCP capabilities through an MCP server: the agent connects over MCP, discovers the merchant's tools, then invokes the transaction per UCP. MCP is the pipe, UCP is what flows through it on the commerce side.
04 Should you choose between implementing MCP or UCP?
Should you choose between implementing MCP or UCP?
The question does not arise in those terms: they answer two distinct needs. MCP matters mostly to those exposing tools and data to agents (SaaS, internal databases, APIs). UCP matters to merchants who want to be discoverable and transactable by agents. A merchant may need only UCP; a tool vendor, only MCP; a platform, both.
05 What is MCP, concretely?
What is MCP, concretely?
The Model Context Protocol is an open standard released by Anthropic in November 2024. It defines a client-server architecture by which an AI application (the client) connects to servers that expose resources, tools and prompts. Its aim is to be a universal connector between models and the outside world, often described as a "USB-C port" for AI. By 2026 it had become the standard way to plug an agent into tools.
06 Where does payment sit in all this?
Where does payment sit in all this?
Above commerce. Once the transaction is described by UCP (or ACP), settlement goes through an authorization and payment layer: UCP handlers, Visa Intelligent Commerce and Mastercard Agent Pay on the network side, AP2 for mandate-based authorization, or x402 for stablecoin settlement. MCP is involved at none of these layers.
Primary sources
Go further
The commerce standards comparison, the UCP reference and the agentic payment context.