SpritesAdd Sprites to Gemini
Available on Gemini CLI, free and paid, on macOS, Linux and Windows. You need a Sprites account with SEO and Search Console already connected — the connector acts on that connection, so Gemini never handles a SEO 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 SEO and Search Console account and answers — no account to name, no confirmation to give first.
- With Sprites, write a post on "programmatic SEO for SaaS" and put it in WordPress as a draft.
- Ask Sprites which queries we rank 8-20 for and could reach the top 5.
- Use Sprites to optimize our /pricing page for "ai ads platform pricing".
- Have Sprites do keyword research for the integrations section and cluster it by intent.
- With Sprites, find pages that lost position in the last 28 days and say why.
Run `gemini mcp list`, or type /mcp inside the CLI — Sprites should show as connected with its tools listed.
What Gemini can do with SEO and Search Console
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.
It writes onto the site, not into the chat
WordPress, Webflow, Shopify, Framer or a custom CMS: the post lands as a draft with metadata and internal links already set.
Keyword research with real numbers
Volume, difficulty and intent clustering from live data, not a model's recollection of a keyword tool.
Edit a page without breaking it
Page edits arrive as a diff. You see exactly which block changes before anything touches the live site.
Read what Search Console knows
Queries you nearly rank for, pages that slipped, and the impressions you are leaving on the table.
Internal links that already exist
New posts link into the site's real structure, because Sprites has read it.
Metadata that is not an afterthought
Titles, descriptions, focus keyphrases and schema written with the page rather than bolted on.
How approvals work here
Gemini renders tool results as text, so a SEO change comes back written out rather than as a card. The approval waits for you in Sprites — open it there and the same run continues. Nothing is applied until you approve it.
What it reads
- Search Console queries, impressions, clicks and average position
- Your live site: structure, internal links, existing pages and voice
- Keyword volume, difficulty and SERP composition
- What currently ranks for the target query
What it can change
- Blog posts, created as drafts in your CMS
- Landing and service pages, created or edited as a reviewable diff
- Titles, meta descriptions, focus keyphrases, headings and schema
- Publishing is always a separate, explicit 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.
SEO and Search Console 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 SEO and Search Console account without asking?
Gemini renders tool results as text, so a SEO change comes back written out rather than as a card. The approval waits for you in Sprites — open it there and the same run continues. Nothing is applied until you approve it.
Do I need a SEO and Search Console API key or developer token?
No. SEO and Search Console is connected once inside Sprites through Google Search Console and your CMS, and the connector acts on that connection. Gemini never sees a credential for it.
Why Gemini for SEO and Search Console 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.
Which content management systems does it publish to?
WordPress, Webflow, Shopify's blog, Framer, and any other CMS through a webhook. The CMS is connected once in Sprites; your agent never handles the credential.
Will it publish without asking?
No. Posts arrive as drafts and page edits arrive as diffs. Publishing is a separate approval, and a page edit shows you every block it would change.
Keep going
The same Gemini connector reaches every other channel — nothing else to add.
SEO and Search Console, from Gemini
Paste one URL, sign in once, and the next SEO question you ask Gemini gets answered from the live account.