Shopify Claude Connector: The Complete Guide

A Shopify MCP server implements the Model Context Protocol to connect AI agents like Claude to Shopify. Shopify has moved aggressively here: by its Winter '26 Editions it had shipped four official MCP servers across multiple releases starting in Summer '25, making it one of the first major ecommerce platforms to embrace the protocol at this scale.

For merchants and developers alike, that means Claude can become an operator of the store - taking real actions and reading real data - rather than just an advisor about it.

Shopify is the world's leading commerce platform for independent businesses, powering millions of stores. It provides everything needed to sell online and in person - product and inventory management, checkout and payments, themes and storefronts, analytics and a vast app ecosystem. Its Hydrogen framework and Oxygen hosting let developers build custom, high-performance storefronts.

That breadth - and the sheer volume of routine store-management tasks - is exactly what makes an AI connector so useful for Shopify merchants.

Through the connector, Claude can operate across store management and analytics:

• Product management: create new products, update or delete existing listings, generate optimised descriptions, set collections and configure variant options.
• Order operations: create new orders, associate them with customers, and streamline fulfilment.
• Collection organisation: create custom collections and add or remove products to keep categories tidy.
• Business analytics: extract insights in natural language - customer lifetime value, "hidden gem" products with high repeat-purchase rates, and line-item fulfilment delays.

• Bulk product work: generate optimised descriptions and configure variants across many products from a specification.
• Catalogue tidy-up: reorganise collections and fix inconsistent categorisation in one pass.
• Order handling: create and fulfil orders, reducing manual entry.
• Merchandising insight: ask which products quietly drive repeat purchases, or where fulfilment is lagging - and act on the answer.
• Theme and store development: developers use it to build custom themes and integrations faster.

Beyond back-office operations, Shopify's Storefront MCP powers customer-facing AI experiences. With the Winter 2026 Edition it shipped inside Hydrogen 2026.1.4, turning every Hydrogen storefront on Oxygen into an AI agent endpoint by default. In practice, that means the same protocol that lets you manage your store can also power AI shopping assistants for your customers - a significant step toward agent-native commerce.

Coverage from commerce and developer communities (Polar Analytics, Ask Phill, Rewarx and others) has been enthusiastic, framing Shopify's MCP rollout as one of the most serious commitments to agent-native commerce by a major platform. The most cited practical win for developers is speed: building custom themes, many report around a 45% reduction in development time compared with manual coding.

Merchants, meanwhile, highlight the analytics: being able to ask plain-English questions about lifetime value, repeat-purchase "hidden gems" and fulfilment delays - and get actionable answers - lowers the barrier to data-driven decisions. As always with write-capable connectors, the advice is to scope permissions and review actions, especially around orders and product deletions.

Shopify open-sourced its AI Toolkit (MIT licence) in April 2026. The most common starting point is the developer MCP, which gives Claude documentation search and live GraphQL schema introspection - exactly what you want when building themes or apps. Add it to Claude Code with a single stdio command:

claude mcp add --transport stdio shopify-dev-mcp -- npx -y @shopify/dev-mcp@latest

That exposes seven tools spanning the Admin API surface, the docs, and the GraphQL schemas - no store credentials required for documentation and schema work.

Connecting to a live store

To take real actions you need a store-scoped token. Create a custom app in your Shopify Partner dashboard, grant only the scopes the task needs, and authenticate. The Shopify CLI handles the OAuth flow:

shopify auth login

Store the resulting credentials in environment variables, never in the prompt or a committed file. Begin with read and analytics scopes to build confidence, then layer in write scopes once you trust the behaviour. Shopify's AI Toolkit documentation covers the equivalent setup for Cursor and VS Code.

The connector can change your live store - create and delete products, create orders - so permissioning matters. Grant the minimum scope a task needs, begin with read-only analytics, and review actions that affect orders, inventory or customer data. For customer-facing Storefront MCP deployments, treat the agent endpoint with the same care as any public surface.

• A scope grants more than you expected: write_products grants all product writes, including delete. Shopify's scopes are coarse, so audit exactly what each one allows before approving an app and prefer the narrowest read scope that still does the job.
• Tools don't appear after adding the server: the stdio server runs via npx, so Node must be on the PATH Claude uses. If npx isn't found, install Node or point the command at an absolute path.
• GraphQL queries fail against your store: the dev MCP introspects the schema for your API version. A query that works in docs can fail if your store is pinned to an older Admin API version - check the version your app targets.
• Writes hit the wrong store: if you manage multiple stores, the active CLI session determines the target. Confirm with shopify auth login which store you are authenticated against before running write actions.
• Plan-gated features return nothing: some objects and reports depend on your Shopify plan. An empty analytics answer can mean the feature isn't on your tier.
• Credentials leaking into context: never paste tokens into the chat. Keep them in environment variables so they are never part of a prompt Claude sends upstream.

The AI Toolkit and the MCP servers are free and open-source under the MIT licence - there is no Shopify charge to connect Claude. What you pay for is your underlying Shopify plan, which governs which objects, reports and storefront features are available. The Storefront MCP ships inside Hydrogen on Oxygen, so customer-facing AI endpoints come with your existing Hydrogen hosting rather than a separate product.

On the Claude side, the developer MCP works with any Claude Code access; the one-click store connector path follows Anthropic's normal plan requirements. Underlying Admin API rate limits still apply, so high-volume automation belongs in a purpose-built integration rather than the conversational path.

• Write risk: product and order actions affect your live store and need review.
• Multiple servers: Shopify ships several MCP servers; capabilities depend on which you connect.
• Plan and access: some features depend on your Shopify plan and store configuration.

Shopify merchants who want to manage their store and analytics in plain English, and developers building themes, integrations or AI shopping experiences. If you run or build on Shopify, this is one of the most consequential connectors in the directory - and a sign of where commerce is heading.

What can it do?

Manage products, orders and collections, write optimised descriptions, and surface analytics like lifetime value and fulfilment delays - in natural language.

Is it official?

Yes - Shopify has shipped multiple official MCP servers.

What is the Storefront MCP?

It powers customer-facing AI and ships in Hydrogen on Oxygen, turning storefronts into AI agent endpoints.

Who is it for?

Both merchants (operations and analytics) and developers (themes and integrations).

The Shopify connector turns Claude into a store operator and a developer accelerator at once - managing products, orders, collections and analytics in plain English, and, via the Storefront MCP, powering AI experiences for customers. Shopify's early, serious investment in MCP makes it one of the most forward-looking connectors in the catalogue.

Scope permissions, start with analytics, and expand into write actions as you build trust. Browse the rest in the complete Claude Connectors Directory.