Xc banner image

MCP Is Becoming Commerce's New HTTPS: Here's How and When Sellers Will Adopt

Vice President, Commerce and GenAI
  • Twitter
  • LinkedIn

The Quiet Shift From Pages to Protocols

E-commerce once revolved around what people could see: product detail page layouts, review carousels, and retargeting pixels. In the age of autonomous shopping agents, the focus shifts to what models can read and call. Anthropic’s Model Context Protocol (MCP) represents one of the most mature attempts to standardize that machine-to-catalog handshake, describing products, offers, and checkout functions in a single JSON manifest located at /.well-known/mcp/manifest.json.

Industry observers have already grouped MCP with Agent-to-Agent (A2A) and similar initiatives as the “USB-C moment” for AI — the missing piece that allows independent agents to interoperate at web scale.

 

Why Sellers Will Eventually Opt-In

The transition to agent-driven commerce raises legitimate concerns for merchants, but emerging solutions are addressing the main friction points.

Perceived Loss: No email capture, no pixel history
Reality: Agents can pass a signed, revocable shopper-profile token that merchants can feed into their CRM for post-purchase journeys. This keeps the process privacy-safe while remaining actionable.

Perceived Loss: Fewer upsell banners
Reality: Ranking systems that prioritize structured attributes such as warranty information or sustainability scores are already improving conversions in early pilots. Walmart’s internal testing shows measurable improvements when agents can surface differentiated value beyond price.

Perceived Loss: Fear of a price race to the bottom
Reality: MCP supports first-class “differentiator” fields such as bundled services or loyalty benefits, enabling merchants to present a full value proposition rather than competing purely on price.

 

Where the Critical Mass Comes From

1. Platform Defaults

  • Shopify is already transitioning merchants from legacy REST APIs to GraphQL Admin APIs by April 2025, signalling a move toward richer schema-based integrations.
  • Salesforce has introduced a Vector Search layer within Data Cloud, positioning it as a foundation for generative AI experiences. While MuleSoft is expected to support MCP, official direction for Commerce on Core is still pending.

2. Marketplace Mandates

Major marketplaces including Amazon, Walmart, and Temu are experimenting with agent-facing feeds that prioritise MCP-compliant offers. Industry insiders suggest Walmart may formalize this advantage by 2026.

3. Consumer Pull

Surveys indicate that roughly 38% of U.S. consumers — and a majority of Gen Z — already use generative AI assistants during some part of the buying journey. Once agent-driven checkouts reach around 10% of GMV within a vertical, merchants who opt out risk disappearing from recommendations entirely.

 

The Resulting Timeline

PhaseGMV Reachable via AgentsIndicative Window
Pioneer marketplaces & D2C~8%Now – H1 2025
Early majority (Shopify auto-enable, mid-tier clouds)30–40%H2 2025 – H1 2026
Late majority (WooCommerce, Magento, regional chains)55–70%2026 – 2027
Laggards (luxury brands, highly curated UX)Trailing 15%2028+

 

The Data-Ownership Truce

Protocol working groups are embedding consent directly into the specification. MCP v0.3 introduces a mandatory data_usage section, allowing merchants to block agents that do not respect retention limits. Regulators are also encouraging zero-party data flows similar to these tokens. Both Europe’s Digital Markets Act and recent amendments to California’s CCPA contain language that exempts such consent-driven data exchanges from the strictest tracking regulations.

 

What Merchants Should Do Now

  1. Audit your catalog attributes and fill gaps in pricing detail, dimensions, sustainability information, and warranty data.
  2. Deploy a vector index (Salesforce Data Cloud, pgvector, or Pinecone) to answer semantic queries such as “best option” within milliseconds.
  3. Expose a lightweight MCP layer over existing product and checkout APIs. Start with read-only endpoints before enabling actions like reserveItem or placeOrder.
  4. Tokenize loyalty programs so MCP shopper tokens can convert into full accounts with explicit user consent.
  5. Monitor protocol development. Anthropic’s MCP and cross-vendor A2A working groups release frequent schema updates that may affect integrations.

 

Bottom Line

MCP is not a future consideration — it represents the next major shift in digital commerce. Just as “mobile-first” reshaped the web a decade ago, agent-driven commerce is likely to redefine how customers discover and purchase products. By the time next year’s Black Friday dashboards refresh, a significant share of online GMV may already be flowing through agent calls. Merchants with clean data structures and accessible endpoints will be positioned to capture that traffic, while others may struggle to understand where their customers went.


Sources

  1. Anthropic – Introducing the Model Context Protocol
  2. Anthropic Documentation – MCP: USB-C for AI
  3. ModelContextProtocol.io – Introduction
  4. Business Insider – The future of AI will be governed by protocols
  5. Salesforce Blog – Vector Databases Built for the AI Era
  6. Salesforce Help – Vector Search in Data Cloud
  7. Shopify Developer Docs – REST Admin API Deprecation
  8. Deloitte Connected Consumer Survey 2024
  9. Bain & Company – Understanding the Five Types of AI Consumers (2025)