Connecting Shopify to Claude can mean three different things, and each one needs a different setup.
A developer may want Claude Code to understand Shopify APIs, extensions and app requirements. Someone building an AI shopping experience may want Claude to search a Shopify catalog, manage a cart or move a buyer toward checkout. A merchant may want Claude to research products, build product pages, edit an offer and publish the finished page to Shopify.
Those are different connection paths, with different tools, servers and permission models.
Search for a Shopify MCP Claude setup and you will therefore find several approaches. The right one depends on what Claude needs to accomplish.
This guide covers the main Shopify MCP options, how Shopify Dev MCP works with Claude Code, how PagePilot MCP connects to Claude and Claude Code, and what each setup can and cannot do.
Quick Answer: How Do You Connect Shopify to Claude?
The most important distinction is that there is no universal Shopify MCP connection that gives Claude every Shopify capability.
What Is Shopify MCP for Claude?
Shopify MCP for Claude refers to MCP servers that expose defined Shopify-related tools to Claude. What Claude can do depends on the server it connects to.
Model Context Protocol allows Claude to call tools rather than rely only on conversational knowledge. Depending on the connection, those tools might search live data, retrieve records, modify something, create a new resource or move through several related actions.
That means Shopify development, product discovery, carts, checkout, customer accounts and merchant workflows do not all use the same MCP server.
The server determines the capability. Connecting an MCP does not automatically give Claude universal access to Shopify.
Which Shopify MCP Should You Connect to Claude?
Start with the job you want Claude to perform.
Shopify AI Toolkit and Shopify Dev MCP
Use this route when Claude is helping you build for Shopify.
Typical use cases include:
- Shopify app development
- Shopify APIs
- extensions
- Shopify CLI workflows
- Polaris
- API-schema exploration
- implementation validation
- API migrations
Shopify currently recommends its AI Toolkit plugin as the main setup for supported AI development environments. Developers who specifically want an MCP connection can use Shopify's separate Dev MCP server.
Shopify Dev MCP runs locally and is focused on Shopify development resources rather than merchant product-launch workflows.
For the current installation method and Claude Code command, use Shopify's official AI Toolkit documentation rather than relying on an old copied command, because developer tooling can change.
Shopify Storefront Catalog MCP
Storefront Catalog MCP is designed for AI shopping experiences focused on one merchant's existing Shopify catalog.
It can help an agent search and retrieve products already sold by that merchant.
For example, a shopper might ask:
Find waterproof jackets under $150 in this store.
The distinction is important:
Storefront Catalog MCP helps customers discover what a merchant already sells. It does not help the merchant decide which new products to start selling.
Merchants looking at the wider product-page ecosystem can also compare the role of MCP with more traditional Shopify page builders.
Shopify Cart MCP
Cart MCP handles the pre-checkout part of the shopping journey.
It can support actions such as:
- creating a cart
- retrieving its current state
- revising cart contents
- cancelling a cart
New integrations should use Shopify's dedicated Cart MCP rather than tutorials built around the older Storefront cart tools.
Shopify deprecated its older Storefront get_cart and update_cart approach in favor of the newer Cart MCP architecture.
Shopify Checkout MCP
Checkout MCP takes over when the buyer is ready to move beyond cart building.
It supports the checkout stage of Shopify's agentic-commerce flow.
A common sequence is:
Product discovery → Cart → Checkout
The agent may collect or update required checkout information before returning the buyer to the merchant's checkout experience.
Direct completion depends on the agent's authentication and permissions, so connecting Checkout MCP does not mean every Claude-based agent can autonomously complete a purchase.
Shopify Order MCP
Order MCP handles post-checkout order state for orders associated with the requesting agent's commerce flow.
It should not be confused with unrestricted Shopify Admin order access.
Shopify's current agentic-commerce model can therefore be thought of as:
Catalog → Cart → Checkout → Order
Customer Accounts MCP
Customer Accounts MCP handles authenticated customer-specific workflows.
These may include:
- retrieving supported order information
- checking order status
- accessing customer-account information
- working with supported customer preferences
This is different from Order MCP.
Customer Accounts MCP is tied to the customer's authenticated Shopify account, while Order MCP belongs to the relevant agentic-commerce flow.
PagePilot MCP
PagePilot MCP serves a different audience.
Use it when the merchant wants Claude to work through PagePilot's product-launch workflow.
Supported areas include:
- product research
- product-page generation
- retrieving existing PagePilot pages
- editing page wording
- changing PagePilot pricing
- editing variants
- generating AI product images
- seeing Shopify stores already connected to PagePilot
- publishing PagePilot pages to Shopify
- updating supported Shopify products previously created through PagePilot
PagePilot MCP is not a universal Shopify Admin server.
It does not create standalone pages or advertorials through MCP. It also does not add, remove or reorder page sections, change deeper design settings, edit SEO settings, upload your own images, connect Shopify stores, browse the template gallery or delete and duplicate pages.
Those deeper editing tasks remain separate from the MCP workflow. PagePilot's guide to Shopify product page customization covers the broader page-editing side.
Need help deciding which PagePilot MCP setup fits your workflow? Contact PagePilot Support.
How to Connect Shopify Dev MCP to Claude Code
Shopify Dev MCP is the development path.
Step 1: Check the Requirements
You will need:
- Claude Code
- Node.js
- terminal access
Shopify's current AI development documentation requires Node.js 18 or higher for its AI Toolkit environment.
Step 2: Choose the Shopify Developer Setup
Shopify currently offers two related options.
Shopify AI Toolkit is its recommended broader development setup.
Shopify Dev MCP is available when you specifically want an MCP server connected to Claude Code.
Shopify provides the current Claude Code installation command in its official AI Toolkit documentation. Copy the current command from Shopify rather than from a static third-party article, so you are using the latest package and syntax.
Step 3: Restart Claude Code
Once the plugin or MCP server has been added, restart Claude Code so the new development tooling is available.
Step 4: Test It With a Development Task
For example:
Which Shopify API should I use to retrieve product metafields?
Or:
Review this Shopify extension against current platform requirements.
Or:
Help me migrate this extension to the current Shopify API version.
Keep the purpose clear.
Shopify Dev MCP is development tooling. It is not designed to research products for a merchant, build PagePilot product pages or publish a PagePilot page to Shopify.
How to Connect PagePilot MCP to Claude
PagePilot provides a more direct merchant setup because it generates the connection details inside the PagePilot dashboard.
Before You Start
You need:
- a PagePilot account
- access to PagePilot Agent & MCP
- Claude
- a Shopify store already connected to PagePilot if you plan to publish
Connecting PagePilot MCP and connecting Shopify are separate steps.
PagePilot MCP cannot connect your Shopify store.
If you have not connected the store yet, do that through PagePilot before attempting to publish. Merchants working through their broader Shopify setup may also find PagePilot's AI dropshipping workflow guide useful for understanding how product research, page creation and store operations fit together.
Step 1: Open PagePilot Agent & MCP
Inside PagePilot, open PagePilot Agent & MCP.
Choose the Claude tab.
PagePilot presents the Claude connection as a guided three-step process rather than requiring you to assemble an MCP configuration manually.
Step 2: Open Claude Connectors
Use the Open Claude Connectors button inside PagePilot.
Depending on the Claude interface you are using, the custom-connector controls may appear under Settings or Customize.
Select the option to add a custom connector.
Using PagePilot's direct button is the easiest route because it takes you toward the correct Claude connector screen.
Step 3: Copy Your Generated PagePilot Connection Details
PagePilot provides the information Claude needs, including:
- the connector name
- the generated Remote MCP Server URL
Copy these values directly from your own PagePilot account.
The generated URL contains the PagePilot API credential, so treat the entire URL as a secret.
Do not:
- publish it
- share it publicly
- paste it into a public repository
- include it in an unredacted screenshot
- copy somebody else's connection URL
There is no reason to reproduce PagePilot's generated credential or configuration in an article. Each user should retrieve their own current connection details from their PagePilot dashboard.
Step 4: Save and Enable PagePilot
Save the connector inside Claude.
Enable PagePilot in the conversation where you want Claude to use its tools.
Step 5: Start With a Product Task
PagePilot provides a Start creating option that opens Claude with a starter request.
A merchant might begin with:
Create a PagePilot product page from this product URL in English, then show me the result before publishing.
If the Shopify store is already connected, the workflow can continue into publishing.
Having trouble connecting Claude? Contact PagePilot Support for help with your setup.
How to Connect PagePilot MCP to Claude Code
PagePilot also provides a dedicated Claude Code setup.
The important difference is that Claude Code uses a project-scoped configuration rather than Claude's standard custom-connector flow.
Step 1: Open the Claude Code Setup in PagePilot
Inside PagePilot Agent & MCP, select Claude Code.
PagePilot provides the current project setup instructions directly in the dashboard.
Step 2: Use the Configuration Generated by PagePilot
PagePilot generates the MCP configuration required for the project.
Copy that configuration directly from your own PagePilot dashboard into the project file Claude Code uses for project-scoped MCP servers.
Do not rebuild the configuration from an example found in an article.
The generated configuration contains authentication information tied to the PagePilot account, so it must be handled as a credential.
If you collaborate through version control, do not commit a live PagePilot API key into a shared repository.
Step 3: Restart Claude Code
After saving the configuration, restart Claude Code so it can load the PagePilot MCP server.
Step 4: Review the Server Approval
Claude Code may ask you to approve a project-scoped MCP server before it can be used.
Review the server before approving it.
Step 5: Start Your PagePilot Workflow
Once PagePilot is available, you can use normal language instead of MCP commands.
For example:
Create a product page from this URL in English and show me the finished page before publishing.
The PagePilot dashboard also provides a starter prompt for Claude Code that you can copy and adapt.
If the Claude Code connection does not load as expected, contact PagePilot Support.
Claude vs Claude Code for PagePilot MCP
Regular Claude is usually the simpler interface when the goal is a conversational merchant workflow.
Claude Code makes more sense when PagePilot is being used inside a development project or alongside Shopify development tooling.
Can Claude Connect Directly to Shopify Storefront MCP?
A developer can build a Claude-based shopping application around Shopify's Catalog, Cart, Checkout and related commerce tools.
That is different from a merchant adding a ready-made connector.
Shopify's commerce MCP surfaces can involve:
- an agent profile
- authentication
- capability negotiation
- application logic
- commerce-flow state
They are infrastructure for building commerce agents rather than a universal one-click connection that lets regular Claude operate a store.
PagePilot's merchant setup is different because PagePilot creates the remote MCP connection details for its own product-page workflow.
Can I Add a Remote MCP to Regular Claude?
Yes.
Claude supports custom remote MCP connectors.
The general process is:
Open Claude's connector settings.
Add a custom connector.
Enter the remote server details provided by the MCP service.
Complete any required authentication.
Enable the connector for the conversation where you want to use it.
Remote MCP servers need to be reachable over the internet because Claude's cloud infrastructure connects to them.
For PagePilot, those connection details are generated in the PagePilot dashboard.
Only connect Claude to MCP servers operated by organizations you trust, especially when those servers expose write actions.
What Can Claude Do With PagePilot MCP?
Once the connector is enabled, Claude can call PagePilot's supported tools through ordinary requests.
Research Products
PagePilot MCP supports merchant product research.
For example:
Find me products worth researching for a new store.
This is different from Shopify Storefront Catalog MCP.
Storefront Catalog MCP searches products already sold by one merchant. PagePilot product research belongs earlier in the merchant workflow, when the merchant is deciding what may be worth testing.
If product economics are part of that decision, PagePilot's guide to high-margin dropshipping products provides additional context around margin, product selection and testing.
Create a Product Page
Claude can create a PagePilot product page through MCP.
For example:
Create a German product page from this URL using the Bloom template and target the copy toward women shopping for a gift.
Merchants who want ideas for structure, visual hierarchy and persuasive elements can also review PagePilot's Shopify product page examples before choosing how they want a new page positioned.
PagePilot MCP currently creates product pages.
It does not create standalone pages or advertorials through the MCP workflow.
Select a Template
PagePilot templates are selected by name.
Available examples include:
- Bloom
- Greens
- Honey
- Clarity
- Aura
- Legacy
- Stone
- Cotton
Saved templates can also be used.
Claude cannot browse the PagePilot template gallery through MCP. If you want a specific template, include its name in the request.
If you do not specify one, PagePilot can reuse the previously selected template.
For a broader look at page-building options, see PagePilot's comparison of Shopify page builders.
Select a Language
PagePilot supports product-page generation in more than 30 languages.
You can include the language directly in the request:
Create this product page in French.
Or:
Build this page in German using the Bloom template.
Edit Page Copy
Claude can make targeted text changes to an existing PagePilot page.
For example:
Rewrite the headline to emphasize portability, but leave the rest of the page unchanged.
Or:
Make the guarantee section clearer without changing the offer.
If the page needs broader conversion work, PagePilot's guide to ecommerce product page optimization covers the role of copy, imagery, trust elements and page structure.
Can Claude Edit Prices and Variants?
Yes, within PagePilot's supported product-page workflow.
For pricing:
What's the current price on this PagePilot page?
Then:
Change the price to 29.99 and set the compare-at price to 49.99.
Price changes update the PagePilot page first.
They do not change the live Shopify product until the updated PagePilot page is published.
Be Specific With Variant Changes
Variant edits need more care.
A good request is:
Keep every existing color and size, then add Blue in the same size combinations.
A vague request such as:
Make the sizes S and M.
can unintentionally remove other variants.
Describe the final configuration you want, including the options that must remain.
Can Claude Generate Product Images?
Yes.
PagePilot MCP supports AI-image generation for PagePilot product pages.
For example:
Generate three lifestyle images for this product page.
You can also ask:
How many AI image generations do I have remaining?
A single PagePilot request can generate up to four images and uses the account's available image allowance.
Claude cannot upload arbitrary user image files into a PagePilot page through MCP.
Product imagery is only one part of the page, so it can be useful to review PagePilot's high-converting product page guidance when deciding how images, copy and trust elements should work together.
Can Claude Publish a Product to Shopify?
Claude can publish a PagePilot product page to a Shopify store that has already been connected to PagePilot.
A simple workflow might be:
Which Shopify stores are connected?
Then:
Publish this finished page as a new Shopify product.
PagePilot MCP can see stores already connected through PagePilot and publish supported pages to them.
It cannot create the Shopify connection.
If a store has not been connected yet, complete that step in the PagePilot dashboard before asking Claude to publish.
Need help with your store connection or publishing workflow? Contact PagePilot Support.
Can Claude Manage My Shopify Store?
Claude can perform Shopify-related actions exposed by the MCP servers it is connected to, but no single MCP connection automatically gives Claude full Shopify Admin control.
The scope changes by server:
- Shopify AI Toolkit / Dev MCP: development resources and supported developer workflows
- Storefront Catalog MCP: product discovery within an existing catalog
- Cart MCP: shopper cart actions
- Checkout MCP: purchase-stage workflows
- Customer Accounts MCP: authenticated customer workflows
- PagePilot MCP: merchant product research, PagePilot page creation and editing, AI images and Shopify publishing
- Admin-capable MCP: broader Shopify operations according to the tools and API scopes exposed
This is why "Can Claude manage Shopify?" does not have a universal yes-or-no answer.
The better question is:
Which Shopify tasks does the connected MCP expose?
Best Shopify MCP for Claude by Use Case
Shopify development → Shopify AI Toolkit or Shopify Dev MCP
Search one Shopify catalog → Storefront Catalog MCP
Shopper cart actions → Cart MCP
Checkout workflows → Checkout MCP
Authenticated customer workflows → Customer Accounts MCP
Merchant product research → PagePilot MCP
Create and edit PagePilot product pages → PagePilot MCP
Generate PagePilot AI product images → PagePilot MCP
Publish PagePilot pages to Shopify → PagePilot MCP
Broad Shopify Admin operations → depends on the implementation and Shopify API scopes
Shopify Dev MCP vs PagePilot MCP for Claude
Shopify Dev MCP helps Claude build for Shopify. PagePilot MCP helps Claude operate PagePilot's product-launch workflow.
They are complementary rather than substitutes.
A merchant who is also developing Shopify functionality could reasonably use both.
Example: Run a Product Launch Through Claude
A PagePilot product workflow can remain inside one Claude conversation.
Start with product research:
Find me products worth researching for a new store.
After choosing a product:
Build a French product page for this product using the Bloom template.
Then configure the offer:
Keep all existing variants and set the main price to 39.99 with a compare-at price of 59.99.
Create supporting imagery:
Generate three lifestyle images for the page.
Review the page:
Show me the finished page details before publishing.
Then publish:
Publish it as a new product to my connected Shopify store.
This is also where PagePilot differs from Shopify Dev MCP.
Shopify Dev MCP gives Claude development context. PagePilot MCP gives Claude merchant-facing PagePilot tools that can move a product-page workflow toward publication.
For more ways AI can fit into product testing and ecommerce operations, see PagePilot's guide to using AI for dropshipping.
Can I Connect Multiple Shopify MCP Servers to Claude?
Yes.
You do not need one MCP server with access to every part of your Shopify operation.
A setup could use:
- Shopify Dev MCP for development
- PagePilot MCP for product-launch workflows
- Storefront Catalog and Cart MCP for customer-facing shopping
- Customer Accounts MCP for authenticated customer workflows
Specialized connections can also reduce unnecessary permissions.
A development assistant does not need PagePilot publishing access simply because both workflows involve Shopify.
Is It Safe to Connect PagePilot or Shopify MCP to Claude?
Risk depends on what the connected server can do.
Searching a public catalog is very different from:
- changing prices
- modifying variants
- publishing products
- accessing customer data
- changing order information
Before connecting an MCP server to live commerce systems:
- use MCP servers you trust
- review requested permissions
- expose only the tools required for the workflow
- review consequential write actions
- disconnect servers you no longer use
- keep credentials out of public files and screenshots
- do not place live API credentials in shared version-control repositories
- test unfamiliar workflows before using them with production data
For PagePilot specifically, the generated Claude connector contains credential information, and the Claude Code configuration also contains account authentication.
Treat both as secrets.
PagePilot write actions may also trigger Claude approval prompts. Keeping those prompts enabled gives you a chance to review changes involving pricing, variants, images or publishing before they proceed.
Troubleshooting PagePilot MCP With Claude
Claude Cannot See PagePilot Tools
First check whether the PagePilot connector is enabled in the current conversation.
If it is not, Claude will not have access to the PagePilot toolset even if the connector has already been configured.
If the connection details were regenerated, use the current values from your own PagePilot dashboard rather than relying on an older saved URL.
Claude Code Does Not Load PagePilot
Check that:
- the project configuration is in the correct project location
- you copied the current configuration generated by PagePilot
- Claude Code was restarted after the configuration was saved
- the PagePilot MCP server was approved when requested
Avoid copying a configuration belonging to another PagePilot account.
Claude Can Create a Page but Cannot Publish It
Check that:
- your PagePilot account has the required access
- the Shopify store is already connected to PagePilot
- you are working with the intended PagePilot page
- PagePilot is enabled in the Claude conversation
- the requested publishing action is available for that page/store
The MCP cannot establish the Shopify store connection for you.
The Connection Credential Was Exposed
If a PagePilot MCP credential appears publicly in a repository, screenshot or shared document, treat it as exposed.
Replace the affected credential before continuing to use that connection.
The Shopify Page Looks Different After Publishing
Publishing and MCP connectivity are not the same as theme presentation.
Shopify themes can affect how a product page appears after publication. If the issue is theme compatibility or how the page renders inside the store, contact PagePilot's support team rather than repeatedly reconnecting the MCP.
Still having trouble? Contact PagePilot Support.
Common Shopify and Claude MCP Mistakes
Connecting Dev MCP and Expecting Merchant Operations
Shopify Dev MCP is developer tooling. It is not a PagePilot product-launch assistant.
Treating Storefront Catalog MCP as Merchant Product Research
Storefront Catalog MCP searches products that already exist inside one merchant's catalog. Merchant-side product research serves a different purpose.
Following Old Storefront Cart Tutorials
Older Storefront cart tools were deprecated in favor of Shopify's dedicated Cart MCP architecture. Use the current Shopify documentation for new implementations.
Assuming a Shopify MCP Endpoint Is a One-Click Claude Connector
Shopify's agentic-commerce MCP surfaces are development infrastructure. They should not be presented as equivalent to PagePilot's generated merchant-facing remote MCP connection.
Expecting PagePilot MCP to Connect Shopify
It cannot. Connect the store through PagePilot first.
Using Vague Variant Instructions
Describe both what should change and what should remain. Variant requests represent the intended final configuration.
Need Help Connecting Claude to PagePilot?
If you are unsure which setup fits your workflow, cannot get Claude or Claude Code connected, or need help publishing to Shopify, PagePilot's support team is available through live chat and email.
