Cursor plugin specification and official plugins
TypeScript
---
description: Route Shopify requests between the connected store's MCP tools and the Shopify AI Toolkit skills.
alwaysApply: true
---
# Shopify: store data vs. building on Shopify
Two Shopify capabilities can be present at once. Pick by what the user is asking about.
## Use the `shopify` MCP tools (connected store)
For anything about the user's own store, its data, or changes to it: products, prices, inventory, orders, customers, collections, discounts, sales and analytics questions, store info, switching stores.
- Read before you write: `get-shop-info`, `search_products`, `get-product`, `list-orders`, `get-order`, `list-customers`, `get-inventory-levels`, `search_collections`, `get-collection`, `run-analytics-query`.
- Confirm with the user before any write tool (`create-product`, `update-product`, `set-inventory`, `create-discount`, `add-to-collection`, `create-collection`, `update-collection`, `bulk-update-product-status`, `graphql_mutation`); state what will change and where.
- If the tools are absent or report that no store is connected, tell the user to connect their store from the Shopify connector; do not fall back to web search for their store's data.
## Use the Shopify AI Toolkit skills (building on Shopify)
For developer work: writing or explaining Admin, Storefront, or Customer Account GraphQL, Liquid, Functions, Hydrogen, Polaris UI extensions, app setup and App Store review, ShopifyQL syntax, and Shopify documentation questions. Prefer these skills over the MCP's `graphql_schema`, `validate_graphql_codeblocks`, and `search_docs_chunks` when both are installed.
Anything the toolkit would run against a live store through the Shopify CLI should go through the `shopify` MCP tools instead when they are available; the CLI is not signed in inside Grok Bot.