Skip to main content
If your agent already calls Shop MCP, it can search Channel3 too. Our catalog uses the same tool names, the same catalog arguments, and the same UCP response shape, so the client code you already have works against both.

The one-line change

Send the same request you send to Shop, with the same headers and body, to a different URL:
search_catalog, lookup_catalog, and get_product take the same catalog arguments as on Shop. Responses follow UCP 2026-08-25: money in minor units, pagination.cursor, messages[], and variants[].seller. MCP hosts such as Claude, ChatGPT, and Claude Code connect with the URL alone.
Don’t send your Shop access token to Channel3. Use a Channel3 API key in x-api-key for Token-tier limits and buy links that credit your account. With no key, calls run on the Anonymous tier.

Run both side by side

Send each search to both URLs and merge the results. Remember which server each product came from:
  • Products from Shop go on to Shop’s cart and checkout tools as usual.
  • Products from Channel3 have no cart or checkout tools. Send the buyer to variants[].url, which opens the store’s product page.
Product and variant IDs belong to the server that returned them. Don’t pass a Channel3 ID to Shop, or a gid://shopify/... ID to Channel3.

What’s different

Filters and context

Anything Channel3 can’t apply, such as an unsupported filter or attribute value, an unserved market, or a third like entry, comes back as a warning in messages[] with the path of the input. Results are never narrowed by a filter that wasn’t applied. Channel3 adds fields of its own, such as website_ids and brand_ids filters and commission placement data. See the Extension reference.