Shopify Storefront MCP cart tools end Aug 31: move to UCP

If you built a shopping assistant against Shopify's Storefront MCP cart tools, maintenance ends tomorrow — August 31, 2026. Shopify announced the deprecation back on June 24 and pointed everyone at the UCP-conforming Cart MCP server instead. This is not a rename. The endpoint moved, the request shape changed, and update_cart now has PUT semantics, which means a naive port will quietly wipe carts.

What actually happened

Per Shopify's developer changelog, the deprecated tools are get_cart and update_cart on the Storefront MCP server at https://{shop}.myshopify.com/api/mcp. The replacement lives at https://{shop-domain}/api/ucp/mcp and exposes create_cart, get_cart, update_cart, and cancel_cart, implementing the UCP cart capability.

Three changes that will break a lazy migration:

• update_cart is now PUT, not PATCH. You send the complete line_items array on every request. Send a partial array and you have not added a line — you have replaced the cart with one line. This is the one that bites.
• Requests need a meta object carrying ucp-agent.profile. Omit it and you are not a conforming client.
• cancel_cart requires meta["idempotency-key"]. Retries against a cancel endpoint without one are exactly the bug you do not want in a checkout path.

The context: Shopify switched on WebMCP tools across every Liquid storefront on August 5, plus the Hydrogen developer preview. Nothing to install, nothing to configure. Agents can search the catalog, manage the shopper's cart, hit checkout, and search shop policies. WebMCP itself is still an origin trial limited to Chromium browsers — early, but live on your store whether or not you noticed.

Why the Shopify MCP migration matters for your store

Two separate jobs here, and merchants keep conflating them.

If you build agent-facing integrations — a custom assistant, a marketplace connector, a concierge bot on a headless build — this is a dated migration with a real deadline and a silent failure mode. Test the PUT semantics against a scratch store today. A cart that empties itself is not a 500; it is a conversion loss you find in a support ticket three weeks later.

If you just run a Shopify store, the deadline is not your problem, but the August 5 change is. Your storefront now exposes tools an AI shopping agent can call, and the answers those tools return come from your product data and your shop policies. The catalog tools read through the Storefront API. The policy tools read your actual policy pages. Whatever is in there — thin descriptions, a shipping policy last edited in 2023, missing variant details — is now what an agent tells a shopper on your behalf.

That is the work worth doing this week. Not the migration; the merchandising. Structured, complete product data was already the thing separating stores that convert AI traffic from stores that get scraped and skipped. Shopify just made it addressable by default.

And note the pattern for planning purposes: the cart tools got roughly ten weeks from deprecation notice to end of maintenance. That is the window you should assume for anything in the agentic commerce stack right now. Protocols at this stage move faster than your roadmap does. Keep the integration layer thin enough to swap.

Sources: Shopify developer changelog — Storefront MCP cart tools deprecation, Shopify developer changelog — WebMCP support for Liquid and Hydrogen storefronts.