By Ira Bodnar, Ryze AI · Updated · Connector tested November 13, 2026
Quick answer
The main way to connect Grok to Shopify is the Ryze AI connector. Link the store to Ryze AI with its .myshopify.com address and approve the request in Shopify admin. Then open grok.com/connectors, choose New Connector and Custom, paste https://connector.get-ryze.ai/mcp and log in to Ryze AI when Grok asks. Grok then holds 5 Shopify tools for that store.
- Ryze AI: Integrations, Connect on the Shopify card, then type the .myshopify.com address
- Shopify admin: approve the access request for the Ryze AI app
- grok.com/connectors: New Connector, Custom, paste the connector URL
- Ryze AI page: log in, pick the workspace, press Allow connection, then open a Grok chat
Grok to Shopify at a glance
| Fact | Detail |
|---|---|
| Main way to connect | Ryze AI's hosted MCP connector, which Grok takes by URL as a custom connector |
| Address to paste | https://connector.get-ryze.ai/mcp, the same for every account |
| How Grok signs in | After the URL, Grok asks you to finish authentication. You log in on the Ryze AI page and press Allow connection |
| Shopify tools in Grok | 5 in total: shopify__read and shopify__search_content read, shopify__write and shopify__edit_content change content, shopify__delete removes |
| Can Grok change the store | Yes, through the two write tools and the delete tool. xAI describes no confirmation step on grok.com; Grok Bot shows an approval card when Auto Review wants your OK, and Grok Build asks first by default |
| Other data in the same Grok chat | Google Ads, Meta Ads, GA4 and Search Console tools from the same address, once those accounts sit in the same Ryze AI workspace |
| Grok plan | xAI makes connectors available to all Grok users. On The X Subscription, Grok Bot comes with Premium, Super and Ultra, and Plus and Free leave it out |
| Ryze AI price | Free to add. The tools run on a plan or trial, starting with Paid Ads at $89 a month and a 7-day free trial |
| Shopify's own option for Grok | Shopify's help center lists a Shopify connector for Grok. Its overview page does not say what that connector reads or changes |
| Store access of the default connection | 13 Shopify access scopes, without read_customers, read_discounts, read_all_orders or write_orders |
| Last tested | Connector checked November 13, 2026, with Shopify calls sent from Claude Code. No step was run inside Grok |
Before you start
- A Grok account, Grok Bot or Grok Build. xAI says connectors are available to all Grok users, and its connectors page names no separate plan for custom MCP servers. On Grok Business and Enterprise an admin has to add the connector in console.x.ai before members can use it. Grok Bot is its own app that logs in with a Cursor account; Premium, Super and Ultra on The X Subscription include it, while Plus and Free do not.
- Rights to approve an app on the store. The default connection raises an access request inside Shopify admin, so use a staff login that may install apps. Ryze AI asks for the .myshopify.com address, which differs from the custom domain shoppers see.
- An active Ryze AI plan or trial. Adding the connector is free, yet the five Shopify tools answer only on a plan or trial. Paid Ads: $89 a month, 7-day free trial. SEO Starter: $129 a month, 3-day free trial, and it publishes Content Plan articles to a Shopify blog. Agency: $279 a month. Shopify CRO: $1,499 a month. Paying yearly cuts 30% off the first year.
How to connect Grok to Shopify on grok.com
Steps 1 and 2 take place in Ryze AI and Shopify admin, steps 3 to 5 in Grok. Every account pastes the same address.
Connect the store in Ryze AI
Log in to Ryze AI or create an account, go to Integrations and press Connect on the Shopify card. The Shopify app tab asks for the store's .myshopify.com address; type it and press Continue.
Approve the request in Shopify admin
Shopify opens an access request for the Ryze AI app inside your admin. Approve it, and Shopify returns you to Ryze AI with the store marked as connected. At no point do you copy an API key.
Add a custom connector on grok.com
Open grok.com/connectors, press New Connector and pick Custom. Paste https://connector.get-ryze.ai/mcp as the server URL. xAI accepts only servers its own systems can reach over the public internet, and this address is one of them.
Log in to Ryze AI and allow the workspace
Grok then asks you to complete authentication. On the Ryze AI page, log in, select the workspace that holds the store and press Allow connection.
Ask Grok about the store
xAI says Grok discovers the tools a new connector offers and makes them available in conversations. Open a chat and try: List the five Shopify products I updated most recently, with the title, status and SEO title of each.
On authentication, xAI's connectors page says no more than to complete whatever is required once the URL is in. A second xAI page, on tunneling, says OAuth or API key flows for a custom server run inside Grok. No xAI page mentions dynamic client registration. The log-in and Allow connection screens belong to Ryze AI, as the Ryze AI help center Grok page shows them, and they were not run on grok.com for this guide. Grok's tool list can lag behind Ryze AI: when the store was linked later than the connector, delete the connector, create it again and start a fresh chat.
Grok Business, Grok Bot and Grok Build
Three more places take the same address. The Shopify approval lives in Ryze AI, so none of them sends you back to Shopify admin.
Grok Business and Enterprise (admin)
Team plans put one step at the front: an admin registers the connector in xAI's console. xAI ties adding and removing connectors to Team Read-Write permissions, which admins usually hold.
- Log in at console.x.ai, choose the team, then open Grok Business and Connectors. One xAI page calls the same menu Grok Enterprise.
- Press + Add Connector, choose Other and paste https://connector.get-ryze.ai/mcp.
- Finish whatever authentication the console asks for.
- xAI's page tells members to link their own accounts at grok.com/connectors after a catalog connector is added. The custom server steps stop at authentication, so confirm with your admin how members reach it.
Grok Bot
Grok Bot is a desktop and phone app of its own, apart from grok.com, and it logs in with a Cursor account. According to the Ryze AI help center, Ryze AI is one of the built-in apps on Grok Bot's Connect apps screen. Ryze AI appears nowhere in xAI's documentation, and nobody checked that screen for this guide, so the steps come from the Ryze AI help center.
- Open Connect apps in the Grok Bot sidebar. In the phone app, tap your avatar in the top left corner and choose Connect apps.
- In the box labeled Search across apps and skills, enter Ryze AI. Open the entry whose developer line reads Ryze AI and press Add.
- A browser tab opens on Ryze AI. Log in, pick the workspaces and press Allow connection.
- Once Authorization complete shows, press Open Grok Bot or Return to Grok Bot.
- Start a new chat. Typing @ lets you attach the app to the task.
No Ryze AI result in the search? The desktop app has a manual route at the foot of Connect apps, Add a custom connector. Give it a name, pick Remote HTTPS as the Type, put the connector URL in Server URL and press Add plugin. xAI also lets you ask a Bot to add the URL. Afterwards xAI suggests checking the Installed list. An app you connect is tied to your account, which means all of your Bots can use the store. If an older hand-added copy of Ryze AI is still installed, the Ryze AI help center says to uninstall it to avoid a double set of tools.
Grok Build CLI
Grok Build, xAI's coding agent for the terminal, registers a remote server with one command.
- Run the command below in a terminal.
- On first use of the server, a browser opens for the Ryze AI sign-in. Finish it there.
- In the terminal interface, /mcps (alias /connectors) opens the MCP tab. Select the ryze server and press i to authenticate it.
grok mcp add --transport http ryze https://connector.get-ryze.ai/mcpGrok Build stores the OAuth tokens in ~/.grok/mcp_credentials.json and namespaces tools as <server>__<tool>, so the five Shopify tools sit under the ryze server name. When no browser can open the sign-in page, /mcps shows its URL in a panel you can copy, a change from release V1.0.74.
Grok and MCP: the facts in one table
xAI (its documentation now names the company SpaceXSI) runs three products that take MCP servers, each with its own rules. Read across a row to compare them.
| Question | grok.com and team admins | Grok Bot | Grok Build |
|---|---|---|---|
| Where the address goes | New Connector, then Custom, at grok.com/connectors. On team plans an admin first uses + Add Connector, then Other, in the console | The Connect apps screen; for a server outside the catalog, the desktop form or a Bot asked to add it | The command grok mcp add, or a server table written into config.toml under ~/.grok |
| Transports | A public URL. Grok turns down localhost and private network addresses. xAI's tunneling notes mention SSE and Streamable HTTP servers | Remote HTTPS by URL. Command servers start on the cloud machine the Bot works on | HTTP by URL (the settings reference says HTTP/SSE), or stdio for a command on your machine |
| Sign-in | Whatever authentication the server needs, finished in Grok | Provider login in a browser tab, to be done in roughly 10 minutes. Cursor's connector backend keeps the tokens | Browser login on first use, with tokens saved in mcp_credentials.json under ~/.grok |
| Approval before a call | xAI describes none; tools are used when a question touches the service | Auto Review is on from the start and shows a card (Allow once, Always allow, Deny) for actions it wants you to OK | Ask is the starting mode. Allow and deny rules can name MCP tools through the MCPTool filter, and deny wins |
| Plan | Connectors are open to all Grok users | Premium, Super or Ultra on The X Subscription, not Plus or Free | The MCP page names no plan |
| Managing a server later | Back on grok.com/connectors. If a server address changes, delete the old connector and create a new one | Click the connected count next to the Connect apps heading. Each app has Reconnect and Remove, and its tools can be turned off one by one | /mcps: Space switches a server on or off, x deletes it. From the shell, grok mcp remove |
Sources: xAI's Grok connectors, custom MCP tunneling, connector management, Grok Bot apps, Grok Bot approvals, Grok Bot plans, Grok Build MCP servers and Grok Build permissions, checked November 14, 2026. Ryze AI steps: the Ryze AI help center Grok page.
What Grok can reach in Shopify
Grok holds no Shopify credential at any point. Ryze AI keeps the store connection, and three choices there decide what Grok can touch.
- The default Ryze AI app
- You type the .myshopify.com address and approve one access request in Shopify admin. Ryze AI refreshes the tokens itself, and you never paste a key.
- Your own custom app
- For wider access, open the Custom app tab and enter the store address plus the Client ID and Client secret from a Shopify Dev Dashboard app you build yourself. The Ryze AI help center gives the App URL and redirect URL to use, with Embed app left unchecked. Pick the Admin API scopes you want, then release the app and install it.
- Which store Grok works on
- One workspace can hold several stores. The starred primary store is used unless you name another one in the chat, and a store connects to one Ryze AI workspace at a time.
Ryze AI documents what each connection type covers. Shopify's access request lists the exact scopes before you approve.
| Area | Access |
|---|---|
| Products, collections, pages and blogs | Read and change, SEO title and description included, on the default app |
| Metafields and metaobjects | Read with shopify__read and change with shopify__write, as far as the connection's scopes reach |
| Orders | Readable for the last 60 days on the default app. Anything older needs a custom app holding read_all_orders |
| Theme files and URL redirects | Out of reach on the default app. A custom app of your own covers them |
| Customer records | The default app does not request them. A custom app with that scope does |
| Bulk exports | Results of bulkOperationRunQuery cannot be downloaded through the tools, so large reads go page by page through the Admin API |
The 13 Shopify access scopes of the default connection
Behind the default connection sits the Ryze AI Shopify app. A currentAppInstallation query on a development store on November 13, 2026 returned 13 access scopes for it. The middle column follows Shopify's access scope page as read that day.
| Scope | Shopify objects it covers | What Grok gets through Ryze AI |
|---|---|---|
| read_products, write_products | Products, variants, collections, selling plans and resource feedback | Read and change |
| read_content, write_content | Articles, blogs, comments and pages | Read and change |
| read_metaobjects, write_metaobjects | Metaobjects | Read and change |
| read_publications, write_publications | Publication fields and the mutations that publish to sales channels | Read and change |
| read_themes, write_themes | Online store themes. Shopify also wants an exemption before an app may change theme files | Read. Theme file edits go through your own custom app |
| read_orders | Orders, fulfillments, order transactions and abandoned checkouts created in the last 60 days | Read only |
| read_reports | ShopifyQL queries through shopifyqlQuery | Read only |
| read_analytics | Not described in Shopify's current scope list | Read only |
Missing from the list: read_customers, read_discounts, read_all_orders, write_orders. In practice, through the default connection Grok cannot open customer records, see discounts, look back past 60 days of orders, or alter an order. A custom app you own, given the right scope, opens up customers, discounts or the older orders.
Source: Shopify's access scopes, checked November 13, 2026. Connection types: the Ryze AI Shopify guide and the Ryze AI custom app guide.
Removing access
To take the store away from Grok, remove the connector: delete it at grok.com/connectors, or have the team admin delete it in the console. Grok Bot users press Remove on the app; Grok Build users type grok mcp remove ryze. Ending Ryze AI's own access to the store takes one more step: press disconnect on its Shopify card, or remove the app from Shopify admin.
What Grok can do in Shopify
Through Ryze AI, Grok gets 5 Shopify tools: two that read, two that change content and one that deletes. Every call runs as the connected store, inside the scopes that connection holds.
| Tool | Type | What it does |
|---|---|---|
| shopify__read | Read | Sends a read-only query to the Shopify Admin GraphQL API for the connected store. Its manifest covers products and variants, collections, orders, metafields and metaobjects, themes, pages, blogs and SEO fields; what actually returns depends on the connection's scopes. |
| shopify__search_content | Read | Looks inside a single text field the read tool can fetch, such as a blog article body, and answers with the matching lines, their line numbers and the lines around them. |
| shopify__write | Write | Sends an Admin GraphQL mutation that creates or updates something, for example productUpdate or metafieldsSet. It turns away any delete, remove, cancel or deactivate mutation. |
| shopify__edit_content | Write | Applies find-and-replace edits to one text field on the server in a single call, and can validate the result as JSON or Liquid before saving it. |
| shopify__delete | Delete | Handles destructive mutations, any that delete, remove, revoke, cancel, discard or deactivate, productDelete and tagsRemove among them. |
Whether Grok pauses before a change depends on the product, as the table of Grok facts above shows. xAI describes no approval step on grok.com, so a line such as wait for my yes is an instruction to the model. The chat inside Ryze AI is separate: its Tool approvals picker starts on Skip all approvals, and Approve write & delete or Manual approve make that chat ask first. Scheduled tasks run without an approval step.
Shopify API limits
Shopify meters Admin API use per app and per store with a leaky bucket, counted in query cost points for the GraphQL Admin API, and spent capacity comes back at a restore rate. After a rejected request Shopify advises queuing, caching and backoff. Ryze AI adds limits that hold in every client, Grok included: bulkOperationRunQuery exports cannot be downloaded through the tools, a missing Admin API scope is reported and never worked around, and a store sits in one Ryze AI workspace at a time.
Limits in numbers
| Limit | Figure | Set by |
|---|---|---|
| Request budget per app and store | Points per second: standard plans 100, Advanced Shopify 200, Shopify Plus 1,000, Shopify for enterprise 2,000 | Shopify |
| Most one query may cost | 1,000 points, whatever the plan | Shopify |
| Point prices | Objects 1 point, mutations 10, scalars nothing; a connection scales with its first or last argument | Shopify |
| Lists | 250 items in one input array, 25,000 objects reachable by paging | Shopify |
| Wait after a throttled request | One second, Shopify's recommended backoff | Shopify |
| Budgets seen in the test | A development store: 2,000 points, refilling at 100 per second. A Shopify Plus store: 20,000, refilling at 1,000 per second | Shopify, as returned on November 13, 2026 |
| Length of one read query | Up to 50,000 characters in shopify__read | Ryze AI tool definition, seen November 13, 2026 |
| Grok Bot connector that stops answering | Times out after three minutes, per the release note of August 12, 2026 | xAI |
| Grok Build timeouts | 30 seconds for a server to start, 6,000 seconds per tool call; both are defaults | xAI |
Sources: Shopify GraphQL Admin API rate limits, Shopify API limits and Shopify access scopes, checked November 13, 2026; Grok Bot apps, Grok Bot changelog and Grok Build MCP servers, checked November 14, 2026.
What the default connection read in the test
Ten shopify__read calls went through the Ryze AI connector on November 13, 2026, on the default connection, to a development store holding Shopify's sample snowboard catalog. Claude Code sent them; it uses the same address as Grok. Points are what Shopify took from the store's 2,000-point budget.
| Query sent | Answer | Points |
|---|---|---|
| Every product with SEO title and description | 17 products. Blank SEO title and description on 15; both filled on 2, The Complete Snowboard and The Hidden Snowboard | 7, of 16 requested |
| Every collection with its SEO fields | 3 collections: Home page, Automated Collection and Hydrogen. None had either SEO field filled | 4 |
| Pages, blogs and articles | 2 pages, 1 blog, no articles | 15 |
| Every product with all its variants | 17 products and 26 variants. Shopify estimated 156 points and charged 5 | 5 |
| Order count (ordersCount) | 0, given as an exact count | 10 |
| Inventory, first item only | Returned one item | 3 |
| Themes in the store | 3, one of them the live theme | 4 |
| currentAppInstallation | The Ryze AI app with its 13 scopes | 3 |
| customers(first: 1) | Refused: no access to the customers field | 2 |
| discountNodes(first: 1) | Refused: the app lacks read_discounts | 2 |
First 3 prompts to run
Each prompt says what to ask Grok. Answers come from your own store; the tested reads above show what the read tool returned on a sample store.
1. Spot products with blank SEO fields
Read the 20 Shopify products I updated most recently. For each, give the title, handle, SEO title and SEO description, and flag any product where one of the SEO fields is blank.
Tools used: shopify__read
What comes back: A product table with both SEO fields, followed by the products where either field is blank. The store is not changed.
2. Swap one phrase in a long description
Look through the description of my-product (that is the handle) for free shipping and quote each line where the phrase appears. Leave the text alone until I answer yes and give you the new wording.
Tools used: shopify__read and shopify__search_content, then shopify__edit_content once you agree
What comes back: The lines that match, with line numbers and the text around them. After your yes, a single replacement is written and the rest of the description stays as it was.
3. Check a collection before rewriting its SEO
Show the title, description, SEO title and SEO description of the collection with handle summer. Suggest an SEO title under 60 characters and an SEO description under 155, and save them only after I say yes.
Tools used: shopify__read, then shopify__write once you agree
What comes back: The values as they stand, Grok's two suggested values and, after you confirm, the response of the collection update.
Put real handles from your store in place of my-product and summer. On grok.com the yes in prompts 2 and 3 is an instruction to Grok, since xAI describes no approval step there, so keep it in every prompt that edits.
10 jobs to hand to Grok
Ten jobs to give Grok, each with the Ryze AI tool behind it. Calls of the kind behind jobs 1 to 8, and the refusal in job 10, ran on the development store on November 13, 2026, from Claude Code. Job 9 changes the store and was not run.
| Job | What to ask Grok | Tool | On the default connection |
|---|---|---|---|
| Product SEO gaps | Which of my products have a blank SEO title or SEO description? | shopify__read | Works |
| Collection SEO gaps | Show each collection with its SEO title and description and mark the blank ones. | shopify__read | Works |
| Content list | List my pages and blogs, and the articles in each blog, with their handles. | shopify__read | Works |
| Variant review | Count the variants of each product and name the products that have only one. | shopify__read | Works |
| Live theme | Which themes does the store have, and which one is live? | shopify__read | Works for reading. Theme file edits need a custom app |
| Access check | Which Shopify access scopes does the Ryze AI app hold on this store? | shopify__read | Works |
| Recent orders | How many orders came in over the past 30 days? | shopify__read | Works inside the 60-day window |
| Phrase finder | In the description of a product I name, find each line that mentions free shipping, with its line number. | shopify__search_content | Works |
| SEO fill-in | Write SEO titles for the products with blank ones, show them to me, and save them after I say yes. | shopify__write | Covered by write_products. Not run here, since it changes the store |
| Customer list | Show my ten newest customers. | shopify__read | No; read_customers is missing, so connect a custom app |
2 ways to connect Grok to Shopify
Two ways to give Grok a Shopify store are named for Grok on their vendor's own pages. The Ryze AI connector is this guide's main way, because one public address goes into grok.com, Grok Bot and Grok Build, the store is approved once in Shopify admin and nothing has to run on your computer. The second way is Shopify's own connector for Grok, which Shopify's help center lists by name. Six more options follow the table. None of their pages gives Grok steps, and the ones that run on your computer cannot go into grok.com, though Grok Build does start local command servers.
| Way | Works in | How to add it in Grok | Store data it reaches | Cost |
|---|---|---|---|---|
| Ryze AI connector (the main way) | grok.com (added on the web), Grok Business and Enterprise, Grok Bot, Grok Build | A custom connector with https://connector.get-ryze.ai/mcp at grok.com/connectors, after an admin adds it on team plans. Grok Bot: Connect apps per the Ryze AI help center, or a Remote HTTPS custom connector. Grok Build: grok mcp add --transport http. Then the Ryze AI sign-in | Products, variants, collections, pages, blogs, metaobjects and SEO fields to read and change. Orders from the last 60 days, read only. Deletes in their own tool. No customers, discounts, theme file edits or redirects on the default app | Connector free. Paid Ads $89 per month, 7-day free trial |
| Shopify connector for Grok | Shopify's list says Grok and names no single Grok product | Not covered here. Shopify's overview page names the connector, and its setup page was not opened for this guide | Not stated on Shopify's overview page, which does not say what each connector reads or changes | Not stated on the overview page |
Six Shopify options that do not fit Grok
- Shopify AI Toolkit plugin, with the Dev MCP server inside. The install lines Shopify prints cover Claude Code, Codex, Antigravity CLI, Cursor, VS Code and OpenClaw; there is none for Grok. Its Dev MCP server (npx -y @shopify/dev-mcp@latest) answers from developer docs and API schemas, needs no sign-in, runs locally and sees no store data. On grok.com a local server cannot be added at all, because the form wants a public address.
- Shopify CLI connector. Built for developers working on a store from their own machine, it lets an AI tool read and change store data within the access granted. The assistants Shopify's help center names for it are Claude Code, Codex, Cursor and Visual Studio Code.
- Shopify's UCP servers (https://{shop}/api/ucp/mcp). These are for shopping agents: catalog search, carts, checkout and ask_business, with an agent profile required on every request. Store editing is not part of them. Shopify's migration page adds that the old Storefront MCP catalog and cart tools at https://{shop}/api/mcp are gone.
- Composio. Its remote address is https://connect.composio.dev/mcp, it says it manages OAuth and token refresh for you, and for Shopify it counts 376 tools and 45 triggers. The only Composio Shopify page in this research is the one written for Cursor, and Grok is absent from it.
- Zapier MCP. Whatever Shopify actions your Zapier account has become tools, at two Zapier tasks for each call that succeeds. Zapier's quickstart lists Cursor among popular MCP clients and scripts installs for Claude Code, Cursor and GitHub Copilot CLI. Grok gets no mention.
- GeLi2001/shopify-mcp, open source. MIT license, no charge, a Node process with 31 tools, order actions such as refunds and fulfillment included. It runs on the credentials of a custom app you create. The README's examples are a claude mcp add command and a JSON mcpServers block; Grok is not mentioned.
Which one to pick
Ryze AI is the best way to connect Grok to Shopify for reading and editing product, collection, page and blog content and SEO fields from grok.com, Grok Bot or Grok Build, with one caveat: on the default app, customer records, theme files and URL redirects stay out of reach until you add a custom app of your own, and the tools offer no bulk export of a whole catalog. Anyone who prefers a route run by Shopify should read Shopify's page on its Grok connector, which this guide neither opened nor tested. The default Ryze AI connection cannot change orders, as write_orders is not among its scopes; GeLi2001/shopify-mcp has order tools, refunds included, though its README gives no Grok setup.
Sources: Shopify help center on AI tools, Shopify AI Toolkit, Shopify CLI connector, Shopify Storefront MCP migration, Composio Shopify toolkit, Zapier MCP quickstart, Zapier Shopify MCP and GeLi2001/shopify-mcp, checked November 13, 2026; xAI Grok connectors and Grok Build MCP servers, checked November 14, 2026. Ryze AI side: the Ryze AI Shopify guide.
Shopify and Grok: dates that matter
| Date | What happened |
|---|---|
| March 20, 2025 | Version 1.0.0 of @shopify/dev-mcp, Shopify's Dev MCP server, appeared on npm. |
| February 2, 2026 | xAI became part of SpaceX, which announced the deal that day. xAI's docs now print the name SpaceXSI. |
| April 22, 2026 | Storefront Catalog MCP switched to the Universal Commerce Protocol, offering search_catalog, lookup_catalog and get_product. Shopify kept the earlier search and lookup tools running to June 15, 2026. |
| May 6, 2026 | Connectors arrived in Grok on the web, iOS and Android. The launch post also brought Bring Your Own MCP, the custom server option. |
| May 25, 2026 | Grok Build opened as an early beta for SuperGrok and X Premium Plus subscribers; the launch post said MCP servers work out of the box. |
| June 24, 2026 | Shopify deprecated the Storefront MCP cart tools in favor of UCP Cart MCP, with the old tools kept until August 31, 2026. |
| August 11, 2026 | Grok Bot launched as a beta. |
| October 2, 2026 | With release V0.67.0, Grok Bot's Marketplace screen took the name Connect Apps. |
| October 12, 2026 | The X Subscription began, bundling Grok, Grok Bot, Cursor and X Premium into one plan. |
| October 27, 2026 | Shopify released @shopify/dev-mcp 1.18.0, which was still current on November 13, 2026. |
| November 2, 2026 | Grok Bot reached 1.0. Grok Build V1.0.74, out that day, puts an MCP sign-in URL in the /mcps panel when no browser opens. |
Sources: @shopify/dev-mcp on the npm registry, Shopify changelog, April 22, 2026 and June 24, 2026, checked November 13, 2026; xAI news on SpaceX, Grok connectors, Grok Build, Grok Bot, The X Subscription and Grok Bot 1.0, and the Grok Bot and Grok Build changelogs, checked November 14, 2026.
How this guide was tested
Everything tested for this guide happened on November 13, 2026, in two parts: the connector's public address and its sign-in metadata, then Shopify calls through the connector against a development store. Claude Code sent those calls; Grok sent none.
| What was run | What came back |
|---|---|
| Unauthenticated request to https://connector.get-ryze.ai/mcp | Status 401. Its WWW-Authenticate header pointed to where the sign-in details live. |
| Both discovery files of the connector | They loaded and listed endpoints named authorize, token and register; two grant types, authorization code and refresh token; PKCE using S256; and two scopes, mcp:read and mcp:write. |
| shopify__read, ten times, default connection | Data on eight calls, a refusal on two. The tested reads table has each query, its answer and its cost, including the 13 scopes and the 7-point product SEO read. |
| shopify__search_content: the word snowboard in the-complete-snowboard's description | A single hit, line 1. |
| Calls that ended in an error | Five. Two were the refused reads; the others were a query priced above 1,000 points, a field Shopify does not know and a mutation aimed at the read tool. See the errors table for the wording. |
Nothing was tried inside Grok itself. No connector went into grok.com, the xAI console, Grok Bot or Grok Build, so the Grok steps rest on xAI's pages as they read on November 14, 2026, and the Grok Bot catalog steps on the Ryze AI help center. Nobody searched Grok Bot's Connect apps for Ryze AI. Claude Code was the stand-in client, on the same connector address. The three tools that change the store, shopify__write, shopify__edit_content and shopify__delete, were not called, and Shopify's own Grok connector was not tested.
Errors and fixes
Exact error messages from the test
Each message below is copied exactly from the test of November 13, 2026. Grok may repeat one of them to you; the other two columns say why it happened and what to try.
| Message | Cause | Next step in Grok |
|---|---|---|
| Access denied for customers field. | The default app never asked Shopify for read_customers, so customer data is closed to it. | Reconnect with a custom app that has read_customers and repeat the question. |
| Access denied for discountNodes field. Required access: Apps must have `read_discounts` access scope. | read_discounts is not among the default app's 13 scopes. | Move the store to a custom app that includes read_discounts. |
| Query cost is 1729, which exceeds the single query max cost limit (1000). | Code MAX_COST_EXCEEDED: one query wanted 250 products, each with 250 variants, each with 250 metafields. | Tell Grok to fetch fewer items per page or to break the request into two. |
| Field 'seoTitle' doesn't exist on type 'Product' | Code undefinedField: the query named a field that does not exist. Shopify keeps SEO data in seo, with title and description inside. | No data was touched. Repeat the request and name the seo field. |
| This is a write operation | shopify__read was handed a mutation; it declines and names the write tool. | Have Grok resend the change through shopify__write, and accept the prompt if Grok Bot or Grok Build shows one. |
Other problems
- The Shopify tools are missing in Grok
- Linked the store in Ryze AI only after adding the connector? Delete the connector in Grok, create it again and start a fresh chat.
- grok.com will not save the connector
- Grok only takes servers it can reach on the public internet, which the Ryze AI address is, so look for a typo in https://connector.get-ryze.ai/mcp. Team plans need an admin to add it in console.x.ai before anyone else can.
- Grok Bot shows Ryze AI as Disabled by team admin
- Grok Bot applies the team's Cursor connector policy, and that policy blocks the app. Ask your Cursor team admin to turn it on.
- The same tools appear twice in Grok Bot
- Two copies are installed, the built-in Ryze AI app and an earlier hand-added server. Uninstall the hand-added one.
- Ryze AI rejects the Shopify domain
- Ryze AI wants the address ending in .myshopify.com, shown in Shopify admin. A shop's public domain is refused.
- Grok cannot reach theme files, redirects or customers
- These sit outside the default Ryze AI app. Reconnect the store from the Custom app tab with an app of your own that carries the needed scopes.
- Orders older than 60 days are missing
- Sixty days is all read_orders allows. Reaching further back takes a custom app holding read_all_orders.
- Grok reports a missing scope
- No workaround exists on the Ryze AI side. Give your custom app the scope, release and reinstall it, then repeat the request.
- The store is connected in another workspace
- Each store connects to a single Ryze AI workspace at a time, so disconnect it in the other workspace before trying again.
- The tools say a subscription is required
- Without an active Ryze AI plan or free trial the Shopify tools stay locked. Begin the trial, then ask Grok again.
- Grok Build cannot open the sign-in page
- From V1.0.74 the /mcps panel prints the sign-in URL. Press c to copy it and paste it into a browser.
Terms on this page
- Custom connector
- Grok's name for an MCP server you add yourself by URL, outside its built-in list and its catalog.
- MCP
- The Model Context Protocol, an open standard that lets AI apps call tools on outside systems. grok.com, Grok Bot and Grok Build all accept MCP servers.
- Admin GraphQL API
- Shopify's API for running a store. The Ryze AI read, write and delete tools send their queries and mutations to it.
- Access scope
- A named Shopify permission such as read_products. An app reaches only what its scopes allow.
- Query cost
- Shopify's points for how heavy a request is. Each app gets a budget per store that refills every second.
- Development store
- A test store that Shopify provides for developers. Every tested read on this page ran against one stocked with Shopify's sample snowboards.
- Connect apps
- Grok Bot's screen for adding apps and skills. It was called Marketplace until release V0.67.0 of October 2, 2026.
Sources: Shopify's access scopes and rate limits, checked November 13, 2026; xAI's Grok connectors and the Grok Bot changelog, checked November 14, 2026.
Frequently asked questions
What is the best way to connect Grok to Shopify?
Ryze AI is the best way to let Grok read and edit live Shopify store content, with one caveat: the default app stops at content and SEO fields, so theme files, redirects and customer records call for a custom app of your own. Shopify lists a connector of its own for Grok, untested here, and its Dev MCP server is a local helper for app and theme code that never reads a store.
How do I connect Grok to Shopify?
First link the store in Ryze AI: type the .myshopify.com address and approve Shopify's prompt in your admin. On grok.com/connectors pick New Connector, then Custom, and enter https://connector.get-ryze.ai/mcp. Finish by logging in to Ryze AI, choosing the workspace and pressing Allow connection.
What is the Shopify MCP URL for Grok?
The Ryze AI connector lives at https://connector.get-ryze.ai/mcp, a single address shared by every account, and it goes into grok.com/connectors as a custom connector. Shopify's Dev MCP server has no URL since it runs on your own computer, while Shopify's UCP servers at https://{shop}/api/ucp/mcp are meant for shopping agents.
Is there a Shopify connector for Grok?
Yes, Shopify's help center names a Shopify connector for Grok in its list of connectors for merchants. That overview gives no detail on what the connector reads or changes, and this guide did not test it. The steps on this page cover the Ryze AI connector.
Does Shopify have its own MCP server?
Yes, several, each built for something else. @shopify/dev-mcp, the Dev MCP server, hands coding tools Shopify's docs and API schemas; it runs locally, skips sign-in and never reads a store, and the AI Toolkit that packages it lists Claude Code, Codex, Antigravity CLI, Cursor, VS Code and OpenClaw but not Grok. The UCP servers are for shopping agents. For merchants, Shopify's help center lists connectors or plugins for ChatGPT, Claude, Gemini, Grok, Perplexity, Muse and Microsoft Copilot.
Which MCP servers work with Shopify in Grok?
Two options name Grok: the Ryze AI connector, usable on grok.com, in Grok Bot and in Grok Build, and Shopify's connector for Grok. On the pages checked for this guide, Composio, Zapier MCP, GeLi2001/shopify-mcp and Shopify's AI Toolkit leave Grok out.
Is there an MCP that gives Grok my Shopify and Meta Ads data together?
Yes. When Shopify and Meta Ads are connected in the same Ryze AI workspace, one connector address serves both sets of tools, along with Google Ads, GA4 and Search Console. A single Grok chat can then pull store figures and ad figures.
Do I need a paid Grok plan?
Not on grok.com, where xAI opens connectors to every Grok user. Business and Enterprise teams need an admin to add the connector first. Grok Bot is another matter: it ships with Premium, Super and Ultra on The X Subscription and is left out of Plus and Free.
Do I need a paid Ryze AI plan?
Adding the connector costs nothing; running the Shopify tools takes a plan or free trial. Prices: Paid Ads $89 a month with 7 free days, SEO Starter $129 a month with 3 free days, Agency $279 a month, Shopify CRO $1,499 a month. A yearly plan saves 30% in the first year.
What can Grok do in my Shopify store through Ryze AI?
Five tools cover it: read-only Admin GraphQL queries, a search inside one text field, mutations that create or update, find-and-replace edits within a text field, and delete mutations when you ask.
Can Grok delete products or pages?
Yes, with shopify__delete, which sends mutations like productDelete, while the write tool turns deletes away. On grok.com xAI describes no confirmation, so ask Grok to hold off until you say yes. Grok Bot raises an approval card when Auto Review wants your OK, and Grok Build asks by default.
Can Grok edit theme files or customers?
The default Ryze AI app does not allow it. Theme files, URL redirects and customer records open up once you connect your own custom app with those scopes on the Custom app tab.
Does this work in Grok Bot and Grok Build?
Yes. For Grok Bot, the Ryze AI help center says to add Ryze AI from Connect apps; if it is not listed, the desktop app's custom connector form takes Remote HTTPS and the connector URL. Grok Build users run grok mcp add --transport http ryze https://connector.get-ryze.ai/mcp and complete the browser login.
Can I connect more than one Shopify store?
Yes. On the Shopify card in Ryze AI, press View and then Add one more account. The store with the star is primary and used by default, and every store belongs to one workspace at a time.
How do I disconnect Grok from Shopify?
Delete the Ryze AI connector at grok.com/connectors, press Remove on the app in Grok Bot, or run grok mcp remove ryze in Grok Build. Disconnecting the store on its Shopify card in Ryze AI, or uninstalling the app in Shopify admin, ends Ryze AI's access too.