What changed
Shopify's October 13, 2026 developer changelog announced Shop MCP at mcp.shop.com, a public MCP service with 17 shopping tools spanning catalogue search, product lookup, carts, checkout, Shop account sign-in and order tracking. Search spans more than one billion listed products without an API key. Developers can configure any compatible agent or use Shopify's shop CLI. A signed-in shopper can use stored Shop Pay addresses and payment details, but the shopper must approve the total and payment method before the agent calls complete_checkout. Shopify also describes a non-Shopify-store path involving a buyer-approved single-use card.
Why it matters
Until now, many agents could discover products but had to hand buyers off to a separate checkout. A general-purpose agent now has a documented route to search, cart, purchase and post-purchase status without a bespoke platform partnership. For builders this changes the integration boundary and creates an opportunity to build specialist shopping assistants. For merchants, it moves more product discovery and transactions into external agent interfaces, increasing the importance of accurate catalogue data and clear checkout attribution. Shopify has not published independent conversion-lift evidence for this launch.
One endpoint covers discovery through purchase
The hosted mcp.shop.com service provides 17 tools. search_catalog, lookup_catalog and get_product handle product discovery; additional tools build carts, create and inspect checkout, complete authorised payment and retrieve order status. Search can run without credentials, while higher rate limits require an API key. The shop CLI uses the same server for local testing.
Shop account authentication is a buyer boundary
Shop sign-in enables saved sizes, preferences, shipping details and Shop Pay. Shopify says cart and checkout flows can also work without sign-in, but using stored payment credentials requires the shopper's authenticated session and explicit confirmation of the total and payment method. Developers should not confuse tool access with permission to charge a customer.
Non-Shopify checkout broadens the scope
Shopify's documentation says that for stores outside Shopify, a shopper can approve the purchase in Shop and the agent receives single-use card details for the merchant's own checkout. This is a separate payment path with operational and security implications; implementation details, merchant compatibility and reliability need further independent testing.
No webhooks at launch
Shopify explicitly says Shop MCP does not provide webhooks at launch. Integrators must poll get_checkout for completion status and handle retries and idempotency carefully. Completed orders on Shopify stores appear in the merchant's ordinary admin. An agent should not assume the first checkout response means payment settled.
Distinct from existing Shopify agent protocols
Shop MCP at mcp.shop.com is a consumer-shopping service combining catalogue and checkout. It is not the same as the Global Catalog MCP at catalog.shopify.com/api/ucp/mcp used for the November 2 migration away from legacy REST endpoints, and not the same as September's browser-embedded WebMCP checkout support or Meta-specific agentic storefront channel. Shopify says existing Catalog API integrations require no changes.