SpritesAdd Sprites to Google Antigravity
Available on Antigravity 2.0, Antigravity IDE, Antigravity CLI and the Antigravity SDK. You need a Sprites account with WordPress already connected — the connector acts on that connection, so Google Antigravity never handles a WordPress 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 WordPress account and answers — no account to name, no confirmation to give first.
- With Sprites, write a post on "wordpress speed optimization" and draft it in WordPress.
- Ask Sprites which WordPress pages lost position in the last 28 days and why.
- Use Sprites to rewrite the meta title and description on our /pricing page.
- Have Sprites add an FAQ section with schema to the three posts that get AI Overview impressions.
- With Sprites, cluster our blog by intent and tell me which posts cannibalise each other.
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 WordPress
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.
The post lands in WordPress, not in the chat
A draft in your posts list with the title, excerpt, focus keyphrase, meta description and internal links already filled in — not a wall of text you have to paste and reformat.
It has read your site first
Internal links point at pages that exist, and the voice matches what is already published, because Sprites crawled the site before it wrote anything.
Page edits arrive as a diff
You see which block changes before anything touches the live site. No agent rewriting a page you cannot recover.
Metadata and schema written with the page
Titles, descriptions, headings and FAQ schema produced alongside the body rather than bolted on by a plugin afterwards.
Search Console is in the same conversation
Queries you rank 8–20 for, pages that slipped, and the post that would close the gap — asked and answered without changing tools.
Publishing is always a separate yes
Drafts are created without asking. Nothing goes live on your domain until you approve it.
How approvals work here
Google Antigravity renders tool results as text, so a WordPress 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
- Your published posts, pages, categories and internal link structure
- Search Console queries, impressions, clicks and average position
- Keyword volume, difficulty and what currently ranks
- Existing titles, meta descriptions and schema
What it can change
- Posts and pages, created as drafts
- Titles, meta descriptions, focus keyphrases, headings and FAQ schema
- Edits to existing pages, delivered as a reviewable diff
- Publishing is a separate, explicit approval — never implied by a draft
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.
WordPress 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 WordPress account without asking?
Google Antigravity renders tool results as text, so a WordPress 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 WordPress API key or developer token?
No. WordPress is connected once inside Sprites through WordPress (Application Password or the Sprites plugin), and the connector acts on that connection. Google Antigravity never sees a credential for it.
Why Google Antigravity for WordPress 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.
Is there an official WordPress MCP server?
Sort of, and it changed in 2026. The Abilities API shipped in WordPress core 6.9, and the bridge that exposes those abilities as MCP tools is the WordPress/mcp-adapter plugin, on its own release cadence. Automattic’s earlier wordpress-mcp repository was archived on January 19, 2026, so any guide telling you to install that one is out of date.
What is the difference between that and Sprites?
The adapter exposes WordPress to a model. It does not do the research, know what already ranks, read Search Console, or write in your voice — it gives an agent the ability to create a post, and leaves the deciding to whatever is on the other end. Sprites is the other end.
Keep going
The same Google Antigravity connector reaches every other channel — nothing else to add.
WordPress, from Google Antigravity
Paste one URL, sign in once, and the next WordPress question you ask Google Antigravity gets answered from the live account.