The read side is broad enough to answer questions about a store without opening the admin — orders filtered and sorted, products by collection, customers paginated. The write side is deliberately narrow: tag a customer, create a discount, build a draft order into a real one. That is the shape of a support or merchandising workflow, not a full store-management surface.
An MCP server over Shopify's GraphQL Admin API. The read tools cover products, variants, collections, customers, orders and shop settings; the write tools cover customer tags, discount codes, draft orders and webhook subscriptions.
- Products by search title, by collection or by ID, and variants by ID — get-products, get-products-by-collection, get-products-by-ids, get-variants-by-ids
- get-customers with pagination, and tag-customer to add tags to one
- get-orders with query filtering, a sort key and reverse ordering, plus get-order for a single order
- create-discount for a discount code — percentage or fixed amount, with a start date and a once-per-customer switch
- create-draft-order and complete-draft-order to build an order with line items and a shipping address, then turn it into a real one
- get-collections, get-shop and get-shop-details for the store's own structure and its shipping countries
- manage-webhook to subscribe, find or unsubscribe a webhook topic
A custom app created in your Shopify admin with read and write scopes for products, customers and orders, and the Admin API access token it issues. The store domain is supplied alongside it in your client config. Runs on Node.
One command plus a key — npx -y shopify-mcp-server, then supply credentials