By Ira Bodnar, Ryze AI · Updated · Connector tested November 13, 2026
Quick answer
The main way to connect Antigravity to Shopify is the Ryze AI connector. Connect your store in Ryze AI by typing its .myshopify.com domain and approving the access prompt in Shopify admin, then give Antigravity's mcp_config.json a ryze entry whose serverUrl is https://connector.get-ryze.ai/mcp and finish the Ryze AI sign-in. The agent then has 5 Shopify tools: 2 that read, 2 that write and 1 that deletes.
- In Ryze AI open Integrations, click Connect on the Shopify card and approve the prompt in Shopify admin
- In Antigravity open MCP Servers, Manage MCP Servers, View raw config and add the ryze entry
- Complete the Ryze AI sign-in and click Allow connection
- Start a new agent chat and ask which products have an empty SEO title
Antigravity to Shopify at a glance
| Fact | Detail |
|---|---|
| Main way to connect | The Ryze AI connector: a hosted MCP server that Antigravity reaches through one serverUrl entry, with nothing to install or keep running |
| Server address | https://connector.get-ryze.ai/mcp |
| Where the entry goes | mcp_config.json, either ~/.gemini/config/mcp_config.json for every project or .agents/mcp_config.json inside one workspace. The IDE, the App and the CLI read the same format |
| Sign-in | Shopify: your .myshopify.com domain and an access prompt in Shopify admin, with no API keys. Antigravity: OAuth 2.0 with PKCE in the browser, with no client ID to type because the connector offers dynamic client registration. The App adds an Authenticate button and a code to paste back |
| Shopify tools | 5 in all: 2 read, 2 write and 1 delete, each with an optional connection_id |
| Can it change the store | Yes, on the default connection for products, collections, pages, blogs, metaobjects and SEO fields. Antigravity keeps any MCP tool without a rule in Ask mode, so each change waits for your click by default |
| Other data in the same chat | Google Ads, Meta Ads, GA4 and Search Console tools, among others, when those platforms are connected in the same Ryze AI workspace |
| Antigravity plan needed | None is named. Google's MCP page lists no plan, and the plans page gives every plan all product features |
| Ryze AI price | Adding the connector costs nothing. The tools need an active plan or 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 |
| Shopify's own option for Antigravity | The Shopify AI Toolkit plugin, installed in the Antigravity CLI with agy plugin install. It brings Shopify's developer docs and API schemas, and a CLI connector for store access from your own computer |
| Last tested | Connector checked and Shopify calls sent through it from Claude Code on November 13, 2026. Sign-in data compared with Antigravity's OAuth order on November 15, 2026. Nothing was run inside Antigravity |
Before you start
- Google Antigravity. Google's MCP documentation for Antigravity names no plan, and its FAQ says personal Google accounts can use Antigravity on any plan, the free tier included. The IDE, the App and the CLI read the same mcp_config.json format, so any of them works. Enterprise accounts cannot sign in to the standalone IDE: they use the App, the CLI or the IDE extensions, and an admin may first have to allow MCP servers in Gemini Enterprise.
- A Shopify store you can approve apps for. You need the store's .myshopify.com domain (not the custom domain) and a Shopify login that can approve the Ryze AI app's access prompt. To change theme files, URL redirects or customer records you need to create your own custom app in the Shopify Dev Dashboard instead.
- 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 is the plan for publishing Content Plan articles to the Shopify blog. Connecting is free, and the Shopify tools need an active plan or trial. Annual billing takes 30% off the first year.
How to connect Antigravity to Shopify
These steps are for the Antigravity IDE. Two happen in Ryze AI and Shopify, four in the editor. The App and the CLI use the same config entry and are covered below.
Connect Shopify in Ryze AI
Create a Ryze AI account or sign in, open Integrations and click Connect on the Shopify card. On the Shopify app tab type your .myshopify.com domain and click Continue.
Approve the access prompt in Shopify admin
Approve the prompt in your Shopify admin. You return to Ryze AI with the store connected and no API keys to copy. Optionally click View on the Shopify card to pick the blog that articles publish to and the article template.
Open the raw MCP config in the Antigravity IDE
In the agent side panel of the editor, click the ... menu at the top and select MCP Servers. Click Manage MCP Servers, then View raw config. This opens mcp_config.json. The global file is ~/.gemini/config/mcp_config.json and a per-workspace file is .agents/mcp_config.json.
Add the ryze entry
Under mcpServers add an entry named ryze with the serverUrl https://connector.get-ryze.ai/mcp and save the file. There is no client ID or secret to enter: Antigravity runs OAuth 2.0 with PKCE on its own for servers that support dynamic client registration, and the Ryze AI connector does.
Sign in to Ryze AI
Antigravity handles the browser sign-in itself, and Google's MCP page gives no IDE steps for how it begins. When the Ryze AI page comes up, choose the workspace that holds your Shopify store and click Allow connection.
Ask your first question
Open a new agent chat and ask: Which of my Shopify products have an empty SEO title or SEO description? Antigravity asks for approval before an MCP tool runs until you allow it, so approve the first call.
The Ryze AI help article for Shopify covers the Shopify side of the connection. There is no Ryze AI help page for Antigravity, and Ryze AI was not tested in it for this page.
Sources: Google's Antigravity MCP documentation, checked November 15, 2026, and the Ryze AI Shopify guide.
Antigravity App
The Antigravity App lists its MCP servers on the Customizations page and has an Authenticate button of its own, so signing in works differently from the IDE. Since App 2.30.0 there is one catch: in the Knowledge Work layout the Installed tab shows plugins only, and the MCP Servers section is not there. Switch to Software Engineering under Settings > General > Interface Layout before step 1. Business and enterprise accounts always get the Software Engineering layout.
- Click Customizations in the sidebar, then Installed, and scroll to MCP Servers.
- Click Copy Config File Path and add the ryze entry shown below to that mcp_config.json.
- Back in Customizations, Installed, MCP Servers, click Authenticate next to ryze.
- Complete the Ryze AI sign-in in the browser, copy the authorization code, paste it into Enter authorization code and click Submit. The server then reconnects by itself.
The entry to add is the same in the IDE, the App and the CLI:
{
"mcpServers": {
"ryze": {
"serverUrl": "https://connector.get-ryze.ai/mcp"
}
}
}The App's Add MCP Server (+) button opens a searchable catalog with no field for an address, so a custom server like this one is written into mcp_config.json by hand. Remote servers have to speak Streamable HTTP: Google's docs rule out the legacy HTTP+SSE transport and the httpUrl key, and accept url as another name for serverUrl. Antigravity's OAuth redirect URI is https://antigravity.google/oauth-callback.
Antigravity CLI
The Antigravity CLI (agy) loads the same two files. Put the ryze entry in ~/.gemini/config/mcp_config.json or in <workspace>/.agents/mcp_config.json, then type /mcp in the prompt panel. The MCP Manager that opens shows the status of each server, reloads the configuration and shows connection logs. Give the global and the workspace entry different names, because when two files use one name the server already running keeps it.
Google writes Authenticate steps for the App only. The CLI changelog refers to a sign-in link for MCP servers that use OAuth (version 1.5.2, November 6, 2026), but no Google page lists the steps, so this guide does not either. The changelog also names mcp add, remove, list, enable and disable subcommands for the user-level file; their exact syntax is unpublished, so no command line is given here. Tokens are kept in ~/.gemini/antigravity/mcp_oauth_tokens.json, where expired ones are refreshed and invalid ones removed.
Sources: Google's Antigravity MCP documentation, the Gemini CLI to Antigravity CLI update, the Gemini CLI migration page, the Antigravity changelog and the connector checks on this page. Checked November 15, 2026.
Antigravity and MCP: the facts in one table
| Topic | What Google's Antigravity pages say |
|---|---|
| Where MCP works | The MCP page covers the Antigravity App, the Antigravity CLI and the standalone IDE. The Visual Studio extension page documents the same two mcp_config.json files |
| Config format | One schema on every surface: an mcpServers map keyed by server name. An enabled plugin can bring servers in its own <plugin-root>/mcp_config.json |
| Local or remote | command starts a local stdio process, and serverUrl (or url) points at a remote server over Streamable HTTP. Each entry names exactly one of the two |
| Headers | A headers object on a remote entry sends extra HTTP headers, such as an Authorization bearer token or an API key |
| OAuth | Automatic for servers offering Client ID Metadata Documents or dynamic client registration. Antigravity tries oauth.clientId from the file first, a metadata document second and registration third |
| Approvals | MCP tools with no rule wait in Ask mode. Rules are written mcp(server/tool), mcp(server/*) or mcp(*), and Deny outranks Ask, which outranks Allow |
| Presets that stop asking | Turbo, in the App on a personal account, runs MCP tools without a prompt. In the CLI the default request-review prompts first, while always-proceed skips the prompt except where an ask or deny rule applies |
| Hiding tools | enabledTools keeps only the tools you list, disabledTools hides the ones you list, and disabled: true pauses a server without deleting its entry |
| Loading and output | Tools load lazily from schemas cached on disk unless a tool is marked eager. In the CLI a lazily loaded tool hands up to 10 KB of its result straight to the agent |
| Plan and enterprise | No plan is named for MCP. The standalone IDE is not supported for enterprise deployments, and admins can set MCP allowlists in Gemini Enterprise |
| Moving servers over | With the Software Engineering role at first launch, the App offers to import MCP servers, skills and rules from Claude Code, Codex, Cursor and Gemini CLI |
Sources: MCP, permissions, settings, plans, enterprise, getting started, Visual Studio extension and changelog pages of Google Antigravity. Checked November 15, 2026.
Other AI clients
The same URL works in other MCP clients. Shopify is connected once in Ryze AI, so nothing changes on the Shopify side.
Gemini
Google's other assistant has its own steps. See How to connect Gemini to Shopify. For the Antigravity client in general, see Ryze AI in Antigravity.
Claude Code and Codex
Both take the same URL from a terminal. See How to connect Claude Code to Shopify and How to connect Codex to Shopify.
Shopify access and permissions
Two sign-ins are involved: Shopify for store access and Ryze AI for the connector. Antigravity adds its own OAuth step on top, for the Ryze AI connector only. Four things decide what the agent can see and change.
- Which store
- The store you connected in Ryze AI. You can connect several stores to one workspace; the agent uses the primary store unless you name another one, and the tools accept an optional connection_id. A store can be live in only one Ryze AI workspace at a time.
- Which connection type
- The default Ryze AI Shopify app covers products, collections, pages, blogs, metaobjects, SEO fields and recent orders. Theme file edits, URL redirects and customer records need your own custom app, connected on the Custom app tab with a Client ID and Client secret from the Shopify Dev Dashboard.
- Read or write
- Reads and writes use separate tools, and deletes use a third. Shopify decides what a call may touch through the scopes of the installed app, so a missing scope is reported rather than worked around.
- How Antigravity signs in
- Antigravity tries a manually set oauth.clientId first, then a Client ID Metadata Document if the server supports one, then dynamic client registration. The Ryze AI connector advertises dynamic client registration and no metadata document, so the third path applies and you enter nothing.
The scopes of the default Shopify app
The default connection installs the Ryze AI Shopify app. On a test store that app held 13 Shopify access scopes on November 13, 2026, read with currentAppInstallation. Antigravity itself signs in to the connector only, with the scopes mcp:read and mcp:write from the connector's discovery data. This is the Shopify list, with what Shopify says each scope covers.
| Scopes on the default app | What Shopify says they cover | Access |
|---|---|---|
| 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, fulfillments 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 |
Shopify's scopes come in read and write pairs, and the default app holds both for products, content and metaobjects. The way to keep Antigravity to reading is a rule on the client side: leave the write and delete tools in Ask mode, or hide them with disabledTools in mcp_config.json.
When you need your own custom app
When the default app is not enough, Ryze AI accepts your own custom app. It is created in the Shopify Dev Dashboard with the App URL and redirect URL that the Ryze AI custom app guide lists (Embed app unchecked) and the Admin API scopes you pick, then released and installed. What it adds to the default connection:
| Need | What the custom app brings |
|---|---|
| Theme files such as robots.txt or theme.liquid | Possible with your own app. Ryze AI's help center does not offer it on the default connection |
| URL redirects | Possible with your own app |
| Customer records | Add the read_customers scope. The default connection answered a customers query with ACCESS_DENIED in the test |
| Discounts | Add the read_discounts scope. The default connection refused a discountNodes query in the test |
| Orders older than 60 days | Shopify's read_orders covers the last 60 days. Older orders need read_all_orders, which Shopify's scope page names for that purpose |
Not on the default list: read_customers, read_discounts, read_all_orders and write_orders. Customer records, discounts and orders older than 60 days therefore need your own custom app, and order changes such as refunds are not available on the default connection.
Sources: Shopify access scopes, the Ryze AI Shopify guide and the Ryze AI custom app guide, checked November 13, 2026. Scope list read on the test store of November 13, 2026.
Limits that shape the answers
These limits shape what comes back in prompts. The first three come from Ryze AI's documentation of the Shopify connection, the last three from Google's Antigravity MCP page.
| Area | Limit |
|---|---|
| Bulk exports | Full-catalog bulk exports (bulkOperationRunQuery) cannot be downloaded through the tools. |
| Missing scopes | Missing Admin API scopes are not worked around. The agent reports the missing scope. |
| One workspace per store | A store can be live in only one Ryze AI workspace at a time. |
| Timeouts | Antigravity waits up to 5 minutes for a server to connect and list its tools and up to 3 minutes for each tool call. The timeoutSeconds setting changes both. |
| Tool loading | MCP tools load lazily by default: schemas are cached on disk and the agent reads them when needed. |
| Tool approval | An MCP tool without a configured rule runs in Ask mode, so each call needs your approval until you allow it in the policy configuration. |
Sources: the Ryze AI Shopify guide and Google's Antigravity MCP documentation, checked November 15, 2026.
Removing access
To remove access, disconnect the store on the Shopify card in Ryze AI. In Antigravity, delete the ryze entry from mcp_config.json, or set disabled: true on it to pause the server and keep the entry. In the App, More actions (⋮) next to the server also offers Disable and Delete. Stored OAuth tokens live in ~/.gemini/antigravity/mcp_oauth_tokens.json.
What Antigravity can do in Shopify
The Ryze AI connector exposes 5 Shopify tools: 2 that read, 2 that write and 1 that deletes. Writes and deletes are separate tools, so you can approve them separately. All five take an optional connection_id, as seen in the tool definitions on November 13, 2026.
| 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. |
In Antigravity, an MCP tool with no configured rule runs in Ask mode, so every call waits for your approval. Google's docs give the rule forms mcp(server/tool) for one tool and mcp(server/*) for all tools on a server. Allow shopify__read and shopify__search_content if you like, and leave shopify__write, shopify__edit_content and shopify__delete in Ask mode, because they change a live store. In the Ryze AI chat, the Tool approvals picker starts on Skip all approvals; choose Approve write & delete (reads run freely, changes need approval) or Manual approve there. In Claude, the same tools can be set to Needs approval.
Shopify limits in numbers
Shopify meters its Admin GraphQL API in cost points, per app and per store. These figures come from Shopify's rate limit pages and from the cost data returned in the November 13 test. If you add the Shopify AI Toolkit or an open-source server, your own app's budget applies.
| Limit | Figure or rule | Who sets it |
|---|---|---|
| Request budget | 100 points per second on standard plans, 200 on Advanced Shopify, 1,000 on Shopify Plus and 2,000 on Shopify for enterprise | Shopify |
| One query | At most 1,000 points, whatever the plan | Shopify |
| What things cost | An object costs 1 point, a mutation 10, a connection is sized by its first and last arguments, and scalars cost 0 | Shopify |
| Lists | Input arrays hold up to 250 items. Paging through arrays of objects stops at 25,000 objects | Shopify |
| After a throttle | Shopify recommends a one-second backoff | Shopify |
| Orders | read_orders covers orders created within the last 60 days. read_all_orders is needed for older ones | Shopify |
| Seen in the test | A development store had 2,000 points that refilled at 100 per second, and a Shopify Plus store 20,000 that refilled at 1,000 per second. Reading 17 products with their SEO fields was charged 7 points | Shopify, measured |
| Ryze AI tool input | shopify__read accepts a query of up to 50,000 characters | Ryze AI |
| Tool output in the CLI | Up to 10 KB of a lazily loaded tool's result goes to the agent directly | Antigravity |
Sources: Shopify GraphQL Admin API rate limits, Shopify API usage limits and access scopes, checked November 13, 2026. Ryze AI tool input and the measured budgets from the test of November 13, 2026. The CLI figure from the Antigravity changelog, checked November 15, 2026.
Shopify calls tested through the connector
On November 13, 2026 the Ryze AI connector took these Shopify calls from Claude Code, on the default connection to a Shopify development store that holds Shopify's sample snowboard catalog. Antigravity was not the client, but it talks to the same server and the same tools. 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 with 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 | 10 |
| The first inventory item | Returned | 3 |
| Themes | 3 themes, one with the role MAIN | 4 |
| The installed app and its access scopes | The app Ryze AI with 13 scopes | 3 |
| Customers | Refused with ACCESS_DENIED | 2 |
| Discounts | Refused with ACCESS_DENIED | 2 |
shopify__search_content was also run on the description of one product for the word snowboard and returned 1 match, on line 1. The write and delete tools were not run.
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.
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 one in-place edit to that text field once you approve the tool call in Antigravity.
3. Fill SEO fields for a collection
Set the SEO title and SEO description of the collection with handle my-collection to the text below, then read them back to confirm.
Tools used: shopify__write, shopify__read
What comes back: A single update to the collection, then a read of the saved fields. The call waits for your approval in Ask mode.
These prompts describe what comes back and show no sample results, because the answers come from your own store. Replace the handles and phrases with your own. The prompts that change data run on a live store.
10 jobs to hand to Antigravity
Ten jobs to hand the Antigravity agent, each with the tool that does the work. The rows marked as run were sent through the connector from Claude Code on November 13. The two that change the store were not run.
| Job | Ask the agent | Tool | Works on the default connection |
|---|---|---|---|
| SEO audit of products | List every product whose SEO title or SEO description is empty. | shopify__read | Yes. It ran in the test |
| SEO audit of collections | List every collection with its SEO title and description, and mark the empty ones. | shopify__read | Yes. It ran in the test |
| Content inventory | List my pages, blogs and blog articles with their handles. | shopify__read | Yes. It ran in the test |
| Variant check | List every product with its variants and flag the products that have only a default variant. | shopify__read | Yes. It ran in the test |
| Order count | How many orders does the store show? | shopify__read | Yes, for the last 60 days. It ran in the test |
| Access check | Which Shopify access scopes does this connection have? | shopify__read | Yes. It ran in the test |
| 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. It ran in the test |
| Fix a phrase | Replace that phrase in the description and show me the line before and after. | shopify__edit_content | Yes, after you approve the call in Antigravity. Not run in the test |
| 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, after you approve the call in Antigravity. Not run in the test |
| Discount list | List my active discount codes. | shopify__read | No. It needs a custom app with the read_discounts scope |
5 ways to connect Antigravity to Shopify
Five ways can give the Antigravity agent access to a Shopify store. This guide treats the first, the Ryze AI connector, as the main way: Antigravity stores one serverUrl entry, the Shopify approval happens once inside Ryze AI, and there is no Shopify app of your own, terminal command or key to set up. The other four were read on their own pages on November 13, 2026, and none of them was installed for this guide. The setup column shows how each one would go into Antigravity.
| Way | Runs where | Setup in Antigravity | What it reaches in the store | Price |
|---|---|---|---|---|
| Ryze AI connector (the main way) | Hosted by Ryze AI. One address for Antigravity, Claude, ChatGPT and other MCP clients | A ryze entry with serverUrl https://connector.get-ryze.ai/mcp in mcp_config.json, then the browser sign-in. In the App, Authenticate and a pasted code | 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 | Free to add. The tools need an active plan or trial: Paid Ads $89 per month with a 7-day free trial |
| Shopify AI Toolkit plugin, from Shopify | On your computer | In the Antigravity CLI run agy plugin install https://github.com/Shopify/shopify-ai-toolkit. Needs Node.js 18 or higher | Two parts. The Dev MCP server gives the agent Shopify's developer docs and API schemas, runs locally with no authentication and holds no store data. The Shopify CLI connector can read and change store data through the Shopify API, limited by the access you grant | Shopify's page states no price |
| Composio | Hosted by Composio | A serverUrl entry for https://connect.composio.dev/mcp, then Composio's authorization in the browser. Composio's pages read here show the Cursor steps, so the Antigravity entry is an adaptation and was not checked | 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 by Zapier | Add the MCP URL Zapier generates as a serverUrl entry and sign in. Zapier turns on actions for the apps already connected to your Zapier account. Antigravity was not checked on Zapier's pages | The Shopify actions of your Zapier account. Zapier's Shopify page lists 20 triggers and 38 actions | Each successful tool call uses two tasks from your Zapier plan |
| GeLi2001/shopify-mcp, open source | A Node process you run | A command entry in mcp_config.json 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 |
Shopify's CLI connector page names Claude Code, Codex, Cursor and Visual Studio Code as supported tools, and Antigravity is not on that list, although the plugin repository has an agy install command on the Dev MCP page. Shopify also publishes a separate Dev MCP server package, @shopify/dev-mcp, version 1.18.0 of October 27, 2026, which runs as npx -y @shopify/dev-mcp@latest and serves developer docs only. The Ryze AI connector and the toolkit can share one Antigravity setup under different names.
Options that do not fit Antigravity
- Shopify's connectors for merchants. Shopify's help center lists a plugin or connector for ChatGPT, Claude, Gemini, Grok, Perplexity, Muse and Microsoft Copilot. Antigravity 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, and the older Storefront MCP catalog and cart tools on https://{shop}/api/mcp were removed.
- Antigravity's MCP Store and Plugin Marketplace. The IDE installs catalog servers from its MCP Store, and the App and CLI from the Plugin Marketplace that opened on October 29, 2026. Google's MCP page lists 77 MCP Store servers, and Ryze AI is not one of them. This guide did not check either catalog for a Shopify entry.
Which one to pick
Ryze AI is the best way to connect Antigravity to Shopify for store content and SEO work from one hosted address that the IDE, the App and the CLI share, with caveats: the tools need a Ryze AI plan once the trial ends, theme files, URL redirects and customer records need your own custom app, and the full catalog cannot be exported in bulk. Add the Shopify AI Toolkit when you are writing a Shopify app or theme and want the agent to know the API schemas. Composio and Zapier make sense when your team already uses one of them for other apps. The open-source server suits you when you need order actions such as refunds or fulfillment and can keep a custom app of your own.
Sources: Shopify AI Toolkit and Dev MCP, Shopify CLI connector, Shopify connectors for AI tools, Storefront and UCP MCP, @shopify/dev-mcp, Composio Shopify, Composio pricing, Zapier MCP for Shopify, Zapier MCP quickstart and GeLi2001/shopify-mcp, checked November 13, 2026. Antigravity setup and catalogs from the Antigravity MCP documentation, checked November 15, 2026.
Shopify, Antigravity and MCP: dates that matter
| Date | Event |
|---|---|
| March 20, 2025 | Shopify published the first version of its Dev MCP server, @shopify/dev-mcp 1.0.0. |
| November 18, 2025 | Google Antigravity shipped as an AI-powered IDE, version 1.11.2. The launch entry does not mention MCP. |
| 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. |
| May 19, 2026 | Google released the Antigravity App and the Antigravity CLI and began moving Gemini CLI users to the new CLI. |
| June 24, 2026 | Shopify announced that the Storefront MCP cart tools give way to the UCP Cart MCP tools, kept until August 31, 2026. |
| October 2, 2026 | Antigravity CLI 1.2.15 fixed sign-in to MCP servers whose client registration answers HTTP 200 instead of 201. |
| October 27, 2026 | @shopify/dev-mcp 1.18.0 came out. It was still the newest version on November 13, 2026. |
| October 29, 2026 | The Plugin Marketplace opened in the Antigravity App and CLI. |
| November 6, 2026 | Antigravity CLI 1.5.2 fixed MCP OAuth sign-ins that failed with Invalid PKCE code_verifier when the server reconnected during the sign-in. |
| November 9, 2026 | Antigravity App 2.30.0 brought the Knowledge Work layout, which hides the MCP Servers list, and an import of MCP servers from Claude Code, Codex and Cursor. |
| November 13, 2026 | Antigravity CLI 1.5.8 stopped signing users out of OAuth servers without a client secret once an access token expired. |
Sources: @shopify/dev-mcp on the npm registry, Shopify changelog on Catalog MCP and UCP and on the cart tools, checked November 13, 2026; Antigravity changelog, Google Developers Blog, May 2026 and Antigravity blog, October 2026, checked November 15, 2026.
How this guide was tested
Two dates stand behind this guide. On November 13, 2026 the connector was checked and Shopify calls went through it from Claude Code on a development store. On November 15 the connector's sign-in data was compared with the OAuth order in Google's Antigravity docs.
| Check | Result |
|---|---|
| Connector address without a sign-in, November 13 | 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. |
| The connector's two discovery files, November 13 | Both loaded. They name the authorize, token and register endpoints, the authorization code and refresh token grants, PKCE with S256, and two scopes: mcp:read and mcp:write. |
| Sign-in data against Antigravity's client order, November 15 | A register endpoint is listed, Client ID Metadata Documents are marked unsupported and clients without a secret are accepted. Antigravity's third route, dynamic client registration, is therefore the one that applies. |
| The resource value Antigravity checks, November 15 | The protected resource file for the /mcp path names https://connector.get-ryze.ai/mcp, the match Antigravity requires. The file at the root names the host without /mcp, and Google does not say which of the two Antigravity reads. |
| Tool list in a signed-in client, November 13 | 5 Shopify tools under the names in the tools table: 2 read, 2 write, 1 delete. |
| Reads on the development store, November 13 | Ten calls through the default connection: eight returned data and two were refused, as listed in the table of tested calls. |
| 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 guide: anything inside Google Antigravity. The IDE, the App and the CLI were not opened, and no Ryze AI sign-in was completed from them, so the setup, sign-in and approval steps follow Google's Antigravity documentation as read on November 15, 2026. The Shopify calls came from Claude Code, which talks to the same server. The write and delete tools were not run, because they change the store.
Antigravity and Shopify errors and fixes
Exact messages from the test
These are the exact messages Shopify and the connector returned in the test on November 13, 2026. If the Antigravity agent shows one of them, this is what it means.
| Message | What it means | What to do |
|---|---|---|
| Access denied for customers field. | The default connection does not ask Shopify for customer data (ACCESS_DENIED). | 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 (ACCESS_DENIED). | 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 (MAX_COST_EXCEEDED). | Ask the agent to fetch fewer items per page, or to 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 with invalid_arguments and names the write tool. | Let the agent repeat the call with shopify__write and approve it when Antigravity asks. |
Other problems
- The server never finishes connecting
- Antigravity waits up to 5 minutes for a server to connect and list its tools. Check that mcp_config.json is valid JSON, that the entry uses serverUrl (or url) and not httpUrl, and reload the configuration.
- Authenticate does nothing in the App
- Complete the Ryze AI sign-in in the browser, copy the authorization code it shows, paste it into Enter authorization code and click Submit.
- The MCP Servers section is missing in the App
- The App is in the Knowledge Work layout, whose Installed tab lists plugins only. Open Settings > General > Interface Layout and pick Software Engineering.
- The Shopify tools do not appear
- If Shopify was connected in Ryze AI after the server was added, remove the ryze entry and add it again, then start a new chat so the tool list refreshes.
- 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 or old orders are missing
- Customer records are not requested by the default connection, and orders older than 60 days stay hidden unless a 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.
- Every tool call asks for approval
- That is Antigravity's Ask mode for MCP tools without a rule. Allow chosen tools in the policy configuration, using the mcp(server/tool) form.
- The tools say 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 through which an assistant such as Antigravity calls tools on outside servers.
- mcp_config.json
- The file where Antigravity keeps its MCP servers, one global and one per workspace, in the same format on every surface.
- Admin GraphQL API
- Shopify's API for reading and changing store data. The read and write tools send queries and mutations to it.
- 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.
- Custom app
- An app you create in the Shopify Dev Dashboard and connect to Ryze AI with its Client ID and Client secret, to reach what the default app does not.
- Ask mode
- Antigravity's default for an MCP tool that has no rule: each call waits until you approve it.
Sources: Shopify access scopes, GraphQL Admin API rate limits, checked November 13, 2026; Antigravity MCP documentation, checked November 15, 2026.
Frequently asked questions
How do I connect Antigravity to Shopify?
Connect your store in Ryze AI: open Integrations, click Connect on the Shopify card, type your .myshopify.com domain and approve the prompt in Shopify admin. Then add a ryze entry with the serverUrl https://connector.get-ryze.ai/mcp to Antigravity's mcp_config.json and complete the Ryze AI sign-in.
Is there a Shopify connector for Antigravity?
The Ryze AI connector at https://connector.get-ryze.ai/mcp is one. It is hosted and goes into mcp_config.json as a single serverUrl entry. Shopify's own help center lists connectors for other assistants but does not name Antigravity, and Shopify's AI Toolkit has an install command for the Antigravity CLI.
Does Shopify have an MCP server I can use in Antigravity?
Shopify publishes the Dev MCP server, which runs on your computer and serves developer docs and API schemas with no store data, and it ships inside the Shopify AI Toolkit plugin, which has an Antigravity CLI install command. For store data and edits you need a connector such as Ryze AI, Composio, Zapier MCP or an open-source server.
What is the Antigravity Shopify MCP URL?
The URL is https://connector.get-ryze.ai/mcp. Put it in the serverUrl field of a ryze entry in ~/.gemini/config/mcp_config.json or in .agents/mcp_config.json, then complete the sign-in. The same address works for every platform connected in your Ryze AI workspace.
Where is the Antigravity MCP config file?
The global file is ~/.gemini/config/mcp_config.json and a workspace file is .agents/mcp_config.json. In the IDE, open the ... menu in the agent panel, then MCP Servers, Manage MCP Servers and View raw config.
Which Antigravity plan do I need for MCP?
No particular plan: Google's Antigravity MCP documentation names none, and the plans page gives every plan all product features. The setup works the same in the IDE, the App and the CLI, apart from how the sign-in starts.
Does Antigravity need a client ID for the Ryze AI connector?
No. Antigravity runs OAuth 2.0 with PKCE and registers itself with servers that support dynamic client registration, which the Ryze AI connector does. The redirect URI is https://antigravity.google/oauth-callback.
Can Antigravity change my Shopify store?
Yes, on the default connection it can create and update product, collection, page and blog content and SEO fields, through shopify__write and shopify__edit_content. Antigravity keeps those tools in Ask mode until you allow them, so each change waits for your approval by default.
Can Antigravity delete products or pages?
Only through the separate shopify__delete tool, which runs destructive mutations such as productDelete. Leave it in Ask mode, or hide it with disabledTools in mcp_config.json, and review each call.
Can it read customers, discounts or old orders?
Not on the default connection. In the test, customers and discountNodes queries were refused, and orders cover only the last 60 days. Connect your own custom app with the read_customers, read_discounts or read_all_orders scope for those.
Can I connect more than one Shopify store?
Yes. Several stores can sit in one workspace, one of them marked as primary. The agent uses the primary store unless you name another one, and each tool accepts an optional connection_id. A store can be live in only one Ryze AI workspace at a time.
Does the Antigravity CLI work with the connector?
The CLI reads the same mcp_config.json files, and /mcp opens the MCP Manager to check status and reload. Its changelog mentions a sign-in link for OAuth servers, but Google lists no CLI sign-in steps, so this guide gives none, and the Ryze AI connector was not tested inside Antigravity.
How much does it cost?
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, and Agency is $279 per month. Annual billing takes 30% off the first year.
How do I disconnect?
Delete the ryze entry from mcp_config.json, or disconnect the store on the Shopify card in Ryze AI.