On this page
Shopify now documents two official Catalog MCP interfaces: Global Catalog searches products across Shopify merchants, while Storefront Catalog is scoped to one merchant. Both use Shopify’s Universal Commerce Protocol (UCP) catalog capability and expose tools for product search, lookup, and variant selection. The documented Catalog MCP interface is for product discovery; it does not expose Shopify Admin order or catalog-write operations.
On October 13, 2026, Shopify also announced Shop MCP, which adds carts, checkout, and signed-in order lookup through a separate MCP connection. That changes the agentic commerce picture, but it does not turn Catalog MCP itself into an Admin API editor.
Quick answer: Use Catalog MCP to discover products and select variants, with Global Catalog for cross-merchant search and Storefront Catalog for one store. Checkout and signed-in order lookup belong to separate commerce surfaces, including Shop MCP.
What Is Shopify Catalog MCP Functionality?
Catalog MCP is an official Shopify interface for AI agents to discover and retrieve product information. Global Catalog searches across eligible Shopify merchants; Storefront Catalog searches within one merchant’s store. Both implement Shopify’s UCP catalog capability and use the same three MCP tools, with scope and response fields varying by interface.
A typical flow is two steps. First, search_catalog finds products from a text query, image, or product identifiers; lookup_catalog resolves known product or variant IDs. Then get_product returns a chosen product’s details, available option combinations, and checkout links. This supports product discovery and variant selection without granting the agent broad Admin API access.
The separate @shopify/dev-mcp package serves Shopify developer documentation and tools. It is distinct from Catalog MCP and from Shop MCP, which adds cart, checkout, and signed-in order features.
How Shopify MCP Catalog Access Actually Works
The Protocol Layer: What MCP Actually Does
MCP defines how a client discovers and calls tools exposed by a server. UCP defines the commerce capability and the shape of catalog requests and responses. In Shopify’s current Catalog MCP, the agent sends a request to Shopify’s endpoint, includes the URL of its UCP agent profile, and receives the tools allowed by the capabilities declared in that profile. This is a hosted Shopify service; you do not have to build a custom MCP server merely to call the documented catalog tools.
The API Layer: Admin vs Storefront
Shopify documents two Catalog MCP endpoints:
- Global Catalog:
https://catalog.shopify.com/api/ucp/mcpsearches across Shopify merchants. - Storefront Catalog:
https://{storeDomain}/api/ucp/mcpsearches one merchant’s store.
Both require an agent profile and do not require an API key for standard requests. The tools return catalog discovery data; they are not a proxy for the Shopify Admin API. For product or order changes, a separate app or integration must use the appropriate Shopify APIs and permissions. Catalog access is rate-limited, search results and product images must not be cached, and some response attributes are labeled as inferred by Shopify and may be incomplete or vary in accuracy. Read Shopify’s Catalog documentation and usage guidelines before using results in a customer-facing experience.
| Capability | Global Catalog MCP | Storefront Catalog MCP |
|---|---|---|
| Product search | Across eligible Shopify merchants | Within one merchant’s catalog |
| Endpoint | https://catalog.shopify.com/api/ucp/mcp |
https://{storeDomain}/api/ucp/mcp |
| Standard authentication | Agent profile; no API key required | Agent profile; no API key required |
| Discovery tools | search_catalog, lookup_catalog, get_product |
The same three catalog tools |
| Lookup request limit | Up to 50 product or variant IDs | Up to 10 product or variant IDs |
| Product details | Options, availability signals, and checkout links | Store-scoped options, availability signals, and checkout links |
| Product, inventory, or order writes | Not exposed | Not exposed |
| Checkout execution | A separate checkout surface is required | A separate checkout surface is required |
What Shopify Catalog MCP Functionality Actually Supports
The documented Catalog MCP tools cover these tasks:
- Search by text: find products from a natural-language product request.
- Search by image or similar-product IDs: Global Catalog supports image queries and product IDs for similarity discovery.
- Filter discovery results: use supported filters such as availability, price, shipping destination or origin, and product attributes.
- Look up known IDs: retrieve current product or variant catalog data; one Global Catalog lookup can resolve up to 50 identifiers, while Storefront Catalog supports up to 10.
- Inspect a product:
get_productreturns full details for one product, including option combinations and availability signals. - Refine a variant choice: pass selected options, such as color or size, to find the matching variant and its checkout link.
- Search across or within a store: choose Global Catalog for cross-merchant discovery or Storefront Catalog for a single merchant’s product set.
These are discovery functions. The catalog tools do not update product prices, write metafields, adjust inventory, edit orders, or perform checkout.
What Catalog MCP Means for Post-Purchase Operations
Catalog MCP can help an agent find a product or inspect its listed options, but it does not read Shopify orders or perform post-purchase edits. Keep these responsibilities separate: use Shopify’s documented agent tools for product discovery, and use an order-management app or a properly scoped integration for order changes.
Revize’s customer order-editing app provides self-serve changes before fulfillment, inside a merchant-set editing window. The merchant chooses the available actions; the customer edits through the enabled Revize app block on the Shopify order status or thank-you page, or the Edit Order link in the confirmation email. Revize validates live inventory for variant swaps. A time window alone does not hold fulfillment; the merchant must configure the appropriate hold mode and rules. See the Shopify order-editing guide for the native order editor.
Agentic Commerce and Catalog MCP: What’s Real Today vs What’s Coming
Shopify’s current agent tools have distinct roles:
- Catalog MCP: product search, lookup, details, and variant discovery through Global or Storefront Catalog.
- Shop MCP: a separate MCP server announced October 13, 2026. It can search the catalog, build carts, create checkout on Shopify stores, complete Shop Pay checkout after the shopper confirms, and find orders for a signed-in shopper. At launch, order status is checked by polling
get_checkout; the release notes say webhooks are not available yet. - Shopify dev MCP: developer documentation and tooling, rather than merchant catalog or order-management actions.
For setup, follow Shopify’s current Catalog guide or Shop MCP release notes. Do not assume that a tool described for one server is available through another.
Implementation checklist
If you are evaluating Shopify Catalog MCP:
- Decide whether the agent needs cross-merchant search or one store’s catalog.
- Read the relevant endpoint and agent-profile setup instructions.
- Test search, lookup, and variant selection with real requests, including unavailable or ambiguous options.
- Respect rate limits and the rules against caching results and images.
- Keep product discovery, checkout, and post-purchase order editing assigned to the tools that explicitly support each task.
Frequently Asked Questions
Is Catalog MCP a specific Shopify product?
Yes. Shopify’s Global Catalog MCP searches across eligible merchants, and Storefront Catalog MCP is scoped to one merchant. The developer-focused @shopify/dev-mcp server is a separate product.
What is the Model Context Protocol, exactly?
MCP is a protocol that lets an AI client discover and call tools exposed by a server. In Shopify’s catalog implementation, UCP defines the commerce catalog capability and request/response format carried through MCP.
Do I need a developer to set up Shopify catalog MCP?
You need an MCP-compatible client and an agent profile, then configure the relevant Shopify Catalog endpoint. Shopify hosts the documented catalog server, so a custom MCP server is not required for these tools. More advanced agent behavior may require development work.
Which Shopify plans support catalog MCP?
The Catalog documentation describes endpoints and agent-profile authentication rather than a plan-tier matrix. Check Shopify’s current documentation and your store’s eligibility for the specific catalog or agentic feature you want to use.
Can MCP write to my Shopify catalog, or is it read-only?
No. Catalog MCP exposes product-discovery tools, not product-write or order-edit operations. Shop MCP is separate and adds cart, checkout, and signed-in order lookup. Admin API changes require a separately authorized app or integration.
How does catalog MCP differ from Shopify Flow?
Flow runs event-driven workflows in Shopify Admin. Catalog MCP lets an agent call product-discovery tools on demand. They can complement each other, but Catalog MCP does not itself trigger or execute a Flow workflow.
What Admin API scopes does catalog MCP require?
The hosted Catalog MCP endpoints use an agent profile and do not require an Admin API token or API key for standard requests. If your separate integration uses Admin API operations, request only the scopes needed for that integration.
Can catalog MCP handle Shopify B2B scenarios?
The Catalog MCP tools are documented for product discovery. They do not expose company assignments or a complete B2B order workflow. Verify current B2B catalog and pricing support in the API or agent capability you plan to use; do not assume Plus-only Admin API data is exposed through Catalog MCP.
What AI clients work with Shopify catalog MCP?
Use an MCP-compatible client that can connect to the relevant endpoint and supply an agent profile. Shopify’s October 13 Shop MCP release notes describe sign-in flows for MCP clients such as Claude and ChatGPT; support and behavior depend on the client.
Is there a performance cost to querying catalog data via MCP?
Shopify does not publish a fixed response-time guarantee for Catalog MCP in the cited documentation. Latency depends on the client, request, and service conditions. Respect rate limits and do not cache catalog search results.
How do I handle security for my Shopify catalog MCP server?
Use the required agent profile, keep your client configuration protected, follow Shopify’s no-cache and usage rules, and review what product information your agent displays. Catalog MCP does not use an Admin API token for standard requests; other integrations may have separate credentials and access controls.
Can I use catalog MCP for real-time storefront product recommendations?
Catalog MCP is designed for agent-led product discovery and variant selection. It returns product data and checkout links; Shopify does not document it as a low-latency storefront page API. For a custom storefront experience, choose the interface that fits the performance and presentation requirements.
Related reading
Shopify order-editing statistics · Shopify MCP and UCP endpoint guide · Universal Commerce Protocol developer guide · Shopify AI Toolkit guide · Shopify order management guide · Shopify customer cancellation guide · How to sell on ChatGPT with Shopify agentic storefronts · Shopify Functions migration tutorial · How to let customers edit Shopify orders