Sprites
Perplexity133d livePerplexity Computer
Add Sprites to Google Antigravity
Available on Antigravity 2.0, Antigravity IDE, Antigravity CLI and the Antigravity SDK. You need a Sprites account with your channels already connected — the connector acts on that connection, so Google Antigravity never handles a platform 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.
Which Google Antigravity surface you are on
Only the surfaces below are documented here. Where we have not verified a path, the page says so rather than implying the setup is the same everywhere.
Antigravity IDEVerified
… → MCP Servers → Manage MCP Servers → View raw config.
Antigravity CLIVerified
Reads the same ~/.gemini/config/mcp_config.json; no second setup.
Antigravity 2.0Verified
Shares the config with the IDE and CLI.
Antigravity SDKVerified
Same configuration format, used from your own code.
What Google Antigravity can reach
All ten channels run through the one connector. Rows with a guide go deeper on that pairing; the rest are covered on the channel's own page.
| Channel | What Antigravity does with it | Guide |
|---|---|---|
| Google Ads | Account data available to whichever Antigravity surface a task happens on, configured once. | Set up → |
| Meta | Creative fatigue per ad, audience overlap, new hooks previewed in the real placement. | Set up → |
| Cost per lead by job function, ABM account lists, sponsored content that converts. | Set up → | |
| TikTok | Hook-level hold rates, the next creative batch, and rotation before the CPA moves. | Set up → |
| Performance per subreddit, community-native copy, and the tourist traffic to cut. | Set up → | |
| GA4 | The same connection serves the IDE and the CLI, so a check written in one runs in the other. | Set up → |
| SEO | Search Console evidence in the agent panel next to the code that generates the pages. | Set up → |
| AEO | Who gets cited by ChatGPT and Perplexity for your prompts, and the pages that change it. | Set up → |
| Shopify | Profit per product after ad cost, collection pages, and catalogue-true creative. | Set up → |
| GBP | Performance per location, the listings missing fields, and posts that keep the map pack. | Set up → |
Marketing workflows worth doing in Google Antigravity
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.
Debug an analytics implementation
Read what GA4 recorded against what the code sends, with the agent able to do both halves.
Build a campaign reporting application
Develop against live account data rather than a fixture, so the edge cases are the real ones.
Check a deployment against conversion data
Tie a release to what happened to conversions after it, instead of arguing about correlation later.
Generate a marketing operations tool
A small internal utility built and run on the surface that already has the account connected.
Permissions, approvals and authentication
You sign in with OAuth and the connector acts on your workspace. No API keys in a config file, no shared service account, and revoking the grant kills the very next call.
| Action | When it happens | What that covers |
|---|---|---|
| Read an account | On request | Spend, performance, search terms, rankings, catalogue |
| Draft a change | On request | Campaigns, creative, budgets, pages and posts |
| Apply a change | Only on your approval | Google Antigravity returns the change as text; the approval waits for you in Sprites |
| Spend money | Only on your approval | New campaigns start paused unless you say otherwise |
| Revoke access | Instantly | The next call after a revoke fails, not the one after that |
Google Antigravity MCP questions
Why serverUrl rather than url?
Antigravity requires serverUrl for remote connections and its documentation states plainly that url and httpUrl are not supported. An entry using them is skipped rather than reported as broken.
Do I configure each product separately?
No. All four read ~/.gemini/config/mcp_config.json, or .agents/mcp_config.json inside a workspace. Add it once.
Is Sprites in the MCP Store?
Sprites is added as a custom remote server, which is the supported path for any server not in the Store.
Can it change my ad accounts on its own?
No. Reads happen on request; every write comes back as a change you approve first, and new campaigns start paused. Nothing is applied because a model decided it should be.
How does OAuth work here?
Antigravity registers itself with the authorization server automatically and completes the flow at its own callback URL. There is nothing to pre-register.
Point Google Antigravity at your ad accounts
One URL, one sign-in, and the next question you ask Google Antigravity about your marketing gets answered from the live account.