News

Shopify Opens Its Checkout to Browser Agents Through WebMCP

Agentic Commerce Atlas · · Updated

Good for: Leaders · Builders

On 28 September 2026 Shopify added WebMCP support for checkout, letting browser agents read and update an eligible Shopify checkout and submit it once the buyer has confirmed the order. The four checkout tools run inside Shopify’s checkout page, use the same state as the checkout the buyer sees, and, in Shopify’s words, “don’t expose a new API or require merchant configuration.” Shopify’s documentation says Checkout WebMCP implements the UCP checkout capability in the buyer’s browser, and that agent support for WebMCP is currently limited to Chromium-based browsers.

What Shopify shipped on 28 September

WebMCP is a proposed web standard under which a page registers tools with the browser, and an agent calls them with structured inputs instead of reading page code and simulating clicks. Shopify already provides WebMCP tools for storefronts and carts on every Liquid storefront. The changelog extends them to checkout with four tools:

  • navigate_to_storefront returns the agent to the storefront;
  • get_checkout reads checkout state, messages and, after completion, order details;
  • update_checkout changes supported fields without placing an order;
  • complete_checkout submits the checkout after the buyer confirms.

According to the documentation, update_checkout covers contact details and shipping address, delivery options or pickup locations, discount codes and store credit. On payment, the buyer chooses a saved Shop Pay card or a different billing address; Shopify says Checkout WebMCP does not accept new card details. When the buyer’s own input is needed, such as 3D Secure authentication, Shop Pay login or a blocking checkout UI extension, the tools hand control back and the buyer finishes the step on the checkout page in the same tab.

On the agent side, Shopify requires browser requests to be signed with Web Bot Auth, and says it verifies only keys that agents have registered, with their key directory published to Shopify.

How Shopify keeps the buyer in control of a WebMCP checkout

The documentation sets explicit rules for agents. Before calling complete_checkout, an agent must “show the buyer the current order and total, and get their permission to place it.” A signed request is not permission: Shopify says Web Bot Auth and the ready_for_complete status “don’t grant it.” If the total changes, the agent must ask again, and only a status: completed response confirms the order.

Which Shopify checkouts the tools do not cover

Checkout registers the tools only on eligible checkouts. Shopify lists these exclusions, where the agent should ask the buyer to complete the purchase on the checkout page:

  • the standard three-page checkout, unless the buyer checks out with Shop Pay;
  • B2B checkout;
  • embedded checkout, and checkouts in mobile checkout SDKs;
  • checkouts with merchandise from another shop;
  • draft orders, order edits and payment collection.

Why Checkout WebMCP matters for UCP and Shopify merchants

Shopify says Checkout WebMCP implements the UCP checkout capability (dev.ucp.shopping.checkout) over browser-registered tools instead of server-side JSON-RPC, and that it shares the checkout object, statuses and messages with its server-side Checkout MCP. A browser agent and a server-side agent therefore work with the same UCP checkout model. Shopify still recommends Checkout MCP, and says Checkout WebMCP is for agents already operating in the buyer’s browser.

For merchants, the tools arrive without setup on eligible checkouts. For agent builders, the requirements are concrete: a registered Web Bot Auth key, a Chromium-based browser, and an explicit buyer confirmation of the order and total before submission. WebMCP itself remains a proposed standard, and Cloudflare opened its own WebMCP developer preview in August.

See also UCP explained, MCP explained, AI shopping agent payment authorization, and the agentic commerce timeline.

Frequently asked questions

What did Shopify release on 28 September 2026?

WebMCP support for checkout. Four tools, navigate_to_storefront, get_checkout, update_checkout and complete_checkout, let a browser agent read the active checkout in the buyer's browser session, update supported fields and submit the checkout after the buyer confirms. Shopify says the tools add no new API and need no merchant configuration.

Can an agent place a Shopify order without asking the buyer?

Shopify's documentation says no. Before calling complete_checkout the agent must show the buyer the current order and total and get their permission to place it. A signed Web Bot Auth request and a ready_for_complete status do not count as that permission, and if the total changes the agent must ask again.

Which Shopify checkouts are excluded?

Shopify lists B2B checkout; embedded checkout and checkouts in mobile checkout SDKs; checkouts with merchandise from another shop; draft orders, order edits and payment collection; and the standard three-page checkout unless the buyer checks out with Shop Pay. For these, the agent asks the buyer to finish on the checkout page.

How does Checkout WebMCP relate to UCP?

Shopify says Checkout WebMCP implements the UCP checkout capability (dev.ucp.shopping.checkout) and that it and the server-side Checkout MCP use the same checkout object. Shopify recommends Checkout MCP and says to use Checkout WebMCP only when the agent is already operating in the buyer's browser.

Primary sources

  1. WebMCP support for checkout - Shopify developer changelog · Shopify, 2026-09-28
  2. Checkout WebMCP · Shopify
  3. Carts and checkout for agents · Shopify
  4. WebMCP tools · Shopify