Shopify Storefront MCP (Official)
shopify-mcp-official
Shopify's official hosted Storefront MCP, exposed at {store}.myshopify.com/api/mcp with no authentication. Buyer-facing: search the catalog, fetch product details, build/update a cart, and answer policy and FAQ questions. No admin or write-to-store operations.
When to use
Building a shopping agent that searches a Shopify store's catalog, retrieves product details, and assembles a cart toward checkout.
When not to use
You need admin operations (create products, manage inventory, fulfil orders) — the Storefront MCP is buyer-only and cannot write store data.
Premium · managed ✦
We run it in production for you — idempotent writes, automatic retries, full visibility.
Run it for me →What you need to integrate
Authentication
none · documented
Requirements
- Rate limits: undocumented
- Tool-definition budget: 2,250 tok
Setup checklist
- No authentication required.
- Set environment variables: SHOPIFY_STORE_DOMAIN.
Env: SHOPIFY_STORE_DOMAIN
Docs & known issues
Evaluation
Verified non-idempotent: two identical update_cart calls created two distinct carts (different cart gids) — duplicate-on-retry risk for cart creation.
Works with
- ✓ShipStation MCP Server (v2)— Order-to-fulfillment handoff: Shopify provided the order and address, ShipStation returned rates and created a label. No tool-name collisions. Claude correctly used Shopify for order lookup and ShipStation for shipping in sequence.
- –
- –
- –
- –
- –
- ✓Stripe MCP Server (Official, Hosted)— Ran a storefront + payments flow: Shopify created the order and Stripe took payment with test card 4242. No tool-name collisions; combined tool manifest stayed within a comfortable context budget and Claude routed each step to the correct server.
See the full compatibility list.