Shopping MCP Servers for AI Agents: Four Options Compared
An AI shopping agent needs product data it can query, not just a list of stores to browse. A shopping MCP server lets an agent call a product-search tool while it is helping a person. The useful question is not which server has the longest tool list. It is whether the server covers the products the person wants and gives the agent a clear path from a result to a real store.
This comparison uses each provider's published documentation as of October 25, 2026. Catalogs, access rules and features can change. None of the four services below should be assumed to have every product on the web or a guaranteed final price.
Which shopping MCP server fits?
| If your agent needs... | Consider | Why |
|---|---|---|
| Product discovery across curated independent online stores | Shop Nobi | Its public, read-only `search_products` tool returns products with store links; no Nobi account or API key is needed. |
| Discovery across Shopify merchants, plus product and variant lookup | Shopify Global Catalog | Shopify documents `search_catalog`, `lookup_catalog` and `get_product` for its catalog. |
| Broad retailer offers and price history for an identified product | ShopSavvy | Its published tools include product search, retailer offers and price history. |
| Inventory from participating independent luxury boutiques | within | Its boutique-focused server publishes product search and additional shelf and visual-search tools. |
These are different product scopes, not a ranking by search quality. We have not run a controlled relevance or freshness benchmark across them. Shop Nobi is the Nobi product, so use the linked source pages to check our claims against each alternative.
Shop Nobi: curated cross-store search
Shop Nobi's online search engine exposes six public MCP tools. `search_products` takes a plain-language product request and returns matching listings; seller, price, stock signal, image and click-through link are included when available. `find_shop_nobi_page` looks for an existing Shop Nobi page on an exact topic. `get_product_details` reads descriptions and variant choices; `compare_products` compares catalog listings; `check_price_and_availability` checks their catalog price and stock; `find_alternatives` finds similar listings. These tools currently search products, not services or other offerings. The connection is remote, read-only and requires no Nobi sign-in or key.
It fits an agent helping someone discover products from curated independent stores and then sending that person to the merchant. It does not provide a generic REST catalog API, a complete cross-retailer price-history feed, cart creation or checkout. Price and availability can lag behind the merchant, so the store page is the final place to verify a purchase. Some product links may earn Nobi a commission; the agent should keep any returned commission notice next to the relevant link.
When sending a Shopify product or variant ID, include the selling merchant's domain as `storeDomain`, such as `example.com`. Use `sourceProductId` for a Shopify product and `sourceVariantId` for a Shopify variant only when the live `tools/list` schema supports them. A known Nobi `merchantId` can supply equivalent merchant context. Never put Shopify IDs or SKUs into Nobi `id`, `productId` or `variantId` fields. If the schema accepts only `id`, use the Nobi variant ID returned by search.
Shopify Global Catalog: Shopify product and variant workflow
Shopify's catalog documentation distinguishes Global Catalog, covering Shopify merchants, from Storefront Catalog, scoped to one store. Its tools support search, lookup by identifier and fuller product and variant details. Shopify documents an agent profile and rate-limit rules; an anonymous experiment is different from production integration. Choose this path if Shopify coverage and variant detail are central to the app.
ShopSavvy: offers and price history
ShopSavvy's agent documentation describes a public shopping MCP server with search, retailer-offer and price-history tools. That is a better feature fit when the shopper already knows a product and wants to compare offers or past prices. Its published free, no-key tier has request limits; check its current terms before building production traffic on it.
within: boutique inventory
within's agent documentation describes a public, read-only server for participating independent luxury boutiques, including shelf and visual search. That narrow inventory focus can be useful when a shopper wants boutique fashion. Coverage is limited to participating shops, so check the available locations and products before promising a result.
A practical way to choose
Start with three real shopper requests that matter to your app: a broad discovery request, a specific product, and one request with a hard constraint such as size or budget. For each server, record whether it returns useful products, whether the result identifies the seller, what stock and price evidence it supplies, and whether the shopper can reach the actual merchant. Keep connection checks and your own test calls separate from genuine shopper use.
If curated independent-store discovery is the fit, connect Shop Nobi and try a real product request. If the app needs raw catalog ingestion, historical prices or agent checkout, choose a service that explicitly documents those capabilities. Our product-search API guide explains that choice in more detail.