Sprites MCP · WordPress MCP server · Google Antigravity

WordPress 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 WordPress 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 WordPress speed optimization and draft it on the site.

Spriteswrite_seo_blog_postrunning
SpritesWordPressNeeds your approval
NNorthbound /blog/wordpress-speed-optimization

WordPress speed optimization: what actually moves LCP

The four changes that move Core Web Vitals on a real WordPress install, and the six plugins that promise it and do not.

Draft created · 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 WordPress already connected — the connector acts on that connection, so Google Antigravity never handles a WordPress 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.

Official WordPress MCP vs Sprites MCP

WordPress.com runs its own MCP server at public-api.wordpress.com/wpcom/v2/mcp/v1. Here is what each one covers, so you can pick the one that fits in Google Antigravity — or connect both.

WordPress.com hosts its own MCP server, now able to write: 19 abilities across posts, pages, comments, categories, tags and media, each switched on individually in your MCP settings, with the agent describing every change and asking before it applies. Writes need a paid WordPress.com plan. Self-hosted WordPress has no hosted equivalent; its official route is the WordPress/mcp-adapter plugin over the Abilities API in WordPress 6.9.

WordPress.com’s official WordPress.com MCP server compared with the Sprites MCP server
WordPress.com officialpublic-api.wordpress.com/wpcom/v2/mcp/v1Sprites MCPapproval-gated
Which WordPressWordPress.com sites; self-hosted sites install the MCP Adapter plugin insteadSelf-hosted WordPress, over the REST API with an application password or the Sprites plugin
What it writesPosts, pages, comments, categories, tags and media, each toggled on separatelyPosts and page edits, with metadata, schema and internal links set
Before a change appliesThe agent describes it and asks you to confirm in the chatA draft or a diff you review; going live is a separate approval
What it knows about SEOYour site’s content, analytics and settingsYour site plus Search Console, keyword data and what already ranks
Choosing what to writeLeft to the model and your promptResearched: the keyword, the gap, and the pages that should link to it

If you run WordPress.com and want to draft or tidy content from a chat, its own server is well built — every write is confirmed and every operation can be switched off. Use Sprites when the question is what to write and why: it reads Search Console and keyword data first, works on self-hosted sites without a plugin, and holds every post and edit as a draft you approve.

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

Every write, a draft included, is proposed for your approval first, and going live on your domain is its own separate approval.

How approvals work here

Google Antigravity renders tool results as text, so a WordPress 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

  • 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. 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 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?

Two, one for each kind of WordPress. WordPress.com hosts an MCP server with write tools for posts, pages, comments, media and taxonomies, each change confirmed by you. Self-hosted sites use the official WordPress/mcp-adapter plugin, which exposes the Abilities API from WordPress 6.9 as MCP tools. Automattic’s earlier wordpress-mcp repository has been archived, 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.

All WordPress guides

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.