Model Context Protocol (MCP) is an open standard that lets AI assistants like Claude connect to external systems, Shopify included, over a standard protocol; Anthropic developed this standard and handed it over to the Agentic AI Foundation under the Linux Foundation umbrella as of December 2025. A need we run into often at Nodus Works when advising store owners is "I want to access my store data directly with AI, without a development team." The simplest solution to this need today is Shopify's own official Claude connector: an integration you set up in a few clicks from inside Claude's own interface, where all you need to do is approve it in the admin panel. This guide covers how to set up this official connection, what operations it allows, and when alternative, community-built MCP servers might be necessary.
What Is MCP, and How Does It Connect Shopify and Claude?
MCP is a middle layer that lets an AI assistant (like Claude) access an external system's (like Shopify's) data and functions over a standard, predefined protocol. Specific to Shopify, this protocol acts as a common "language" that lets Claude read your store data and act on it.
The practical result: once the connection is set up, when you give Claude a command like "list the 5 most returned products in the last 30 days" or "show me products with stock below 10," Claude sends this request to Shopify's Admin API and presents the result to you in natural language, with tables and charts. This is a similar experience to Shopify's own Sidekick tool, but it runs outside the Shopify admin panel, inside Claude's own interface (web, desktop, mobile, or Claude Code).
Note: MCP marks a shift away from an era where everyone writes their own integration from scratch to answer "how do I connect my AI to my Shopify," toward an era where everyone uses a shared protocol the same way.
There are three separate layers in the Shopify MCP ecosystem: Shopify's official Claude connector (the right starting point for most store owners), Shopify's official MCP servers aimed at developers (Dev MCP, Storefront MCP, Customer Accounts MCP), and independent servers built by the community. These three serve different needs; the following sections cover when each one is the right choice.
Connecting to Shopify with the Official Claude Connector (No Code Required)
Shopify built a first-party connector for Claude; it's listed under the "Productivity" category in Anthropic's own connector directory and is accessible at claude.com/connectors/shopify. This is the simplest path for store owners, without going through technical steps like building a custom app or setting up Node.js.
Step 1: From inside Claude (web, desktop, or mobile), go to the connector directory, find the Shopify connector, and start the setup.
Step 2: Setup automatically redirects you to your Shopify admin panel, where you're asked to sign in to your store.
Step 3: Shopify shows you, one by one, the data access scopes the connector is requesting. Read each scope carefully before approving; once approved, it isn't possible to reduce the access scope, you can only change it by completely removing the app and reinstalling it.
Step 4: Once you complete the approval, the connection becomes active; you can start asking Claude questions directly about your store or having it carry out actions.
Critical Note: Don't click "Approve" without reading every scope on the approval screen. Shopify doesn't make this decision reversible; if you accidentally approve a broad write permission, you'll need to remove the entire integration and set it up again from scratch to narrow the scope.
The connection uses a custom app access token behind the scenes; but you never see or manage this token yourself, Shopify and Claude handle this process on your behalf. If you're connecting your store through a publicly listed app (public install), this can also be done through OAuth; for everyday use, the difference between the two is invisible to most store owners.
What Operations Can the Connector Perform, and Which Permission Should You Approve?
Once the official Claude connector is approved, you can use Claude to create and update products, view orders (read-only), pull analytics data with tables and charts, manage collections and stock, edit pages, and create percentage-based discount codes.
Orders being read-only is a deliberate design decision; it eliminates the risk of Claude accidentally canceling or modifying an order from the start. On the product and stock side, there's write access, so you need to give your commands in those areas carefully.
Tip: After setting up the initial connection, test it with a read-only command like "show me the total number of products in my store." Don't move on to write operations like bulk product updates or creating discount codes until you're sure the connection works correctly and you know what data it can see.
If you want to set up your store's AI integration with a secure architecture and clarify which permissions are actually necessary and which actions shouldn't be automated, we carry out this assessment under our Shopify AI consulting service; the goal is to let AI add operational speed without putting your store data at risk.
Community MCP Servers: When Do You Need Them, and What Risk Do They Carry?
The official connector covers most store owners' needs; but if you need a specific operation the official connector doesn't support (for example, a very specific report format or data transfer to a third system), independent, community-built MCP servers come into play.
These servers generally run on Node.js and require a custom app token or OAuth client credentials to set up; this makes for a more technical setup process compared to the official connector. After setup, server information needs to be added to Claude Desktop's configuration file.
Critical Note: Before granting broad write access to an unofficial, community-built MCP server, you need to have reviewed that server's source code or be confident it comes from a trustworthy source; blindly trusting a piece of code with full access to your store data is risky. Start with read-only access where possible.
As of January 1, 2026, a new custom app can no longer be created from the Shopify admin panel; new apps are set up through Shopify's Dev Dashboard, using the OAuth client credentials method (Client ID + Client Secret). This change slightly alters the setup steps for developers building a community MCP server, but it doesn't affect store owners using the official Claude connector; that process is already managed on your behalf by Shopify and Claude.
Shopify's Own AI Toolkit: Dev MCP, Storefront MCP, Customer Accounts MCP
"The Shopify MCP server" isn't a single product; there are several separate MCP servers inside Shopify's AI Toolkit, each serving a different purpose.
| Server | Purpose |
|---|---|
| Dev MCP | Lets an AI assistant query Shopify's developer documentation; it doesn't perform actions, it only searches documentation |
| Storefront MCP | Tools related to the customer-facing store experience; catalog/cart tools were removed and replaced with methods based on the Universal Commerce Protocol (UCP) |
| Customer Accounts MCP | A separate server for AI integration into customer account flows |
| Official Claude Connector | For the store owner to perform admin operations (products, stock, analytics) through Claude; this guide's focus |
If you're not a developer and your goal is to access your store's admin data through Claude, the right starting point is the official Claude connector. Dev MCP, Storefront MCP, and Customer Accounts MCP are built for developers who want to integrate their own app or storefront experience with AI, a different use case.
Frequently Asked Questions
Do I need to write code to connect Claude to Shopify?
No. The official Claude connector is an integration you set up from inside Claude and approve in the Shopify admin panel; no coding or custom app building is needed.
Do I need to create a custom Shopify app?
No, not for the official connector; that process is managed on your behalf by Shopify and Claude. This step may be needed only if you're using an independent, community-built MCP server, and since January 1, 2026, that's also done through the Dev Dashboard rather than the admin panel.
Can Claude accidentally change something in my store?
Orders are read-only, so there's no risk of order changes. In areas with write access, like product and stock updates, you need to give your commands carefully.
Can I later reduce the data access scope I approved?
No. Shopify doesn't allow reducing an approved scope; to change the scope, you need to fully remove the connector and set it up again.
Is it safe to use an unofficial MCP server?
Community-built servers can work functionally, but granting broad write access without reviewing the source code is risky. For most store owners, the official Claude connector is a safer and sufficient starting point.
Conclusion
The simplest and safest way to connect Shopify to Claude today is Shopify's official Claude connector; there's no need to build a custom app or deal with a technical configuration file, setting it up from inside Claude and approving it in the Shopify admin panel is enough. Community MCP servers are only for specific needs the official connector doesn't cover, and in that case you shouldn't grant broad permissions without trusting the source.
If you'd like to set up a custom AI integration architecture for your store, or review the security configuration of your existing connection, get in touch with Nodus Works; let's clarify together which permissions are actually necessary.
