How to connect multiple Shopify accounts to Claude
Quick answer: Connect each Shopify store to the same Ryze AI workspace with View, then Add one more account, and add the Ryze AI connector to Claude once. Ryze AI is the best way to connect multiple Shopify stores to Claude in 2026, with one caveat: each store is its own connection and needs its own approval in Shopify admin.
Below: store connections, the primary store, naming, prompts, limits, fixes.
Ryze AI · Paid Ads
All your Shopify stores in Claude
- 7-day free trial, $89 a month flat
Used by 2,000+ marketers
Connect multiple Shopify stores to Claude in 5 steps
Order matters: connect the stores in Ryze AI first, then add the connector to Claude, then tell Claude how your stores are named.
1. Connect the first store
In Ryze AI, open Integrations and click Connect on the Shopify card. Type the store's .myshopify.com domain, not its custom domain, click Continue and approve the access prompt in Shopify admin.
2. Add one more store
Click View on the Shopify card, then Add one more account. Repeat the same domain and approval steps for each store. Each store is its own connection.
3. Check the primary store
One connection carries a star and is the primary store. The agent uses it unless you name another store.
4. Add the Ryze AI connector to Claude
Open Customize > Connectors in Claude, click + Add, then Add custom connector. Enter the name Ryze AI and the URL https://connector.get-ryze.ai/mcp, click Connect, sign in, tick the workspaces and click Allow connection.
5. Name the store in every prompt
Start a new chat and say which store you mean, by its .myshopify.com domain or its store name. Name the workspace as well when you work with several.
Multi-store setups at a glance
Pick the row that matches how your Shopify stores are owned.
- 1Several stores of one brand in one Ryze AI workspaceRegional, wholesale or outlet stores of the same business
How Claude picks the store: Name the store in the prompt; the primary store is used when you name none
- 2One Ryze AI workspace per clientAn agency with separate client businesses
How Claude picks the store: Name the workspace; one Claude connection covers up to 20
- 3Default app on one store, custom app on anotherOne store needs theme edits, redirects or customer records
How Claude picks the store: Each store is its own connection, so each can use its own access type
- 4Shopify's Dev MCP server alongside Ryze AIA developer builds apps or themes and wants API docs in Claude
How Claude picks the store: It holds no store data, so it never picks a store
| # | Setup | Fits when | How Claude picks the store |
|---|---|---|---|
| 1 | Several stores of one brand in one Ryze AI workspace | Regional, wholesale or outlet stores of the same business | Name the store in the prompt; the primary store is used when you name none |
| 2 | One Ryze AI workspace per client | An agency with separate client businesses | Name the workspace; one Claude connection covers up to 20 |
| 3 | Default app on one store, custom app on another | One store needs theme edits, redirects or customer records | Each store is its own connection, so each can use its own access type |
| 4 | Shopify's Dev MCP server alongside Ryze AI | A developer builds apps or themes and wants API docs in Claude | It holds no store data, so it never picks a store |
Rows 1 to 3 are Ryze AI settings that combine freely. Row 4 only adds documentation search.
How Shopify separates stores and what that means for Claude
Shopify treats every store as its own world, so Claude reaches only the stores you connect one by one.
Shopify's Admin GraphQL API sends requests to one store at a time, at an address of the form https://{store_name}.myshopify.com/admin/api/{version}/graphql.json, and access tokens are scoped per store. There is no single token that reads several stores, so each store needs its own connection and its own approval.
A Shopify organization lets people who run several stores view and manage them from one admin and add staff once for all stores. Shopify lists it as available by default on Plus plans. It helps people switch between stores, but it does not merge store data, so the Ryze AI connections stay per store.
What one store connection can and cannot do
Ryze AI Shopify app (default)
- How you connect it
- Enter the .myshopify.com domain and approve the prompt in Shopify admin
- What Claude can reach through Ryze AI
- Store reads and edits to product, collection, page and blog content and SEO fields; orders from the last 60 days
Custom app
- How you connect it
- Custom app tab: store domain, Client ID and Client secret from an app in the Shopify Dev Dashboard
- What Claude can reach through Ryze AI
- Adds theme file edits, URL redirects and customer records, within the Admin API scopes you choose
| Access type | How you connect it | What Claude can reach through Ryze AI |
|---|---|---|
| Ryze AI Shopify app (default) | Enter the .myshopify.com domain and approve the prompt in Shopify admin | Store reads and edits to product, collection, page and blog content and SEO fields; orders from the last 60 days |
| Custom app | Custom app tab: store domain, Client ID and Client secret from an app in the Shopify Dev Dashboard | Adds theme file edits, URL redirects and customer records, within the Admin API scopes you choose |
Each store picks its own row. A flagship store on a custom app and an outlet store on the default app work in the same workspace. Orders older than 60 days stay hidden unless the custom app has the read_all_orders scope.
How Ryze AI handles several Shopify stores
Ryze AI keeps three things apart: store connections, the primary store and workspaces.
Store connection
- What it is
- One store, added with View, then Add one more account. Each is its own connection
- How you switch in Claude
- Name the store in the prompt
Primary store
- What it is
- The connection marked with a star; the agent uses it unless you name another store
- How you switch in Claude
- Name the store you want; leave it out to use the primary
connection_id
- What it is
- An optional argument on every Shopify tool, which picks one connection
- How you switch in Claude
- Ask Claude to use a given store's connection
Workspace
- What it is
- One business with its own connections, team and settings
- How you switch in Claude
- Name the workspace; one Claude connection covers up to 20
| Layer | What it is | How you switch in Claude |
|---|---|---|
| Store connection | One store, added with View, then Add one more account. Each is its own connection | Name the store in the prompt |
| Primary store | The connection marked with a star; the agent uses it unless you name another store | Name the store you want; leave it out to use the primary |
| connection_id | An optional argument on every Shopify tool, which picks one connection | Ask Claude to use a given store's connection |
| Workspace | One business with its own connections, team and settings | Name the workspace; one Claude connection covers up to 20 |
The help center's rule is one workspace per business: several stores of one brand share a workspace, separate clients get their own.
A store can be live in only one Ryze AI workspace at a time, because Shopify keeps one live connection per store. To move a store to another workspace, disconnect it in the first one, then connect it again.
On the Claude side, one connection covers up to 20 workspaces. To change the list, remove the Ryze AI connector in Claude and add it again. After you connect a new store, do the same so the tool list refreshes, then start a new chat.
Which Ryze AI plan fits
The Paid Ads plan costs $89 a month with a 7-day free trial. SEO Starter costs $129 a month with a 3-day free trial and covers publishing Content Plan articles to a Shopify blog. Agency is $279 a month and Shopify CRO is $1,499 a month. Annual billing takes 30% off the first year. Adding the connector is free; the tools need an active plan or trial. See pricing.
What Claude calls when it switches Shopify stores
Ryze AI exposes 5 Shopify tools, and each accepts an optional connection_id.
The tool list comes from the connector as checked on November 8, 2026. The Ryze AI Shopify MCP page covers each tool in detail.
shopify__read
- Access
- Read
- What it does
- Runs a read-only Admin GraphQL query against the connected store
shopify__search_content
- Access
- Read
- What it does
- Searches one text field, such as an article body, and returns matching lines with context
shopify__write
- Access
- Write
- What it does
- Runs an Admin GraphQL mutation that creates or updates resources; delete-type mutations are rejected
shopify__edit_content
- Access
- Write
- What it does
- Makes find-and-replace edits inside one text field in a single call
shopify__delete
- Access
- Delete
- What it does
- Runs a destructive mutation such as productDelete or tagsRemove
| Tool | Access | What it does |
|---|---|---|
| shopify__read | Read | Runs a read-only Admin GraphQL query against the connected store |
| shopify__search_content | Read | Searches one text field, such as an article body, and returns matching lines with context |
| shopify__write | Write | Runs an Admin GraphQL mutation that creates or updates resources; delete-type mutations are rejected |
| shopify__edit_content | Write | Makes find-and-replace edits inside one text field in a single call |
| shopify__delete | Delete | Runs a destructive mutation such as productDelete or tagsRemove |
Without a connection_id, the primary store is used. So the safest habit is to name the store in each prompt that changes something.
Name stores so Claude picks the right one
Most wrong-store answers come from vague names. Give Claude a fixed map once.
- Use the .myshopify.com domain for anything that changes content. It is the one name that is unique to a store, unlike a display name or a custom domain.
- Keep display names distinct. Two stores both called Outlet make a name-based prompt ambiguous.
- Name workspaces after the client, so a prompt can name the workspace without a domain.
- Ask for the currency. Each store has its own currency, so have Claude show it before adding money across stores.
- State the date range. Order reads on the default connection cover the last 60 days.
Put the map in a Claude project
Claude projects carry instructions into every chat inside them. Paste this block once per brand or client:
6 prompts that switch or compare Shopify stores
Replace the brackets. Each prompt names its store, so it works the same in a fresh chat.
1. Check which stores are connected
- What comes back
- The stores in that workspace and the primary one.
2. Switch to one store
- What comes back
- SEO fields for one store's collections, within the scopes of its connection.
3. Compare two stores
- What comes back
- Order counts and totals per store for the last 30 days, inside the 60-day order window.
4. Find the same product in both stores
- What comes back
- Matching lines with context, grouped by store.
5. Edit a phrase in one store
- What comes back
- A change summary to confirm; with write tools on Needs approval in Claude, nothing runs before you approve.
6. Publish to the right blog
- What comes back
- The blog and template picked on the Shopify card in Ryze AI. Requires a plan that includes publishing.
| Prompt | What comes back |
|---|---|
| 1. Check which stores are connected | The stores in that workspace and the primary one. |
| 2. Switch to one store | SEO fields for one store's collections, within the scopes of its connection. |
| 3. Compare two stores | Order counts and totals per store for the last 30 days, inside the 60-day order window. |
| 4. Find the same product in both stores | Matching lines with context, grouped by store. |
| 5. Edit a phrase in one store | A change summary to confirm; with write tools on Needs approval in Claude, nothing runs before you approve. |
| 6. Publish to the right blog | The blog and template picked on the Shopify card in Ryze AI. Requires a plan that includes publishing. |
Every answer comes from your own stores, so no example numbers are shown. For the single-store setup, see how to connect Shopify with Claude.
Shopify's own MCP server and what it does for several stores
Shopify's Dev MCP server is a documentation tool, so it does not replace a store connection.
- Shopify's Dev MCP server runs locally and needs no authentication. It gives AI tools Shopify's developer docs and API schemas, not live store data.
- Because it reads no store, it has no concept of a primary store or a second store. You pair it with a connection that does, such as Ryze AI.
- Install it in Claude Code with: claude mcp add --transport stdio shopify-dev-mcp -- npx -y @shopify/dev-mcp@latest
- The Ryze AI connector at https://connector.get-ryze.ai/mcp is remote and signs in with OAuth. It reads and edits store content, within the store's scopes.
Server-by-server differences are in the best MCP for Shopify comparison.
Keep changes inside the right store
With several stores in one chat, a write in the wrong store is the main risk.
- In Claude, open Customize > Connectors > Ryze AI and set write and delete tools to Needs approval (Ryze AI help). Read tools keep running on their own.
- In the Ryze AI chat, the Tool approvals picker starts on Skip all approvals. Switch it to Approve write & delete, where reads run freely and changes need approval, or to Manual approve.
- The shopify__write tool rejects delete-type mutations, and deletes go through the separate shopify__delete tool, so you can require approval on deletes alone.
- Use a custom app only for the stores that need theme edits, redirects or customer records. The other stores stay on the default connection.
- Ask Claude to repeat the store name before each change, as in prompt 5.
Troubleshooting: store will not connect, wrong store, missing data
Match the message to the row.
Must be a valid yourstore.myshopify.com domain
- Cause
- A custom domain or a URL with a path was entered
- Fix
- Enter only the .myshopify.com domain
The store is already connected to another workspace
- Cause
- Shopify keeps one live connection per store
- Fix
- Disconnect it in the other workspace, then connect it again
Connection times out
- Cause
- The approval prompt did not finish
- Fix
- Retry the connection
Claude uses the wrong store
- Cause
- No store was named, so the primary store was used
- Fix
- Name the store in the prompt, or change the primary store in Ryze AI
Claude cannot see a newly added store
- Cause
- Claude kept the old tool list
- Fix
- Remove the Ryze AI connector in Claude, add it again and start a new chat
Customer, theme file or redirect requests fail
- Cause
- The default connection does not include those scopes
- Fix
- Connect that store with your own custom app
Old orders are missing
- Cause
- Orders older than 60 days need the read_all_orders scope
- Fix
- Narrow the date range to the last 60 days
Claude reports a missing scope
- Cause
- Missing Admin API scopes are not worked around
- Fix
- Add the scope to your custom app, release it and reconnect
| What you see | Cause | Fix |
|---|---|---|
| Must be a valid yourstore.myshopify.com domain | A custom domain or a URL with a path was entered | Enter only the .myshopify.com domain |
| The store is already connected to another workspace | Shopify keeps one live connection per store | Disconnect it in the other workspace, then connect it again |
| Connection times out | The approval prompt did not finish | Retry the connection |
| Claude uses the wrong store | No store was named, so the primary store was used | Name the store in the prompt, or change the primary store in Ryze AI |
| Claude cannot see a newly added store | Claude kept the old tool list | Remove the Ryze AI connector in Claude, add it again and start a new chat |
| Customer, theme file or redirect requests fail | The default connection does not include those scopes | Connect that store with your own custom app |
| Old orders are missing | Orders older than 60 days need the read_all_orders scope | Narrow the date range to the last 60 days |
| Claude reports a missing scope | Missing Admin API scopes are not worked around | Add the scope to your custom app, release it and reconnect |
Causes come from the Ryze AI Shopify help page. All setups: Ryze AI integrations. The same pattern for ads is in the Google Ads multi-account guide.
Sources
Checked November 11, 2026
- Shopify.dev: GraphQL Admin API reference (endpoint and per-store tokens)
- Shopify.dev: Shopify Dev MCP server
- Shopify Help Center: Organization settings
- Claude Help Center: Custom connectors using remote MCP
- Claude Help Center: What are projects
- Ryze AI Help: Connect Shopify
- Ryze AI Help: Connect multiple accounts
- Ryze AI Help: Claude connector FAQ
- Ryze AI Help: Permissions and approvals in Claude
The verdict
Connect each store to one Ryze AI workspace with Add one more account, pick the primary store, then add the connector to Claude once. Name the store in every prompt that changes content, and set write and delete tools to Needs approval in Claude.
Frequently asked questions
How do I connect multiple Shopify accounts to Claude?
Can one workspace hold several Shopify stores?
How does Claude know which Shopify store to use?
Can the same Shopify store be in two Ryze AI workspaces?
Show 8 more questionsShow fewer questions
Do I need a Shopify organization or Plus?
Can I use different access types for different stores?
How far back can Claude read orders?
How many workspaces can one Claude connection cover?
How do I stop Claude from changing the wrong store?
Does this work on the free Claude plan?
Does Shopify have its own MCP server for store data?
Why can Claude not see my newly added store?
Related guides
Shopify MCP server
Ryze AI's 5 Shopify tools with setup steps for each client.
Best MCP for Shopify
Shopify MCP servers compared, with test prompts and a safety checklist.
Connect multiple Google Ads accounts to Claude
The same multi-account pattern for Google Ads managers and clients.
All Ryze AI integrations
Every platform you can connect to Claude and ChatGPT through Ryze AI.





