By Ira Bodnar, Ryze AI · Updated · Connector tested November 13, 2026
Quick answer
The main way to connect OpenClaw to Shopify is the Ryze AI connector. Connect your store in Ryze AI by approving the access prompt in Shopify admin, then save https://connector.get-ryze.ai/mcp in OpenClaw as a streamable-http server with auth set to oauth, using the CLI, Settings > MCP in the Control UI or openclaw.json. Sign in once and OpenClaw can list 5 Shopify tools: two that read, two that write and one that deletes.
- In Ryze AI open Integrations, click Connect on the Shopify card and type your .myshopify.com domain
- Approve the access prompt in Shopify admin
- Save the Ryze AI server in OpenClaw with openclaw mcp set, the Control UI or openclaw.json
- Run openclaw mcp login ryze, click Allow connection, then ask about your products, pages or blog
OpenClaw to Shopify at a glance
| Fact | Detail |
|---|---|
| Main way to connect | The Ryze AI connector, saved in OpenClaw as one remote MCP server named ryze |
| Server address | https://connector.get-ryze.ai/mcp, with transport set to streamable-http |
| Sign-in | OAuth to Ryze AI with openclaw mcp login ryze, or Sign in under Settings > MCP for an administrator. A Ryze AI API key in a bearer header is the other route |
| Shopify tools | 5: shopify__read, shopify__search_content, shopify__write, shopify__edit_content and shopify__delete |
| Can it change the store | Yes, through the write and delete tools. OpenClaw's docs describe no per-call prompt for its built-in runtime, so limit the tools yourself (see the approvals note below) |
| Other data in the same chat | Google Ads, Meta Ads, GA4 and Search Console tools, when those platforms are connected in the same Ryze AI workspace |
| OpenClaw plan needed | None to buy. OpenClaw is MIT licensed and self-hosted, and its docs say it has no paid tier |
| Ryze AI price | Paid Ads is $89 per month with a 7-day free trial. Adding the connector is free |
| Shopify's own option for OpenClaw | The Shopify AI Toolkit plugin, installed with openclaw plugins install npm:@shopify/ai-toolkit. It brings Shopify's developer docs and API schemas, not store data |
| Shopify access of the default connection | 13 access scopes. Customer records, discounts and orders older than 60 days are not among them |
| Last tested | Shopify calls through the connector on November 13, 2026. No step inside OpenClaw was run |
Before you start
- OpenClaw. It is an open-source project under the MIT license that you host yourself. You need a running Gateway and one of three things: the openclaw command on the Gateway machine, administrator access to the Control UI, or write access to the Gateway's openclaw.json.
- Access to your Shopify admin. You need to be able to approve the app prompt for the store. Enter the .myshopify.com domain, not your custom domain. A store can be live in only one Ryze AI workspace at a time.
- A Ryze AI workspace on a plan or free trial. Paid Ads is $89 per month with a 7-day free trial; SEO Starter is $129 per month with a 3-day free trial and covers publishing articles to the Shopify blog. Adding the connector is free, but the Shopify tools need an active plan or trial.
- A note on testing. Ryze AI has no help-center page for OpenClaw and the OpenClaw steps were not run for this page. They follow OpenClaw's own documentation for remote servers that use OAuth, as read on November 15, 2026.
How to connect OpenClaw to Shopify
The first two steps happen in Ryze AI and Shopify, the next three in OpenClaw, and the last is your first prompt. The connector URL is the same for every user.
Connect your store in Ryze AI
Create a Ryze AI account or sign in, open Integrations, find the Shopify card and click Connect. On the Shopify app tab, type your .myshopify.com domain and click Continue.
Approve the access prompt in Shopify
Approve the access prompt in your Shopify admin. You return to Ryze AI with the store connected. The default connection needs no API keys.
Save the Ryze AI server in OpenClaw
Stop the Gateway with openclaw gateway stop, because OpenClaw 2026.10.10 (November 3, 2026) holds back CLI changes to MCP settings while a Gateway runs. Then run: openclaw mcp set ryze '{"url":"https://connector.get-ryze.ai/mcp","transport":"streamable-http","auth":"oauth"}'. The same entry can go under mcp.servers in ~/.openclaw/openclaw.json, or be added with Add server under Settings > MCP in the Control UI while the Gateway runs.
openclaw gateway stop openclaw mcp set ryze '{"url":"https://connector.get-ryze.ai/mcp","transport":"streamable-http","auth":"oauth"}' openclaw mcp login ryzeSign in to Ryze AI from OpenClaw
Run: openclaw mcp login ryze. A browser opens on the Ryze AI page. Sign in if asked, choose the workspace that holds Shopify and click Allow connection, then start the Gateway again. An administrator can instead click Sign in for the ryze server under Settings > MCP.
Finish the sign-in on another machine if needed
If the browser is not on the machine that runs OpenClaw, approve the sign-in there and hand the code it returns to openclaw mcp login with the --code option.
Ask your first question
Once credentials exist, OpenClaw adds the server to the agent runtime. If you saved the connector before Shopify was connected in Ryze AI, remove the entry and save it again so the tool list refreshes. Then ask: Read my products and list the ones whose SEO title or description is empty.
The Ryze AI help center page for Shopify covers the Shopify side of the connection. OpenClaw does not have its own Ryze AI help page; the Ryze AI developers page covers the MCP URL for other clients.
Sources: OpenClaw MCP documentation, OpenClaw MCP transports, Ryze AI Shopify guide. OpenClaw pages checked November 15, 2026.
CLI, Control UI, openclaw.json and API key
OpenClaw CLI
set writes the server definition and login runs the OAuth flow; the credentials stay on the Gateway host. Start the Gateway again afterwards. To see what is saved, openclaw mcp show ryze, list and status print it, and they keep working while the Gateway runs.
openclaw gateway stop
openclaw mcp set ryze '{"url":"https://connector.get-ryze.ai/mcp","transport":"streamable-http","auth":"oauth"}'
openclaw mcp login ryzeControl UI: Settings > MCP
Open the MCP page of the Control UI (/settings/mcp, with /mcp as an alias), choose Add server under Configured servers, name it ryze, pick Streamable HTTP and paste the URL. OpenClaw's docs put the OAuth settings in the scoped config editor on that page, so set auth: "oauth" there and click Sign in. Adding a server needs administrator access. Inside a chat, + > Plugins > Add MCP server saves a server too.
openclaw.json
Edit ~/.openclaw/openclaw.json, which is JSON5, so comments and trailing commas are allowed. The Gateway watches the file and applies the change. Then sign in with openclaw mcp login ryze on a stopped Gateway, or use Sign in under Settings > MCP.
{
mcp: {
servers: {
ryze: {
url: "https://connector.get-ryze.ai/mcp",
transport: "streamable-http",
auth: "oauth",
},
},
},
}A Ryze AI API key instead of OAuth
If you want a Ryze AI API key in place of the browser sign-in, leave out auth: "oauth" and send the key as a bearer header. OpenClaw ignores static Authorization headers while auth: "oauth" is on. Keep the key in an environment variable: a ${RYZE_API_KEY} reference does not trigger the literal-value warning of openclaw doctor when the variable is set.
ryze: {
url: "https://connector.get-ryze.ai/mcp",
transport: "streamable-http",
headers: { Authorization: "Bearer ${RYZE_API_KEY}" },
}A remote entry takes the transport streamable-http or sse, and OpenClaw reads an entry with no transport as sse, so set streamable-http for this address. A request times out after 60 seconds by default, and listing the tools at session start gets 10 seconds when requestTimeoutMs is not set.
OpenClaw and MCP: the facts in one table
| Topic | What OpenClaw's documentation says |
|---|---|
| Where a server is added | Settings > MCP > Add server in the Control UI, + > Plugins > Add MCP server in a chat, openclaw mcp add or set in a terminal, or mcp.servers in ~/.openclaw/openclaw.json |
| Config file | ~/.openclaw/openclaw.json in JSON5, applied by the Gateway when the file changes |
| Transports | stdio for local commands, plus SSE and Streamable HTTP for addresses |
| Sign-in | auth: "oauth" on an HTTP entry, then openclaw mcp login with the Gateway stopped, or Sign in under Settings > MCP for an administrator |
| Whose account | One shared credential that the operator manages by default. Per-requester sign-in needs oauth.identity set to per-requester and gateway.publicOrigin set to an HTTPS origin |
| Approval | MCP tools follow OpenClaw's tool profiles and tool policy. Per-call prompts are documented for Codex runs only |
| Tool names | The agent sees <server>__<tool>, so the Ryze AI tools appear as shopify__read and so on |
| Plan | No paid tier; MIT licensed and self-hosted |
| Admin controls | Adding a server from a chat and signing in from Settings need administrator access. enabled: false keeps an entry and hides its tools |
Sources: OpenClaw MCP documentation, OpenClaw config extensions, OpenClaw MCP registry commands. Checked November 15, 2026.
Other clients
The same URL works in other MCP clients. Shopify is connected once in Ryze AI, so nothing changes on the Shopify side.
Claude Code
Claude Code registers the same URL with one claude mcp add command. How to connect Claude Code to Shopify.
Codex
Codex takes the connector URL through its own MCP settings. How to connect Codex to Shopify.
Claude and ChatGPT
Both add https://connector.get-ryze.ai/mcp as a custom connector. In ChatGPT it is an app under Settings > Apps. If the connector was added before Shopify was connected in Ryze AI, remove and re-add it so the tool list refreshes.
Shopify access and scope
Four things decide what OpenClaw can reach in your store.
- Which store
- The store you connected in Ryze AI. Several stores can sit in one workspace. The agent uses the primary store unless you name another, and the tools accept an optional connection_id.
- Which connection type
- The default Ryze AI Shopify app covers products, collections, pages, blogs, metaobjects, SEO fields and orders. Theme file edits, URL redirects and customer records need your own custom app, connected on the Custom app tab with your Client ID and Client secret.
- One shared sign-in
- By default OpenClaw's OAuth credential is shared and operator-managed, so everyone who talks to that agent works through the one Ryze AI sign-in behind it. Per-requester sign-in needs gateway.publicOrigin set to an HTTPS origin.
- What stands in front of a change
- No prompt is documented for each call in OpenClaw's built-in runtime. The controls are your tool policy and a toolFilter, described under the tools table below.
Access behind each action
What the Shopify tools can do depends on the scopes the store connection has. The table lists what Ryze AI documents for each connection type.
| Action in Ryze AI | Shopify access |
|---|---|
| Read products, collections, pages, blogs, metaobjects and SEO fields | Default Shopify app connection |
| Read orders | Default connection, last 60 days only; older orders need a custom app with the read_all_orders scope |
| Create and update product, collection, page and blog content and SEO fields | Default Shopify app connection |
| Edit theme files such as robots.txt or theme.liquid, and URL redirects | Your own custom app only |
| Customer records | Your own custom app with that scope only |
The 13 Shopify access scopes of the default connection
The default connection installs the Ryze AI Shopify app. On a test store that app held 13 Shopify access scopes on November 13, 2026. Here is the full list with what Shopify says each scope covers.
| Scope | What Shopify says it covers | With Ryze AI |
|---|---|---|
| read_products, write_products | Products, variants, collections and selling plans | Read and edit |
| read_content, write_content | Pages, blogs, articles and comments | Read and edit |
| read_metaobjects, write_metaobjects | Metaobjects | Read and edit |
| read_publications, write_publications | Publishing products and collections to sales channels | Read and edit |
| read_themes, write_themes | Online store themes. Shopify asks for an exemption on top of write_themes before an app may change theme files | Read. Theme file edits go through your own custom app |
| read_orders | Orders, fulfilments and abandoned checkouts created in the last 60 days | Read only |
| read_reports | ShopifyQL analytics queries | Read only |
| read_analytics | Analytics data. Shopify's current scope list does not describe this scope | Read only |
Left out of the list: read_customers, read_discounts, read_all_orders and write_orders. So customer records, discounts and orders older than 60 days need your own custom app, and order changes such as refunds are not available on the default connection.
Source: Shopify access scopes. Checked November 13, 2026.
Removing access
To cut OpenClaw off, stop the Gateway and run openclaw mcp logout ryze to delete the saved credentials, or openclaw mcp unset ryze to remove the entry. Setting enabled: false on the entry hides its tools and keeps the entry. To end the store access itself, disconnect the Shopify card in Ryze AI.
What OpenClaw can do in Shopify
The Ryze AI connector exposes 5 Shopify tools: two read, two write and one delete. Writes and deletes are separate tools, so a filter can treat them differently.
| Tool | Type | What it does |
|---|---|---|
| shopify__read | Read | Runs a read-only Shopify Admin GraphQL query against the connected store. What it returns depends on the scopes of the store connection. |
| shopify__search_content | Read | Searches one text field that the read tool can return, such as an article body, and returns matching lines with line numbers and surrounding context. |
| shopify__write | Write | Runs an Admin GraphQL mutation that creates or updates resources, such as productUpdate or metafieldsSet. Delete, remove, cancel and deactivate mutations are rejected here. |
| shopify__edit_content | Write | Makes find-and-replace edits inside one text field on the server in a single call, with optional JSON or Liquid validation before anything is written. |
| shopify__delete | Delete | Runs a destructive Admin GraphQL mutation that deletes, removes, cancels, deactivates, revokes or discards a resource, such as productDelete or tagsRemove. |
Some limits apply to every client, OpenClaw included. Full-catalog bulk exports (bulkOperationRunQuery) cannot be downloaded through the tools. Missing Admin API scopes are not worked around; the agent reports the missing scope. A store can be live in only one Ryze AI workspace at a time.
Approvals and keeping the agent read-only
OpenClaw's docs describe prompts before each MCP call for Codex runs only. In the built-in runtime, MCP tools follow the usual tool profiles and tool policy: the coding and messaging profiles include them, the minimal profile hides them, and tools.deny with bundle-mcp switches them all off. Inside a chat, + > Plugins > Tool access lets you turn off single tools for that session. The Ryze AI chat has its own Tool approvals picker that starts on Skip all approvals, and in Claude the write and delete tools can be set to Needs approval; neither applies inside OpenClaw.
To keep the agent from changing the store, hide the write and delete tools with a toolFilter on the entry. Names are exact or simple * globs. Run openclaw mcp doctor ryze --probe first to see the names OpenClaw reports.
ryze: {
url: "https://connector.get-ryze.ai/mcp",
transport: "streamable-http",
auth: "oauth",
toolFilter: {
exclude: ["*shopify__write", "*shopify__edit_content", "*shopify__delete"],
},
}This entry hides the three tools that change the store, so only the two read tools stay.
Limits in numbers
| Limit | Number |
|---|---|
| Shopify request budget | Counted in cost points, per app and per store: 100 points per second on standard plans, 200 on Advanced Shopify, 1,000 on Shopify Plus and 2,000 on Shopify for enterprise. |
| One query | At most 1,000 points, on every plan. |
| What things cost | An object costs 1 point and a change costs 10. A list costs more the more items you ask for. |
| Lists | An input list takes up to 250 items. Paging through a list stops at 25,000 objects. |
| After a throttle | Shopify recommends waiting one second before the next request. |
| Seen in the test | A development store had a budget of 2,000 points that refilled at 100 points per second. A Shopify Plus store had 20,000 points that refilled at 1,000 per second. Reading 17 products with their SEO fields cost 7 points. |
| Size of one tool call | The read tool accepts a query of up to 50,000 characters. |
| Orders | The last 60 days on the default connection. Older orders need a custom app with the read_all_orders scope. |
| OpenClaw request time | 60 seconds per MCP request by default, and 10 seconds to list tools at session start when requestTimeoutMs is not set. |
Sources: Shopify GraphQL Admin API rate limits, Shopify API limits. Checked November 13, 2026.
What the default connection can read, tested
Each row is one call to shopify__read on a Shopify development store on November 13, 2026, through the default connection, made from Claude Code. The cost is what Shopify charged against the store's budget of 2,000 points.
| What was asked | What came back | Cost in points |
|---|---|---|
| All products with SEO title and description | 17 products. 15 had both SEO fields empty and 2 had both filled | 7 |
| All collections with SEO title and description | 3 collections. All 3 had both SEO fields empty | 4 |
| Pages, blogs and blog articles | 2 pages, 1 blog and 0 articles | 15 |
| All products with every variant | 17 products with 26 variants. Shopify estimated 156 points and charged 5 | 5 |
| Number of orders | 0, as an exact count. The test store has no orders | 10 |
| The first inventory item | Returned | 3 |
| Themes | 3 themes, one of them live | 4 |
| The installed app and its access scopes | The app Ryze AI with 13 scopes | 3 |
| Customers | Refused with "Access denied for customers field." | 2 |
| Discounts | Refused. The app needs the read_discounts scope | 2 |
First 3 prompts to run
1. Find products with missing SEO fields
Read my Shopify products and list the ones whose SEO title or SEO description is empty. Show the product title and handle for each.
Tools used: shopify__read
What comes back: A list of product titles and handles with the empty SEO fields marked. Nothing is changed. On the test store this kind of read found 15 of 17 products with both fields empty.
2. Fix a phrase inside a long description
Search the description of the product with handle my-product-handle for the phrase old phrase and show me the matching lines. Then replace it with new phrase.
Tools used: shopify__search_content, shopify__edit_content
What comes back: The matching lines with line numbers, then a single in-place edit to that text field. If you hid the write tools with a toolFilter, the edit step is not offered.
3. Update a page or collection SEO title
Update the SEO title of my collection with handle my-collection-handle to the text I give you, and confirm the new value after the change.
Tools used: shopify__read, shopify__write
What comes back: A collection update through a write mutation, then a read of the field so you can compare it with what you asked for.
The first prompt matches a test that was run. The second and third change data, so this page describes what comes back and shows no result for them. Replace the handles and phrases with your own.
The queries behind the results
OpenClaw writes the query itself. This is the query behind the product read in the test table. Paste it into a prompt and ask your agent to run it with shopify__read.
Products with their SEO fields, 7 points on the test store:
query ProductsSeo {
products(first: 50, sortKey: TITLE) {
nodes { title handle status seo { title description } }
pageInfo { hasNextPage }
}
}The installed app and its access scopes, 3 points:
query Scopes {
currentAppInstallation {
app { title handle developerName }
accessScopes { handle }
}
}The search tool answers with line numbers, which is what makes a small edit safe. Searching one product description for the word snowboard returned a single match on line 1, in this shape:
{
"target": "shopify data.products.nodes.0.descriptionHtml",
"totalMatches": 1,
"truncated": false,
"matches": [ { "line": 1, "text": "...", "match": true } ]
}10 jobs to hand to OpenClaw
Ten jobs to give an OpenClaw agent, each with its Ryze AI tool. The first seven reads and searches were run in the test. The two that change the store were not.
| Job | Ask OpenClaw | Tool | Works on the default connection |
|---|---|---|---|
| SEO audit of products | List every product whose SEO title or SEO description is empty. | shopify__read | Yes |
| SEO audit of collections | List every collection with its SEO title and description, and mark the empty ones. | shopify__read | Yes |
| Content inventory | List my pages, blogs and blog articles with their handles, and say which are published. | shopify__read | Yes |
| Variant check | List every product with its variants and flag the products that have only a default variant. | shopify__read | Yes |
| Order count | How many orders does the store show? | shopify__read | Yes, for the last 60 days |
| Access check | Which Shopify access scopes does this connection have? | shopify__read | Yes |
| Find a phrase | Search the description of the product with handle my-product-handle for a phrase and show the matching lines. | shopify__search_content | Yes |
| Fix a phrase | Replace that phrase in the description and show me the line before and after. | shopify__edit_content | Yes, unless you filtered the tool out |
| Fill SEO fields | Set the SEO title and description of these products to the text I give you, then read them back. | shopify__write | Yes, unless you filtered the tool out |
| Discount list | List my active discount codes. | shopify__read | No. It needs a custom app with the read_discounts scope |
5 ways to connect OpenClaw to Shopify
There are five ways to give an OpenClaw agent access to Shopify. This guide treats the first, the Ryze AI connector, as the main way: it is a hosted address, so you run no extra process, create no Shopify app of your own and copy no store key. You approve the store once and save one address. The other four were checked on the dates in the sources and are listed with what each one needs.
| Way | Runs where | Setup in OpenClaw | What it reaches in the store | Price |
|---|---|---|---|---|
| Ryze AI connector (the main way) | Hosted. One address for every user | openclaw mcp set, the Control UI or openclaw.json, then openclaw mcp login ryze | Products, collections, pages, blogs, metaobjects and SEO fields, to read and to edit. Orders from the last 60 days, to read. Deletes go through a separate tool | Paid Ads is $89 per month with a 7-day free trial |
| Shopify AI Toolkit plugin | On your computer | openclaw plugins install npm:@shopify/ai-toolkit. Needs Node.js 18 or higher | Shopify's developer docs and API schemas through the Dev MCP server, which holds no store data. Its CLI connector part can reach store data from your own computer, but Shopify's CLI connector page names Claude Code, Codex, Cursor and Visual Studio Code, not OpenClaw | Shopify's pages state no price |
| Composio | Hosted | Remote MCP address https://connect.composio.dev/mcp, saved as a remote server in OpenClaw. Composio's own setup page documents Cursor, so the OpenClaw entry is the same address in OpenClaw's format and was not run | Composio lists 376 Shopify tools and 45 triggers | The free plan stops at 10,000 tool calls a month. Standard is $18 per seat per month |
| Zapier MCP | Hosted | Zapier gives you an MCP server tied to your Zapier account. Zapier's quickstart names other clients for setup, so the OpenClaw entry is a remote server you save yourself | The Shopify actions of your Zapier account | Each successful tool call uses two tasks from your Zapier plan |
| GeLi2001/shopify-mcp, open source | A Node process you run | A stdio entry that runs npx shopify-mcp with the Client ID and Client secret of your own Shopify custom app and your .myshopify.com domain. Needs Node.js 18 or higher | 31 tools for products, customers, orders, metafields, inventory and tags | Free, MIT licence. 239 GitHub stars, last update April 5, 2026 |
Options that do not fit this job
- Shopify's connectors for merchants. Shopify's help center lists a plugin or connector for ChatGPT, Claude, Gemini, Grok, Perplexity, Muse and Microsoft Copilot. OpenClaw is not on that list.
- Shopify's UCP servers at https://{shop}/api/ucp/mcp. They serve catalog search, cart and checkout to shopping agents and need an agent profile in every request. They do not edit a store. Shopify's migration page says the older Storefront MCP catalog and cart tools on https://{shop}/api/mcp were removed.
- ClawHub. OpenClaw's public plugin registry has no Ryze AI plugin, so the connector is saved by address as in the steps above.
Which one to pick
Ryze AI is the best way to connect OpenClaw to Shopify for store content and SEO work, with one caveat: theme files, URL redirects and customer records need your own custom app, and the full catalog cannot be exported in bulk. Install the Shopify AI Toolkit plugin as well when your agent writes Shopify apps or themes and needs the API schemas. Both can be enabled in one Gateway. Pick Composio or Zapier when your team already runs one of them for other apps. Choose the open-source server when you need order actions such as refunds or fulfilment and can keep a custom app of your own.
Sources: Shopify AI Toolkit, Shopify CLI connector, Shopify help center on AI tools, Shopify Storefront MCP migration, Composio Shopify toolkit page, Composio pricing, Zapier MCP quickstart, GeLi2001/shopify-mcp, OpenClaw ClawHub, Ryze AI Shopify guide. Shopify pages checked November 13, 2026, the Shopify AI Toolkit page again on November 19, 2026.
OpenClaw, Shopify and MCP: dates that matter
| Date | What happened |
|---|---|
| January 30, 2026 | OpenClaw 2026.1.29 renamed the npm package and the CLI to openclaw. |
| March 31, 2026 | OpenClaw 2026.3.31 added remote HTTP and SSE servers by URL under mcp.servers, with auth headers and an optional streamable-http transport. |
| April 22, 2026 | Shopify's Storefront Catalog MCP began to follow the Universal Commerce Protocol (UCP), with the tools search_catalog, lookup_catalog and get_product. The older search and lookup tools were kept until June 15, 2026. |
| June 24, 2026 | Shopify announced that the Storefront MCP cart tools give way to the UCP Cart MCP tools. The older cart tools were kept until August 31, 2026. |
| August 31, 2026 | OpenClaw 2026.8.1, also called OpenClaw 2.0, added servers from the chat composer and per-requester OAuth for shared MCP servers. |
| September 23, 2026 | OpenClaw 2026.9.6 let administrators sign in to MCP connectors from Settings. |
| October 27, 2026 | @shopify/dev-mcp 1.18.0 came out. It was still the newest version on November 13, 2026. |
| November 3, 2026 | OpenClaw 2026.10.10 began protecting MCP configuration while the Gateway runs. The commands openclaw mcp set and login now need the Gateway stopped. |
| November 10, 2026 | OpenClaw 2026.11.3 came out. On November 15, 2026 it was the newest stable release, and its notes list no MCP change. |
Sources: @shopify/dev-mcp versions on npm, Shopify changelog, April 22, 2026, Shopify changelog, June 24, 2026, OpenClaw releases, OpenClaw 2026.3.31 changelog, OpenClaw 2026.10.10 release notes. Checked November 15, 2026 and November 13, 2026.
How this guide was tested
Two sets of checks stand behind this guide: the connector and a Shopify store on November 13, 2026, and OpenClaw's documentation on November 15, 2026. The table lists what was run and what came back.
| What was run | What came back |
|---|---|
| The connector address, without signing in | A request to https://connector.get-ryze.ai/mcp came back as HTTP 401 with a WWW-Authenticate header that points to the sign-in details. OpenClaw's docs say a 401 on initialization shows up as authentication refused (401), and that this is what leads to the sign-in. |
| The tool list in a signed-in MCP client | Five Shopify tools, under the names in the tools table above. |
| shopify__read on a Shopify development store | One call returned all 17 products with their SEO title and description: 15 had both empty, 2 had both. |
| Cost of that call | Shopify counted 7 points, with 16 requested, against a budget of 2,000. |
| Nine more reads through the default connection | Seven worked and two were refused, as listed in the table of tested reads above. |
| shopify__search_content on one product description | One match with its line number. |
| Access scopes of the connection | The app Ryze AI with 13 scopes, listed above. |
| Calls made to fail on purpose | Three: a query that was too large, a field that does not exist and a change sent to the read tool. Their messages are in the errors table below. |
Not run for this page: every step inside OpenClaw. No Gateway was installed or started, no server was saved and no sign-in was attempted. The OpenClaw steps follow its documentation and changelog as read on November 15, 2026. The signed-in client for the tool list and the reads was Claude Code, which reaches the same server and the same five tools. The write and delete tools were not run, because they change the store.
OpenClaw and Shopify errors and fixes
Exact error messages
These are the exact messages Shopify and the connector returned in the test on November 13, 2026, plus one OpenClaw message taken from its documentation, which was not seen in a run.
| Message | What it means | What to do |
|---|---|---|
| authentication refused (401) | OpenClaw's docs say this appears in the startup log and catalog diagnostic when a Streamable HTTP server answers initialization with HTTP 401. The connector answers an unsigned request that way. | Run openclaw mcp login ryze with the Gateway stopped, or click Sign in under Settings > MCP. |
| Access denied for customers field. | The default connection does not ask Shopify for customer data. | Connect the store with your own custom app that has the read_customers scope. |
| Access denied for discountNodes field. Required access: Apps must have `read_discounts` access scope. | Discounts are outside the 13 scopes of the default connection. | Use a custom app with the read_discounts scope. |
| Query cost is 1729, which exceeds the single query max cost limit (1000). | One query asked for too much at once. In the test it asked for 250 products, 250 variants of each and 250 metafields of each variant. Shopify's code for this is MAX_COST_EXCEEDED. | Ask for fewer items per page, or split the question in two. |
| Field 'seoTitle' doesn't exist on type 'Product' | The assistant guessed a field name that Shopify does not have. The SEO fields sit under seo, as title and description. | Nothing was read or changed. Ask again, or tell the agent to use the seo field. |
| This is a write operation | A change was sent to the read tool. It refuses the call and names the write tool. | Let the agent repeat the call with shopify__write. |
Other problems
- The Shopify tools do not appear in OpenClaw
- Until shared credentials exist, OpenClaw leaves the server out of the agent runtime instead of failing the turn. Run openclaw mcp login ryze with the Gateway stopped, then check with openclaw mcp status or openclaw mcp doctor ryze --probe. If you saved the connector before Shopify was connected in Ryze AI, remove the entry and save it again.
- The tool list is empty or times out
- The tool list at session start gets 10 seconds when requestTimeoutMs is not set. Raise requestTimeoutMs on the entry, and confirm transport is streamable-http, because OpenClaw reads a missing transport as sse.
- The sign-in page opens on the wrong machine
- Approve it in the browser, then give the code it returns to openclaw mcp login ryze with --code.
- The API key is ignored
- Static Authorization headers are ignored while auth: "oauth" is on. Remove auth for the key route, or remove the header and use OAuth.
- An openclaw mcp command holds back
- Since OpenClaw 2026.10.10 (November 3, 2026), commands that change saved servers, and login, need the Gateway stopped. Stop it, run the command and start it again, or edit openclaw.json, or use Settings > MCP.
- Shopify does not accept the store domain
- Use the .myshopify.com domain, not your custom domain, on the Shopify app tab in Ryze AI.
- A theme file or redirect edit fails
- Theme file edits such as robots.txt or theme.liquid and URL redirects are not available on the default connection. Connect with your own custom app on the Custom app tab.
- Customer data is missing
- Customer records are not requested by the default connection. They need a custom app with that scope.
- Old orders are missing
- Orders older than 60 days stay hidden unless the custom app has the read_all_orders scope.
- The agent reports a missing scope
- Missing Admin API scopes are not worked around. Add the scope to your custom app, release and reinstall it, then retry.
- The store is already connected elsewhere
- A store can be live in only one Ryze AI workspace at a time. Disconnect it in the other workspace first.
- The tools reply that a subscription is required
- The Shopify tools need an active Ryze AI plan or free trial. Start the trial, then retry.
Terms on this page
- MCP
- The Model Context Protocol, an open standard for connecting AI applications to outside systems. OpenClaw, Claude and ChatGPT support it.
- Gateway
- The OpenClaw process that runs your agents and keeps their settings, MCP servers and saved sign-ins.
- openclaw.json
- The JSON5 settings file at ~/.openclaw/openclaw.json. MCP servers live under mcp.servers.
- Tool
- One action that an MCP server offers. The Ryze AI connector has five for Shopify.
- Access scope
- A named permission in Shopify, such as read_products. An app can do only what its scopes allow.
- Cost points
- Shopify's unit for how heavy a request is. A store gives each app a budget of points that refills every second.
- Development store
- A Shopify store made for testing. The results on this page come from one that holds Shopify's sample products.
Source for MCP: modelcontextprotocol.io. Checked November 15, 2026.
Frequently asked questions
How do I connect OpenClaw to Shopify?
Connect your store in Ryze AI under Integrations by entering the .myshopify.com domain and approving the prompt in Shopify admin. Then save https://connector.get-ryze.ai/mcp in OpenClaw as a streamable-http server with auth set to oauth, using openclaw mcp set, Settings > MCP or openclaw.json, and sign in with openclaw mcp login ryze.
Is there a Shopify MCP server for OpenClaw?
Yes. The Ryze AI connector is one: its address is https://connector.get-ryze.ai/mcp and it has 5 Shopify tools. Shopify's AI Toolkit plugin for OpenClaw adds the Dev MCP server, which has developer docs and API schemas but no store data.
What is the Shopify MCP server URL for OpenClaw?
For the Ryze AI connector the address is https://connector.get-ryze.ai/mcp, the same for every user. Shopify's Dev MCP server has no address: it runs on your computer. Shopify's shopping servers use https://{shop}/api/ucp/mcp, with your store domain in place of {shop}.
Does Shopify have an official MCP server?
Yes, several, for different jobs. The Dev MCP server gives coding tools Shopify's developer docs and API schemas. The UCP servers serve catalog, cart and checkout to shopping agents. For store management Shopify offers connectors for ChatGPT, Claude, Gemini, Grok, Perplexity, Muse and Microsoft Copilot, and a CLI connector for developers that names Claude Code, Codex, Cursor and Visual Studio Code.
Does the Shopify AI Toolkit work with OpenClaw?
Shopify's page lists OpenClaw and gives the install command openclaw plugins install npm:@shopify/ai-toolkit. The toolkit needs Node.js 18 or higher and brings the Dev MCP server for docs and schemas. That server holds no store data, so it does not replace the Ryze AI connector for reading or editing a store.
Which should I use, Ryze AI or the Shopify Dev MCP server?
Use the Ryze AI connector to read and edit a store. Use the Dev MCP server when your agent writes Shopify apps or themes and needs the API explained. It cannot read or change a store. Both can be enabled in one OpenClaw Gateway.
Is Shopify's Storefront MCP still available?
Shopify's documentation says the older Storefront MCP catalog and cart tools on https://{shop}/api/mcp were removed, and points to Universal Commerce Protocol servers at https://{shop}/api/ucp/mcp. Those serve shopping agents and need an agent profile in every request.
Can OpenClaw edit my Shopify products?
Yes. Through Ryze AI, an OpenClaw agent can create and update product, collection, page and blog content and SEO fields with the write tool, and edit part of a long text field with the edit tool. It cannot edit theme files or redirects on the default connection.
Can OpenClaw delete Shopify resources?
Only through the separate shopify__delete tool. The write tool rejects delete, remove, cancel and deactivate mutations. A toolFilter with an exclude list on the ryze entry hides the delete tool from the agent.
Does OpenClaw ask before it changes my store?
OpenClaw's docs describe per-call prompts for Codex runs only. In the built-in runtime, MCP tools follow tool profiles and policy. To require a pause before changes, hide the write and delete tools with a toolFilter and enable them only when you want a change made.
Which OpenClaw plan do I need?
None. OpenClaw is MIT licensed and self-hosted, and its docs say it has no paid tier. The model provider your agent uses has its own costs, which are outside this guide.
Do I need a Shopify custom app?
Not for the default connection, which uses the Ryze AI Shopify app and an approval in Shopify admin. You need your own custom app for theme file edits, URL redirects, customer records or orders older than 60 days.
Can I connect more than one Shopify store?
Yes. Several stores can be connected to one workspace, and the agent uses the primary store unless you name another one. A single store can be live in only one Ryze AI workspace at a time.
Why do the Shopify tools not show up in OpenClaw?
Until shared credentials exist, OpenClaw leaves the server out of the agent runtime. Run openclaw mcp login ryze with the Gateway stopped. If you connected Shopify in Ryze AI after saving the server, remove the ryze entry and save it again so the tool list refreshes.
How much does it cost to connect OpenClaw to Shopify?
Adding the connector costs nothing, but the Shopify tools need an active Ryze AI plan or free trial. Paid Ads is $89 per month with a 7-day free trial, SEO Starter is $129 per month with a 3-day free trial, Agency is $279 per month and Shopify CRO is $1,499 per month. Annual billing takes 30% off the first year.
How do I disconnect Shopify from OpenClaw?
Stop the Gateway and run openclaw mcp logout ryze to delete the saved credentials, or openclaw mcp unset ryze to remove the entry. To end the store access, disconnect the Shopify card in Ryze AI.