Shopify MCP: What It Is, Which Servers Exist, and How to Use Them

There isn't one Shopify MCP server that handles every Shopify task. That single fact explains most of the confusion around the term.

Shopify runs separate MCP interfaces for product discovery, carts, checkout, orders, customer accounts and development. Each exposes different tools and expects different authentication. An agent that searches a catalog cannot edit products.

Most of Shopify's official infrastructure serves shopper-facing commerce and developer tooling. A merchant who wants an assistant to research products, build pages and publish them needs a different workflow.

This guide covers what Shopify MCP means, which servers exist, what each can do, whether Claude or ChatGPT can use them, and where PagePilot MCP fits.

What Is Shopify MCP?

Shopify MCP refers to the Model Context Protocol servers and integrations that let AI systems reach specific Shopify commerce tools, data or development resources. What the AI can do depends entirely on which server it connects to.

Model Context Protocol is an open standard giving AI systems a consistent way to discover tools and call them. A provider exposes a server, and any compatible client reads the tool list.

MCP is the connection layer. It does not decide which Shopify permissions or actions exist. The server does.

Two Shopify Model Context Protocol servers can have almost nothing in common. One searches public listings with no credentials. Another requires an OAuth token tied to a named customer.

Does Shopify Have an Official MCP Server?

Yes, though Shopify provides several MCP servers rather than one universal Shopify MCP server.

Shopify's agent documentation organizes Shopify agentic commerce around four stages: authenticate, discover products, build carts and checkouts, then monitor orders. Separate surfaces cover customer accounts, storefront shopping and development.

Current Shopify MCP Landscape

These are not interchangeable. A server that searches a catalog cannot edit a product.

Which Shopify MCP Server Do I Need?

The right server is the one whose Shopify MCP tools match the task.

Search Products Across Shopify With Global Catalog MCP

Shopify Catalog MCP comes in two forms. Global Catalog MCP handles cross-merchant discovery, searching across the Shopify ecosystem rather than one storefront.

It documents three tools: search_catalog, lookup_catalog and get_product. Requests go to https://catalog.shopify.com/api/ucp/mcp, and every call carries an agent profile URL in meta.ucp-agent.profile.

Find me an organic cotton sweater under $100 that ships to the UK.

Three documented limits matter. Pagination stops at 1,000 results. The total_count field is an estimate. Some fields are generated or enriched by Shopify, so they may be absent or vary in accuracy.

This is product discovery, not merchant Admin access.

Search One Shopify Store With Storefront Catalog MCP

The distinction is scope. Global Catalog MCP searches many merchants. Storefront Catalog MCP searches one.

Shopify recommends it whenever buyer intent is scoped to a single merchant. It exposes the same three tools.

An agent profile is required here too, and the tools returned depend on what it advertises. This fits a store-specific Shopify AI agent or recommendation tool.

What Is Shopify Storefront MCP?

Storefront MCP is a store-specific shopping interface for customer-facing commerce. A Shopify app acts as the MCP client, and a theme extension delivers the chat experience to shoppers.

It spans two endpoints on the same store domain:

• https://{shop}.myshopify.com/api/ucp/mcp serves the UCP catalog tools: search_catalog, lookup_catalog, get_product.
• https://{shop}.myshopify.com/api/mcp serves the store's own tools: search_shop_policies_and_faqs, plus the deprecated get_cart and update_cart.

Shopify documents these servers as not requiring authentication, though catalog tools still need an agent profile.

Shopify's Storefront MCP reference may still show the legacy get_cart and update_cart tools. Shopify deprecated them in favor of UCP Cart MCP and set August 31, 2026 as the end of maintained support. New integrations should use Cart MCP.

Build a Shopify Cart With Cart MCP

Shopify documents a dedicated Cart MCP server for assembling a cart. Its four tools are create_cart, get_cart, update_cart and cancel_cart.

Cart tools accept unauthenticated requests; no Bearer token is needed. Every request still carries an agent profile in meta["ucp-agent"], and cancel_cart requires a unique idempotency key.

The Cart MCP Behavior Most People Miss

update_cart uses full-replacement semantics. Shopify's wording is direct: each request replaces the cart's full state with the payload you send. Omit a field such as line_items and it is removed from the cart.

This differs from Shopify APIs that merge partial updates server-side. An agent sending only the item it wants to change can wipe out everything else. Send the complete desired cart state every time.

Start and Manage Checkout With Checkout MCP

Cart MCP builds the basket. Shopify Checkout MCP handles the purchase stage through create_checkout, get_checkout, update_checkout, complete_checkout and cancel_checkout.

Checkout MCP has stricter access and rate limits than Cart MCP. Completing checkout directly requires Token-tier access with permission to complete purchases; otherwise, the buyer is handed off through the checkout continue_url.

The important correction to a common assumption: most agents cannot complete payment themselves. Only agents whose token has been granted checkout-completion permission can call complete_checkout directly.

Track an Order With Order MCP

Order MCP sits in the post-checkout stage and exposes one tool, get_order. It returns line items, fulfillment expectations and events with tracking, post-purchase adjustments, and a totals breakdown.

Order MCP is not a search engine for every order in a store. Shopify requires the order ID to be a Global ID returned by complete_checkout on a checkout that agent originated. Orders placed through other apps, or directly on the storefront, aren't accessible.

Shopify recommends webhooks as the primary update channel, since they deliver full order state on every change. Use get_order for on-demand reads, not polling.

What's the current status of the order I just placed?

What Is Shopify Customer Accounts MCP?

Customer Accounts MCP handles authenticated, customer-specific workflows: order status, order details and account preferences.

It is the most tightly authenticated surface here, requiring an OAuth 2.0 access token from the authorization code flow with PKCE. Requests go to https://{shopDomain}/customer/api/mcp.

Shopify does not publish a fixed tool list for this server, pointing developers to tools/list instead.

Where is my order?

Customer Accounts MCP is tied to a customer's authenticated Shopify account. Order MCP covers orders placed through a specific agent.

What Is Shopify Dev MCP and the Shopify AI Toolkit?

Shopify offers both the Shopify AI Toolkit and a separate Dev MCP server for development workflows. The AI Toolkit is Shopify's recommended plugin-based setup, while developers who specifically want MCP can run the local @shopify/dev-mcp server.

Shopify AI Toolkit. Shopify documents the AI Toolkit for several supported AI development tools, including Claude Code, Codex, Antigravity CLI, Cursor and VS Code, with additional plugin-supported clients also listed. It ships a ucp skill applying Universal Commerce Protocol best practices and pairs with the UCP CLI (npm install -g @shopify/ucp-cli, Node.js 18 or higher). CLI commands mirror the MCP surfaces: ucp catalog search, ucp cart create, ucp order get.

Shopify Dev MCP. A separate MCP server set up through the @shopify/dev-mcp package. Shopify documents it as running locally and not requiring Shopify authentication.

One thing this tooling is not: a route for a merchant to change live store prices by chat. It gives development environments context for building an AI agent for Shopify, not Admin access.

Where Does UCP Fit Into Shopify MCP?

MCP and UCP are related and frequently confused.

• MCP is the standardized way for AI systems to discover and invoke tools.
• UCP is the Universal Commerce Protocol, an open protocol defining standardized commerce capabilities and data models.
• Shopify UCP bindings are the MCP tools exposing those capabilities: catalog, cart, checkout and orders.

UCP is an industry effort rather than a Shopify product. It was co-developed by Shopify and Google and has broader support across major commerce, technology and payments companies. It carries MCP support built in and is published under the Apache 2.0 license. Shopify's signature documentation currently references the 2026-08-25 specification. That is why Shopify's newer commerce servers share a consistent shape.

Can Shopify MCP Manage My Shopify Store?

Some servers can perform merchant-side actions, but Shopify MCP does not automatically mean Shopify Admin access.

The official surfaces above serve shopper discovery, carts, checkout, agent-originated orders, customer accounts and development. None is a merchant control panel.

Merchant-side actions such as changing products or prices, creating pages or publishing assets need an implementation exposing those write capabilities.

The line runs between customer-facing commerce and merchant operations. Shopify's official ecosystem concentrates on the first; merchant operations mostly come from a Shopify merchant MCP built for that purpose.

Where Does PagePilot MCP Fit?

Shopify's official tools cover shopping, customer and development workflows. PagePilot MCP addresses a different problem: running the PagePilot product-page workflow through an AI assistant.

Supported merchant tasks:

• product research
• page generation from supported URLs
• retrieving existing PagePilot pages
• editing page wording
• reading and changing prices
• editing variants
• generating AI product images
• seeing connected Shopify stores
• publishing a page to Shopify, or updating one it created

Several things stay in the dashboard. This MCP for Shopify does not create advertorials or standalone pages, add or reorder sections, or change fonts, colors and design settings. It cannot edit SEO settings, connect a store, upload your own images, or delete and duplicate pages.

Shopify's catalog and cart servers help an agent shop for a buyer; PagePilot MCP helps a merchant produce the page that buyer lands on. This roundup of Shopify page builders covers the wider category.

Want AI to build the product page too? Explore PagePilot MCP

Shopify MCP vs. PagePilot MCP

Shopify's official ecosystem is commerce infrastructure. PagePilot MCP is a merchant workflow layer for pages. Neither replaces the other.

See what PagePilot MCP can do

Can I Connect Shopify to Claude?

Certainly, though what Claude can do depends on which server you connect.

Claude Code with the Shopify AI Toolkit. Shopify documents Claude Code among its supported development clients.

Claude with a shopping or customer server. Catalog and cart surfaces need no credentials. Customer Accounts MCP needs an OAuth token tied to a real customer.

Claude with PagePilot MCP. PagePilot publishes configuration for Claude and Claude Code, letting supported PagePilot actions run conversationally.

The distinction underneath all three: connecting Claude to Shopify documentation is not permission to operate merchant data. What it can do comes down to the server, its scopes, and whether its tools read or write.

Can I Connect Shopify to ChatGPT?

The same qualified answer applies. ChatGPT can use Shopify capabilities where the relevant server is supported in the ChatGPT environment, but no single switch grants unrestricted access.

PagePilot works as a concrete example. This Shopify MCP integration supports ChatGPT through its setup flow, with Developer Mode enabled first. A merchant can then say:

Publish this PagePilot page to my already connected Shopify store.

The phrase "already connected" is doing real work. The store must be linked in the PagePilot dashboard first; PagePilot MCP cannot create that connection.

Shopify MCP vs. Shopify API

The Shopify API exposes Shopify data and operations programmatically. MCP provides a standardized tool interface an AI system uses to discover and invoke capabilities, many of which rely on those APIs underneath.

MCP does not replace Shopify APIs. It changes who is calling and how available actions are described. Searches for a Shopify MCP API usually mean this comparison: the two are layers, not alternatives.

Shopify MCP Terminology, Sorted

MCP is the protocol connecting AI systems to tools. Shopify MCP servers expose defined Shopify capabilities. Shopify AI Toolkit is the recommended development plugin; Shopify Dev MCP is the separate local server for developers who want MCP directly. UCP is the Universal Commerce Protocol behind Shopify's newer servers.

How to Get Started With Shopify MCP

There is no single installation flow; these are separate servers with separate requirements.

Step 1: Decide What You Want the AI to Do

Search across merchants or one store? Build a cart? Manage checkout? Retrieve order state? Work with customer accounts? Build apps or product pages?

Step 2: Pick the Server for That Task

The job determines the server.

Step 3: Check Client Compatibility

That might be Claude, Claude Code, ChatGPT, Codex, Cursor or VS Code. Not every server works in every client.

Step 4: Check Authentication and Permissions

Shopify describes three tiers of agent traffic. Token tier uses JWT Bearer authentication and reaches sensitive tools including complete_checkout and order tools. Signed tier uses HTTP signatures verified against the agent's public UCP profile, with no access to those. Anonymous traffic carries no credentials and gets the lowest rate limits.

In practice: catalog and cart work without credentials, checkout completion and order reads do not, and Customer Accounts MCP requires OAuth.

Step 5: Test a Small Read Action First

Search this store for black running shoes.

Show me my PagePilot pages.

Where write actions are available, review the proposed change before granting persistent approvals.

Shopify MCP Prompt Examples

Cross-store discovery: "Find me a lightweight carry-on suitcase under $150."

Single-store search: "Search this store for waterproof hiking jackets in black."

Cart: "Add the medium blue version to my cart." "Remove the first item and show me the new total."

Checkout: "Start checkout for this cart." "Show me what information is still needed."

Order: "What's the current status of the order I placed through this agent?"

PagePilot research: "Find me products worth researching for a new store."

PagePilot page building: "Build a German product page from this URL using the Bloom template."

PagePilot publishing: "Publish this finished page to my already connected Shopify store."

Real users rarely say "using Shopify MCP" in a prompt. Once you connect AI to Shopify, the assistant picks tools from the task.

Build your first product page through PagePilot MCP

Is Shopify MCP Safe?

Risk tracks the capabilities exposed, not the protocol. A server searching public listings differs entirely from one reaching protected customer data.

The authentication gradient across Shopify's surfaces shows the pattern. Catalog and cart tools work anonymously. Order reads and checkout completion require Token-tier credentials. Customer Accounts MCP requires OAuth with PKCE, because it reaches a named person's order history.

Before connecting to a live store, check:

• which tools the server exposes, and whether they read or write
• which Shopify resources those tools can reach
• what authentication and access scopes are required
• whether protected customer data is in scope
• whether the client asks for approval before write actions
• whether the provider is one you would trust with those permissions

Does Shopify MCP Replace Shopify Admin?

No. MCP moves specific workflows into an AI assistant, but it does not make Shopify Admin unnecessary.

Catalog MCP lets an agent find products without becoming a merchant admin interface. PagePilot MCP runs supported page workflows while deeper design stays in its dashboard.

The practical scope is narrower: each server only exposes the workflows and permissions it was designed to support. Anyone planning AI ecommerce workflows should map which steps a server genuinely covers first.

What Is the Best Shopify MCP Server for Your Use Case?

There is no single best MCP server for Shopify; the right one depends on the job.

The decision table above maps each job to its server. Global Catalog covers cross-merchant shopping, Storefront Catalog a single store, Cart and Checkout the buying journey. Order MCP handles agent-originated orders, Customer Accounts MCP authenticated shoppers, the AI Toolkit or Dev MCP development, and PagePilot MCP merchant page workflow. Broad Admin access needs an implementation chosen around the specific resources and scopes required.

Merchants weighing the last two usually care about margin and speed to a live page. This list of high-margin dropshipping products helps while deciding what to test. Deeper layout work still belongs in Shopify product page customization rather than a chat window.

Connect PagePilot MCP and run your product-page workflow from chat