Skip to content
→Get Shopify + paid media in one prompt
Migration deadline · June 15, 2026 · Explainer

UCP (Universal Commerce Protocol) — Shopify + BigCommerce's MCP Successor

Shopify's Storefront MCP sunsets on June 15, 2026. Universal Commerce Protocol (UCP), co-led with BigCommerce, takes over — a portable spec for AI agents that travels across storefronts instead of locking to one. Here's what's changing, what's at risk in your workflows, and how to migrate cleanly.

Aditya Sriram in ↗

Co-founder, GoMarble · Updated 2026-06-05 · 7 min read

Try GoMarble for Shopify analytics Shopify MCP comparison →

What's happening

  • →Sunset date: Shopify's legacy Storefront MCP endpoints stop working June 15, 2026.
  • →Successor: Universal Commerce Protocol (UCP) — Shopify and BigCommerce co-led, portable across storefronts.
  • →What's new: Expanded customer/account surface, analytics signals, cross-platform portability.
  • →If you self-host Storefront MCP: Update endpoint URLs and OAuth scopes before June 15.
  • →If you're on Shopify's Admin API: Different surface — UCP migration doesn't affect you.

What UCP actually is

Universal Commerce Protocol is an open spec for AI agents to operate on ecommerce stores. Shopify and BigCommerce are co-leading it, with the explicit goal of portability — the same prompt should work whether the underlying store runs on Shopify, BigCommerce, or any other UCP-conformant storefront.

The architecture mirrors how MCP itself works: a server-side standard that exposes commerce primitives (catalog, cart, checkout, customer, analytics) as agent-callable tools, with a portable auth and discovery contract.

It replaces Shopify's Storefront MCP (released late 2025) which was Shopify-only. UCP is the second-generation answer to "how do AI assistants do commerce" — one designed to be vendor-portable from day one.

What changes vs Storefront MCP

Four meaningful additions; one timeline you can't ignore.

Customer account operations

First-class agent access to customer accounts, addresses, payment methods, and order history — not just storefront browse/buy.

Analytics signals

Standardized storefront analytics surface (sessions, conversions, funnel signals) callable as MCP tools.

Cross-platform portability

Same prompt works across Shopify and BigCommerce. No platform-specific tool names baked in.

Auth model

Storefront and admin auth modes formalized in the spec, with explicit scope contracts for agent-readable vs agent-writable operations.

Endpoint changes

Legacy mcp.shopify.com/storefront endpoints stop accepting new integrations after June 15, 2026. UCP endpoints have a different routing scheme.

Tool naming

Generic UCP tool names replace Shopify-specific names. If you hardcoded tool names in scripts, you need to remap.

Your migration checklist (if you self-host)

  1. Inventory affected integrations — every place a Storefront MCP endpoint appears in Claude / ChatGPT / Cursor configs, custom MCP clients, or internal tools.
  2. Map tool names — UCP tools have generic names. If your prompts call shopify_storefront_get_product, find the UCP equivalent and update.
  3. Update endpoint URLs — replace Storefront MCP endpoints with UCP endpoints in every connector config.
  4. Refresh OAuth scopes — UCP formalizes scope contracts. Re-authorize with the new scopes before sunset day.
  5. Test in a staging Shopify store — UCP semantics differ slightly. Validate cart, checkout, and customer-account flows before flipping production.
  6. Watch for hardcoded responses — if your prompt parsing depends on legacy response shape, expect drift. UCP response schemas are subtly different.

Realistic effort estimate: 1–3 days for a small/medium integration, depending on how many custom workflows use Shopify endpoints.

Where GoMarble fits (and where it doesn't)

Worth being clear: GoMarble doesn't migrate Storefront MCP to UCP for you. They're different API surfaces for different jobs.

GoMarble’s hosted MCP exposes Shopify data via the Shopify Admin API — orders, customers, products, analytics. Useful for paid media reconciliation, SKU-level ROAS analysis, Klaviyo + Shopify attribution. Not on the Storefront MCP surface. So if your team uses GoMarble's Shopify integration for paid media analytics, the UCP migration doesn't affect you — you're on a different surface.

UCP is the right call if you're building agentic commerce — AI-driven catalog browsing, agent-initiated cart/checkout, customer-account operations triggered by Claude. That's what Storefront MCP / UCP is for. GoMarble isn't the tool for that job; migrate to UCP before June 15.

If your Shopify use case is paid media + revenue analysis rather than agentic commerce, GoMarble’s hosted MCP joins Shopify orders with Meta + Google + TikTok + LinkedIn + Bing ad data, Klaviyo email attribution, GA4, and competitor research — in the same connection. No Storefront MCP involvement.

FAQ

What is UCP (Universal Commerce Protocol)?
UCP is a Shopify and BigCommerce co-led open protocol for AI agents to operate on ecommerce stores. It replaces the legacy Storefront MCP endpoints with a unified spec covering catalog, cart, checkout, customer accounts, and analytics signals — designed to be portable across platforms instead of locked to one storefront vendor.
When does Shopify's Storefront MCP sunset?
June 15, 2026. After that date, the legacy Storefront MCP endpoints stop accepting new integrations. Existing integrations need to be migrated to UCP endpoints before then or they will stop working.
Does this affect my AI assistant (Claude / ChatGPT) workflow?
If you added Shopify's Storefront MCP as a custom connector in Claude, ChatGPT, or another MCP-compatible client — yes. After June 15, 2026, the connector needs to be reconfigured to point at UCP endpoints. GoMarble's Shopify integration is a different API surface — Shopify's Admin API for order/customer/product data — so GoMarble customers using Shopify for paid media analytics aren't on Storefront MCP and aren't affected by the UCP migration.
What's new in UCP vs Storefront MCP?
UCP extends the storefront primitives (catalog, cart, checkout) with first-class customer account operations, expanded analytics signals, and a portability layer that lets the same prompt work across Shopify and BigCommerce stores. It's the foundation for cross-platform agentic commerce.
Do I need to migrate manually?
If you integrated Shopify's Storefront MCP yourself, yes — update endpoint URLs, refresh OAuth scopes, and revalidate auth tokens before June 15. If you're using a different surface for Shopify (like Admin-API-based integrations), the Storefront MCP sunset doesn't affect you. Check which API surface your current integration uses.
Does UCP affect non-Shopify integrations?
Not directly — your Meta Ads, Google Ads, Klaviyo, or GA4 connectors aren't affected. But if your workflows reconcile Shopify orders against paid ad ROAS, the Shopify side of that pipeline needs to be on UCP by June 15.

Need Shopify data for paid media analysis?

GoMarble’s hosted MCP joins Shopify orders with Meta + Google + TikTok ad data via the Shopify Admin API — a separate surface from Storefront MCP. The UCP migration isn’t relevant to this use case.