Sprites MCP · SEO MCP server · Google Antigravity

SEO MCP for Google Antigravity: setup in two minutes

Add https://mcp.sprites.ai/mcp as a custom MCP connector in Google Antigravity, sign in to Sprites, and Google Antigravity can read your SEO and Search Console account and propose changes to it. Setup takes about two minutes and needs no API key. Every write comes back as an approval before it touches the account.

MCP server URLhttps://mcp.sprites.ai/mcp

5 steps · about 2 minutes

Google AntigravitySprites connected

Write a post on programmatic SEO and draft it in WordPress.

Spriteswrite_seo_blog_postrunning
SpritesSEONeeds your approval
MMetrica /blog/programmatic-seo-for-saas

Programmatic SEO for SaaS: what actually scales

A working method for building hundreds of pages that rank, and the three failure modes that make most attempts worthless.

Draft in WordPress · not publishedReview

Add Sprites to Google Antigravity

Available on Antigravity 2.0, Antigravity IDE, Antigravity CLI and the Antigravity SDK. You need a Sprites account with SEO and Search Console already connected — the connector acts on that connection, so Google Antigravity never handles a SEO credential.

  1. 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 config
  2. Add 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"
        }
      }
    }
  3. 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
    AllowCancel
  4. Use 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 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.

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 SEO and Search Console

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.

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

Google Antigravity 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 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.

SEO and Search Console 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 SEO and Search Console account without asking?

Google Antigravity 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. Google Antigravity never sees a credential for it.

Why Google Antigravity for SEO and Search Console 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.

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 Google Antigravity connector reaches every other channel — nothing else to add.

All SEO guides

SEO and Search Console, from Google Antigravity

Paste one URL, sign in once, and the next SEO question you ask Google Antigravity gets answered from the live account.