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 Meta Ads already connected — the connector acts on that connection, so Google Antigravity never handles a Meta 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 Meta Ads account and answers — no account to name, no confirmation to give first.
- With Sprites, which Meta creatives are fatiguing and what should replace them?
- Ask Sprites for 5 new hooks for our best-performing Instagram ad.
- Use Sprites to compare Meta ROAS this month against last month by ad set.
- Have Sprites check whether our ad sets are overlapping on audience.
- With Sprites, show me what our top 3 competitors are running on Meta right now.
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 Meta Ads
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.
See fatigue before the CPA does
Frequency, first-time impression ratio and the day a creative's CTR broke trend, per ad rather than per campaign.
Get new creative, not a brief
Hooks, headlines and image concepts drafted against what is already working, previewed in the real placement.
Untangle the ad sets
Audience overlap, learning-phase resets and the ad sets quietly bidding against each other.
Watch the competition
Live ads from any advertiser in the Meta ad library, read as angles rather than screenshots.
Launch across placements
Campaign, ad sets, audiences and ads in one editable proposal, with the creative attached.
Reallocate on evidence
Move budget to the ad set that earns it, with the before-and-after stated in the card.
How approvals work here
Google Antigravity renders tool results as text, so a Meta 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
- Campaigns, ad sets, ads, audiences and their status
- Spend, ROAS, CPA, CTR, frequency and placement breakdowns
- Creative assets and per-creative performance
- Public competitor ads from the Meta ad library
What it can change
- Create campaigns, ad sets, audiences and ads
- Budgets, schedules, statuses and targeting
- New creative, previewed in placement before anything ships
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.
Meta Ads 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 Meta Ads account without asking?
Google Antigravity renders tool results as text, so a Meta 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 Meta Ads API key or developer token?
No. Meta Ads is connected once inside Sprites through Meta (Facebook and Instagram) Ads, and the connector acts on that connection. Google Antigravity never sees a credential for it.
Why Google Antigravity for Meta Ads 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 Meta developer app or a system user token?
No. You connect Meta once inside Sprites with OAuth; the MCP connector then acts on that connection. Your agent never sees a token.
Can it publish an ad without me seeing it?
No. Creative comes back as a preview in the real placement, editable, and ships only when you approve it.
Keep going
The same Google Antigravity connector reaches every other channel — nothing else to add.
Meta Ads, from Google Antigravity
Paste one URL, sign in once, and the next Meta question you ask Google Antigravity gets answered from the live account.