The MCP tools for product catalogs are search_catalog / lookup_catalog / get_product — reorganized into these three. The call targets now point to /api/ucp/mcp . The old tools remain available until June 15, 2026, then will be removed.
Used the previous search and lookup tools, with request/response formats on the old spec. Maintained until June 15, 2026, then removed.
search_catalog / lookup_catalog / get_product — reorganized. The call target moves to /api/ucp/mcp. The formats are also updated to match UCP.
search_catalogSearch a store's product catalog.Filtering, pagination, and buyer contextare supported.
lookup_catalogLook up products and variants by identifierin batch. Supports inputs correlation.
get_productA product'sfull detailsretrieved. Includes interactive variant selection, availability signals, and more.
| Tool | Role | Features stated in the article |
|---|---|---|
search_catalog |
Catalog search | Filtering / pagination / buyer context |
lookup_catalog |
Bulk retrieval by identifier | Batch lookup of products and variants / inputs correlation |
get_product |
Retrieve details for a single product | Variant selection / availability signals / more |
https://{storedomain}/api/ucp/mcp .{storedomain} should be replaced with your own store domain. As for the specific path of the old endpoint,not stated in the article.What you need to do if you're building with Storefront MCP tools (from the article's "What you should do").
search_catalog / lookup_catalog / get_product with one of the following.
Change the call target to https://{storedomain}/api/ucp/mcp .
Review the new request/response schemas for all tool calls and update your app to match.
This post (the Developer Changelog) states that the Storefront Catalog catalog tools "implement UCP" , and that the request/response shapes are updated "to match UCP" , as the post describes.
The full name and definition of the acronym UCP itself are not given in this post. Avoid guessing; confirm the exact definition and specification in the official documentation. On this page we treat it as "the new specification that the catalog tools conform to."
buyer context / inputs correlation / availability signals such terms are mentioned by name in the post, but their specific field specifications are not described. Confirm them in the schema documentation before implementing.The old tools are maintained until this date and then deprecated. This is an Action Required breaking change, so live apps need a migration plan in place by the deadline.
From the old search/lookup tools to search_catalog / lookup_catalog / get_product . Rewrite every tool reference on the MCP client side.
Calls are consolidated to /api/ucp/mcp . Externalizing it as a base URL or environment variable makes migration and rollback easier.
The request/response shape itselfchanges to become UCP-compliant. Estimate on the assumption that parsers, type definitions, and validation will all need updating.
Feature names like buyer context, inputs correlation, and availability signals are tied to the new tools, butthe definition of UCP and the detailed specification of each field are not described in this post. Be sure to check the Storefront Catalog MCP schema documentation before implementing.
search_catalog Rename toget_product , change the endpoint to /api/ucp/mcp , and remap the response to match the new schema.lookup_catalog batch retrievallookup_catalog 's batch identifier lookup, and useinputs correlation to correlate the entered identifiers with the returned results.get_product 's inventory signalsget_product 's interactive variant selection and availability signals to suppress and gray out out-of-stock variants.get_product 's new response. Switch the display logic to be driven by inventory signals.search_catalog / lookup_catalog / get_product 's three tools, plus the/api/ucp/mcp endpoint— migration is required.