Hi, I am using Storefront MCP server in my app, which is on production. I am using search_shop_catalog tool heavily to query about products. Looks like yesterday, this tool was renamed to search_catalog and the response format is also changed. This broke my production workflow. How can i ensure that I am aware of such breaking changes in advance?
1 Like
I want to jump in here to show you are not the only one impacted. This is extremely frustrating that no warning was provided and we are working on a weekend now to get back to parity.
1 Like
We are facing the same issue. Are there any recommendations around it?
We are facing similar issue. Secondly the search_shop_policies_and_faqs isn’t working as expected though.
We ran into the same issue - search_shop_catalog is no longer available. It appears to have been replaced by an undocumented search_catalog tool, which uses a completely different input/output schema. The old tool name now returns a “Tool not found” error.
The same issue occurred in my production app as well. If you’re experiencing this too, please reply with “Same” so we can gauge its impact across the community.
same same - back from holidays with plans for testing - in the bin
policy search seems fine
product search isn’t
we can rewrite that part (massive gaps also here Shopify so hoping for some good changes)
but need some clarity around changes
not usual route to introduce breaking changes
Ok so it took us like an hour to change this tool + now we need to re-test a bunch of stuff
It looks like a positive change (more products / not having to do price filters post fetch) - some of our enrichment passes now are redundant / just there for backup now.
But anyone @GovRayt - it’s really annoying when things change without proper documentation - you could have left the old tool in and introduced the new one.
Same for us too, undocumented breaking change with the search_shop_catalog tool, impacting our production environment 
any news?
Same here. Not happy with this unannounced change! Without any input from Shopify it’s impossible to know if this was intentional or a mistake that’ll be rolled back in a few hours/days.
yeah its 100% not cool to break things
but tbh new tool is MUCH better - like you can fetch 250 products + pass in context of location
before we were having to do an enrichment pass to get translations / currency / media etc and like 10 at a time (often with false positives that need to be filtered out so you end up with 7)
I haven’t tested everything yet but just upping those limits and not having to do extra enrichment queries is great
it will shave quite a bit of time off what we’re doing
Hi @Joe_Dempsey, how are you passing min/max prices to the new endpoint? I’ve tried a few different combinations but nothing seems to filter the products.
{
"jsonrpc": "2.0",
"method": "tools/call",
"id": 1,
"params": {
"name": "search_catalog",
"arguments": {
"catalog": {
"query": "yoga",
"filters": {
"price": {
"max": 2000
}
},
"pagination": {
"limit": 5
}
}
}
}
}
@Simon_J 
Claude code figured out the finer details for me
that works
Seemingly price filter uses the store’s base currency (minor units). max: 2000 = £20.00 for a GBP store.
When you pass context.currency, the filter appears to be ignored — products are returned at converted prices but not filtered by converted amount.
I haven’t tested any of this - just got the products rendering again
which is what we need for current planned testing
I’ll deal with all the proper details of the update next week & hopefully some docs then
previously we we’re doing price filter post fetch
Thanks @Joe_Dempsey. That worked. Tag searches in the query still work too so that’s a plus!
e.g.
{
"jsonrpc": "2.0",
"method": "tools/call",
"id": 1,
"params": {
"name": "search_catalog",
"arguments": {
"catalog": {
"query": "yoga tag:yoga-hot -tag:yoga-kundalini",
"filters": {
"price": {
"max": 2000
}
},
"pagination": {
"limit": 5
}
}
}
}
}
We’re also affected. Our production storefront AI agent broke when search_shop_catalog was renamed to search_catalog with a new input schema. We’ve adapted our code, but the official docs at shopify.dev still reference the old tool name. Would appreciate an official response on whether this change is permanent so we can confidently ship to production.
Same issue here, this is so frustrating! The lack of documentation on this is crazy. I’m also noticing that using the input format that tools/list gives for search_catalog returns no results.
no results:
{
"jsonrpc": "2.0",
"method": "tools/call",
"id": 1,
"params": {
"name": "search_catalog",
"arguments": {
"catalog": {
"query": "blue shirts",
"context": {
"intent": "customer looking for clothing"
}
}
}
}
}
results sending the arguments like we were for search_shopify_catalog:
{
"jsonrpc": "2.0",
"method": "tools/call",
"id": 1,
"params": {
"name": "search_catalog",
"arguments": {
"query": "blue shirts",
"context": "customer looking for clothing"
}
}
}
@Claire_Muller what domain are you using
let me call it with our code
I think with MCP it’s supposed to be more like self documenting with the input schema tool list response but there should be docs
total pain in the ass
I guess what we all need to do is setup some kind of automated daily tool check
@Joe_Dempsey that can be fine for schema changes, but it shouldn’t apply to renaming the tool itself
Hey everyone, we just put a changelog to this effect, you can now safely move to the UCP-shaped tools Storefront Catalog MCP now implements UCP - Shopify developer changelog
We’re sorry for the disruption to the existing tools. As mentioned in the changelog, for catalog-type queries, you have until June 15th to migrate to /api/ucp/mcp.
thanks @Mathieu_Perreault
Quick questions on the roadmap. On our end the Storefront MCP has taken breaking changes with no notice:
-
search_shop_catalog→search_catalog(tool rename + UCP response shape — caused a outage) -
Addition of the
ucp-agent.profilediscovery handshake -
Endpoint moving from
/api/mcp→/api/ucp/mcp, with/api/mcpdeprecated June 15 2026 (fine timeframe)
A few things that would really help us plan and build better:
-
Pipeline visibility — is there a public roadmap / changelog for Storefront MCP? Advance notice of upcoming tools, deprecations, schema changes, and required metadata would let us plan (e.g. if I’d known some of this was soon available I wouldn’t spend time building an enrichment pass to get missing data > instead spend time on more useful things)
-
Specifically: will
update_cart,get_cart, andsearch_shop_policies_and_faqsalso move to UCP //api/ucp/mcp, get renamed, or change schemas? Timeline? -
A direct feedback channel — so we can report issues or ask for capabilities. These updates actually solve quite a few notable problems we had to solve with enrichment passes to the api but e.g. we’re still going to need that to e.g. get inventory. if inventory will be there soon we can probably ditch the entire enrichment pass. Will there be a tool for querying pages? that would be great since a lot of important info/context sits there like size guides / about etc
additional question: After June 15 2026 when /api/mcp is deprecated, what’s the intended flow for password-protected stores? Is there a supported way to authenticate past the password wall