Hi everyone,
since around April 17th, our Shopify Storefront MCP Data Connector ("Search shop catalog") has been completely broken. Every call returns:
"Tool not found: search_shop_catalog"
Background:
Shopify renamed the Storefront MCP tool from search_shop_catalog to search_catalog as part of their UCP migration. The old tool is being deprecated (deadline June 15, 2026), but on some stores it has already been disabled — including ours.
What I tried:
1. Followed Intercom Support's recommendation: deleted the tool and re-added it. Intercom now correctly detects the new search_catalog. ✅
2. But when calling it, I get a different error:
"Invalid arguments: The property '#/meta' of type string did not match the following type: object [...] '#/catalog' of type string did not match the following type: object"
This means: Shopify's new UCP-compliant tool expects meta and catalog as JSON objects, but Intercom serializes them as JSON strings. The result is rejected by schema validation.
I tested the same with a Custom MCP Connector — same error. So this is not a template issue, it's a deeper bug in Intercom's MCP adapter for UCP-compliant tools.
Side effect:
By following the support team's advice to delete and recreate the connector, I lost my entire carefully crafted configuration — description, input parameters, custom Python data transformation, audience settings, etc. Multiple weeks of work.
Questions to the community:
- Is anyone else seeing this issue?
- Has anyone found a workaround for the string-vs-object problem?
- Has anyone managed to get search_catalog to work via Intercom's MCP connector at all?
I have an open ticket with Intercom Support. Will update here once there's progress.
Thanks!