One MCP connection lets agents search more than 1 billion products in Shopify Catalog, create carts, and complete checkout with Shop Pay. Search doesn't need an API key. Existing Catalog API integrations don't change, and you don't need to do anything.
Agents find products in Catalog, but payment sends shoppers to the store's website. Many shoppers drop off during this redirect.
Search → cart → checkout → Shop Pay payment → order tracking, all through a single MCP connection.
https://mcp.shop.com , and a skill description that MCP-compatible agents can read https://mcp.shop.com/skill.md.search_cataloglookup_catalogget_product
Reads Shopify Catalog.
Shoppers sign in just once. After that, search tools use their saved preferences.
Create a cart on the selling store → create a checkout. Complete it with complete_checkout; check its status with get_checkout.
search_orders
Finds orders and shipment tracking for signed-in shoppers.
| Feature | Not signed in | Signed in with Shop |
|---|---|---|
| Product search & details | Yes Works without credentials | Yes Uses saved preferences |
| Cart & checkout creation | Yes | Yes Can use saved addresses |
| Pay with Shop Pay | No | Yes Pays with saved Shop Pay details |
| Agent-completed purchase complete_checkout |
Not specified | Yes After the shopper reviews the total and payment method |
| Order and delivery tracking search_orders |
No | Yes |
| Item | Before | Shop MCP |
|---|---|---|
| Product discovery | Yes Search with Catalog | Yes Same Catalog (1B+ products) |
| Payment | Redirects out Sends shoppers to the store's site | In the agent Completed with Shop Pay |
| Drop-off risk | Redirects often cause drop-off | No redirect, fewer drop-off points |
| Connection method | Use the Catalog API directly | A single MCP connection (+ shop CLI) |
| Order handling | — | Appears as a regular order in the merchant's admin |
| Impact on existing integrations | None Existing integrations that use the Catalog API directly need no changes or action | |
Install the CLI and run shop search to see results in your terminal.
Have your coding agent read skill.md , ormcp.shop.com as an MCP server in your config.
Paying with Shop Pay requires the buyer to sign in. In your own code, use the device flow.
The checkout succeeds when it returns status: completed and an order.
# shop CLI をインストール(エージェントと同じサーバーを叩く)
npm install -g @shopify/shop
# 検索を試す(API キー不要)
shop search "ceramic coffee dripper"Which store the product belongs to
Selling price
Whether the item is in stock
Swap the query for products your agent handles to see the shape of the data your agent receives.
To get the checkout status, you need to poll get_checkout . Build retry intervals and timeouts into your design from the start.
complete_checkout should be called only after the buyer has confirmed the total and payment method. Always build a confirmation step into your UI or conversation flow.
MCP clients like Claude and ChatGPT handle this for you, but in your own code you need to implement the device flow. Carts and checkout work without sign-in, so you can roll it out in stages.
The pass criteria for E2E tests are explicit. Assert in your tests that the checkout returns status: completed and an order.
Orders placed through an agent show up in the merchant's Shopify admin like any other order.Merchants keep their existing fulfillment workflows as-is. Existing integrations that call the Catalog API directly don't need any changes, so migrating is optional and you can run both side by side.
mcp.shop.com to your agent as an MCP server. Build the flow: search → cart → checkout → Shop Sign-in → after confirmation, complete_checkout .get_checkout . Custom clients sign in using the device flow.npm install -g @shopify/shop → Run shop search with the products you plan to use, and check how stores, prices, and inventory are returned before designing.status: completed and order creation.