Shopify UCP Cart MCP is now the path Shopify wants AI agents to take through a cart, and the old one has a date on it. On June 24, 2026 Shopify began deprecating the Storefront MCP cart tools in favor of UCP Cart MCP, with the legacy tools maintained only until August 31, 2026. For a studio building headless Shopify Plus storefronts and AI-native interfaces, this is the moment agentic checkout stopped being a demo and became the supported default.
What changed
Shopify is retiring the get_cart and update_cart tools on its Storefront MCP server and replacing them with UCP Cart MCP. The June 24, 2026 changelog entry moves cart operations from the old endpoint at /api/mcp to a new UCP endpoint at /api/ucp/mcp, which implements the UCP cart capability versioned 2026-04-08. The new server exposes four tools where the old one had two: create_cart, get_cart, update_cart and cancel_cart. The deprecated tools keep working until August 31, 2026, so there is a runway, but the documentation has already shifted to the new ones. Two mechanics deserve attention now. update_cart uses PUT semantics, meaning each request replaces the cart's full state and you must send the complete line_items array rather than a partial patch. And cancel_cart requires an idempotency key as a UUID, with an agent profile passed in a meta object on every call.
Storefront MCP vs UCP Cart MCP, compared
The difference is scope: Storefront MCP was a Shopify-specific way for an assistant to read and edit a cart, while UCP Cart MCP is Shopify's implementation of an open, cross-platform standard for agent checkout. UCP, the Universal Commerce Protocol, is an open standard Shopify co-developed with Google to define how AI agents transact with merchants across cart, checkout, payment and post-purchase, independent of platform or payment processor, per Shopify's UCP overview. The practical upgrades over the old tools are concrete. The cart lifecycle is now complete, with create and cancel as first-class operations rather than side effects. State handling is explicit through PUT semantics, so an agent cannot half-update a cart and leave it inconsistent. And access changed: building on Shopify's agent layer used to need approval, but now a developer registers an agent profile in the Developer Dashboard and calls a public MCP endpoint, per Shopify's agents documentation. The standard also has weight behind it, with stated support from Amazon, Meta, Microsoft, Salesforce and Stripe. That is the signal that matters. This is not one vendor's cart API, it is the shape agent commerce is settling into.
Why it matters for premium studios in Asia
For a premium studio this turns AI shopping agents from a roadmap line into a surface you have to design for now. A high-craft storefront in Jakarta or Singapore has spent years tuning what a human sees and touches: the motion, the product configurator, the checkout speed on a mid-range Android over an uneven network. Agentic commerce adds a second audience that never sees any of it. When an AI agent builds a cart through UCP Cart MCP, your visual craft is bypassed and what represents the brand is your catalog data, your structured product information and the correctness of your cart logic. That is a real shift in where quality lives. A team that treated product data as a CMS afterthought now has a second buyer reading it directly. This sits at the intersection of the two disciplines we care about most, headless Shopify Plus commerce and AI-native interfaces, and it rewards teams that already keep cart and catalog logic clean and well typed rather than buried in theme code.
What we would change this quarter
Audit any agent or assistant integration touching the Storefront MCP cart tools and schedule the move to UCP Cart MCP before August 31, 2026. If you shipped anything against get_cart or update_cart on the old /api/mcp endpoint, it has a known expiry, so put the migration on this quarter's board, not next. The PUT semantics are the part most likely to bite. Code that sent partial cart updates against the old tools will silently wipe line items against the new one unless you send the full line_items array, so rewrite those calls deliberately and test with multi-item carts. Beyond the fix, treat this as a prompt to audit your product data as if an agent were the reader, because one now is. Clean titles, accurate variants, structured specs and honest inventory are what an agent quotes back to a buyer, and they are cheaper to fix before a botched agent cart than after. If you are scoping a headless checkout build this quarter, design the cart layer to speak UCP from the first commit rather than wrapping legacy tools you would only have to replace. The honest framing for clients is that agentic checkout is no longer optional surface area. Shopify just gave it a public endpoint, an open standard and a deprecation date, and the merchants who win the agent channel will be the ones whose data was ready for it.