SpritesAdd Sprites to Google Antigravity
Available on Antigravity 2.0, Antigravity IDE, Antigravity CLI and the Antigravity SDK. You need a Sprites account with AI visibility (AEO) already connected — the connector acts on that connection, so Google Antigravity never handles a AEO 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 AI visibility (AEO) account and answers — no account to name, no confirmation to give first.
- With Sprites, who gets cited when someone asks ChatGPT for the best AI ads platform?
- Ask Sprites to check our AI visibility against our three named competitors.
- Use Sprites to write a comparison page for "us vs [competitor]" and draft it on the site.
- Have Sprites generate an llms.txt from what we actually publish.
- With Sprites, set up a weekly check on our top 20 buying prompts.
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 AI visibility (AEO)
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.
Find out whether you exist
The prompts your buyers type, run against the answer engines, with who gets named and who does not.
See who is taking the citation
The competitor being cited, and the page the engine is reading to do it.
Write the page that wins it back
Answer pages, FAQ pages and comparison pages, structured the way answer engines actually lift from.
Ship an llms.txt that is not a stub
A real index of what you publish, generated from the site rather than hand-listed and forgotten.
Track it over time
Visibility per prompt per engine, so a change is attributable to the page that caused it.
Get told when it slips
A scheduled check that messages you when a citation you had is gone.
How approvals work here
Google Antigravity renders tool results as text, so a AEO 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
- Answer-engine responses for the prompts you care about
- Which brands and pages get cited, and how often
- Your own site structure and existing answer coverage
- Competitor pages the engines are reading
What it can change
- Answer pages, FAQ pages, comparison and "vs" pages
- llms.txt and entity pages
- All drafted onto your site and published only on 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.
AI visibility (AEO) 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 AI visibility (AEO) account without asking?
Google Antigravity renders tool results as text, so a AEO 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 AI visibility (AEO) API key or developer token?
No. AI visibility (AEO) is connected once inside Sprites through Your site, plus AI answer-engine tracking, and the connector acts on that connection. Google Antigravity never sees a credential for it.
Why Google Antigravity for AI visibility (AEO) 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.
What is AEO?
Answer engine optimization: getting cited in the answers ChatGPT, Perplexity, Claude, Gemini and Google AI Overviews give, rather than ranking in a list of ten blue links. The unit of success is a citation, not a position.
How does it know whether we are cited?
It runs your prompts against the engines and reads the answers, recording which brands and sources are named. It is a measurement, not an estimate.
Keep going
The same Google Antigravity connector reaches every other channel — nothing else to add.
AI visibility (AEO), from Google Antigravity
Paste one URL, sign in once, and the next AEO question you ask Google Antigravity gets answered from the live account.