SpritesAdd Sprites to Google Antigravity
Available on Antigravity 2.0, Antigravity IDE, Antigravity CLI and the Antigravity SDK. You need a Sprites account with Shopify already connected — the connector acts on that connection, so Google Antigravity never handles a Shopify credential.
Open the shared MCP config
All four Antigravity surfaces read one file. In the IDE, click … at the top of the agent side panel, choose MCP Servers, then Manage MCP Servers, then View raw config. The file itself is ~/.gemini/config/mcp_config.json, or .agents/mcp_config.json inside a workspace.
Antigravity IDE…MCP ServersManage MCP ServersView raw configAdd Sprites with serverUrl
Antigravity requires serverUrl for any remote connection. Its documentation is explicit that the url and httpUrl keys other clients use are not supported here, and an entry using them is skipped rather than reported.
~/.gemini/config/mcp_config.json{ "mcpServers": { "sprites": { "serverUrl": "https://mcp.sprites.ai/mcp" } } }Sign in
Antigravity registers itself with the Sprites authorization server automatically and completes the flow at its own callback. Save the file, reopen Manage MCP Servers, and connect.
Spriteswants access on behalf of Antigravity- Read your connected ad accounts and site data
- Draft campaigns, creatives and pages for your approval
- Apply only the changes you approve
AllowCancelUse it from any surface
Because the configuration is shared, the CLI and the SDK pick up the same server with no second step. Name the surface you are on when you follow an instruction — the products differ even though the config does not.
Run the first prompt
Ask Google Antigravity this. It routes to a Sprites door, which reads your Shopify account and answers — no account to name, no confirmation to give first.
- With Sprites, which products are profitable after ad cost this month?
- Ask Sprites to list every product in the summer collection with price and inventory.
- Use Sprites to create a collection page for "gifts under $50" and draft it in Shopify.
- Have Sprites rewrite the 20 worst-converting product descriptions.
- With Sprites, build Meta creative from our three best-selling SKUs.
Reopen Manage MCP Servers; Sprites is listed with its tool count, and the same entry is live in the CLI.
What Google Antigravity can do with Shopify
The same doors, whichever client you are in. One MCP configuration shared by the IDE, the CLI, the SDK and Antigravity 2.0, so the connector is added once and every surface has it.
Profit after ad cost, per product
The join nobody does by hand: store revenue against what Google, Meta and TikTok spent to get it.
Read the whole catalogue
Every product, variant and collection — uncapped, filterable, and grep-ready when you want to work on it.
Publish collection pages
Real pages in the store, with metadata and internal links, arriving as a draft to approve.
Refresh product copy at scale
Descriptions rewritten against what converts, proposed as a set you review before it lands.
Creative from real products
Ads built from the actual catalogue — price, variant, image — rather than a model's guess at your range.
Store blog without a second tool
Posts drafted into the Shopify blog through the same connector as everything else.
How approvals work here
Google Antigravity renders tool results as text, so a Shopify change comes back written out rather than as a card. Nothing is applied until you approve it, and the approval waits for you in Sprites — open it there and the same run continues.
What it reads
- Products, variants, collections, inventory and pricing
- Orders, revenue and sessions
- Store pages, blog posts and their metadata
- The ad spend attributable to each, from the connected ad accounts
What it can change
- Collection and landing pages, and store blog posts
- Product descriptions and page metadata
- Nothing touches the storefront without an approval
When it does not work in Google Antigravity
Three things go wrong in this client specifically, and each has a one-line fix.
The server is in the file but never appears.
It is almost certainly using url or httpUrl. Antigravity supports neither for remote servers; the key is serverUrl.
The IDE sees Sprites and the CLI does not.
A workspace .agents/mcp_config.json only applies inside that workspace. Put the entry in ~/.gemini/config/mcp_config.json to share it across surfaces.
Sign-in loops.
Antigravity completes OAuth at its own callback URL. Allow the browser redirect back to antigravity.google rather than cancelling it.
Shopify and Google Antigravity: questions
Which URL do I paste into Google Antigravity?
https://mcp.sprites.ai/mcp. There is one endpoint and every client uses it — every OAuth grant is bound to exactly that address, so a variant of it will not be honoured.
Can Google Antigravity change my Shopify account without asking?
Google Antigravity renders tool results as text, so a Shopify change comes back written out rather than as a card. Nothing is applied until you approve it, and the approval waits for you in Sprites — open it there and the same run continues.
Do I need a Shopify API key or developer token?
No. Shopify is connected once inside Sprites through Shopify Admin, and the connector acts on that connection. Google Antigravity never sees a credential for it.
Why Google Antigravity for Shopify specifically?
One MCP configuration shared by the IDE, the CLI, the SDK and Antigravity 2.0, so the connector is added once and every surface has it.
Do I need a Shopify Partner account?
No. Connect a custom app you create in your own Shopify admin and paste its access token, or use the standard OAuth connect. Neither needs a Partner account.
Can it change prices or inventory?
No. Pricing and inventory are deliberately out of scope. It reads them, and writes only content: pages, posts, descriptions and metadata.
Keep going
The same Google Antigravity connector reaches every other channel — nothing else to add.
Shopify, from Google Antigravity
Paste one URL, sign in once, and the next Shopify question you ask Google Antigravity gets answered from the live account.