Add Sprites to Gemini
Available on Gemini CLI, free and paid, on macOS, Linux and Windows. You need a Sprites account with AI visibility (AEO) already connected — the connector acts on that connection, so Gemini never handles a AEO credential.
Open the Gemini settings file
Gemini CLI keeps MCP servers in its settings JSON. Use ~/.gemini/settings.json to have Sprites available everywhere, or .gemini/settings.json inside a project to scope it there.
Gemini CLI~/.geminisettings.jsonAdd Sprites under mcpServers
Use httpUrl, not url or command — that is the key Gemini CLI reads for a streamable HTTP endpoint. A url entry is treated as SSE and a command entry as a local process, and neither is what this is.
~/.gemini/settings.json{ "mcpServers": { "sprites": { "httpUrl": "https://mcp.sprites.ai/mcp" } } }Sign in
Gemini CLI supports OAuth 2.0 for remote servers and discovers the authorization server from the endpoint itself. Restart the CLI, and the first call opens a browser for the Sprites consent screen; the token is stored in ~/.gemini/mcp-oauth-tokens.json.
Spriteswants access on behalf of Gemini- Read your connected ad accounts and site data
- Draft campaigns, creatives and pages for your approval
- Apply only the changes you approve
AllowCancelCheck it landed
Type /mcp in the CLI to list every server and the tools it exposes, or run gemini mcp list from a shell to see connection status without opening a session.
Terminalgemini mcp list
Run the first prompt
Ask Gemini 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.
Run `gemini mcp list`, or type /mcp inside the CLI — Sprites should show as connected with its tools listed.
What Gemini can do with AI visibility (AEO)
The same doors, whichever client you are in. The account and the analytics are already Google: Gemini reads Google Ads and GA4 alongside Search Console without leaving the family it belongs to.
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
Gemini 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 Gemini
Three things go wrong in this client specifically, and each has a one-line fix.
Gemini connects but reports no tools.
The entry is probably using url rather than httpUrl, so the CLI is speaking SSE to a streamable HTTP endpoint. Change the key and restart.
Edits to settings.json do nothing.
The CLI reads its settings at startup. Restart it, then re-check with /mcp.
A project file and your home file disagree.
.gemini/settings.json in the working directory takes precedence. Keep Sprites in one of the two rather than both.
AI visibility (AEO) and Gemini: questions
Which URL do I paste into Gemini?
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 Gemini change my AI visibility (AEO) account without asking?
Gemini 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. Gemini never sees a credential for it.
Why Gemini for AI visibility (AEO) specifically?
The account and the analytics are already Google: Gemini reads Google Ads and GA4 alongside Search Console without leaving the family it belongs to.
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 Gemini connector reaches every other channel — nothing else to add.
AI visibility (AEO), from Gemini
Paste one URL, sign in once, and the next AEO question you ask Gemini gets answered from the live account.