Sprites MCP · WordPress

WordPress MCP server: research, write and publish to WordPress from your AI agent

The Sprites MCP server connects your WordPress site to any MCP client. Ask for a post and Sprites researches the keyword, writes it in your site’s voice, sets the metadata and internal links, and creates it as a draft in WordPress — publishing stays a separate approval you give.

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

6 doors · 13 agents

ClaudeSprites 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

What Sprites does on WordPress

Every door runs the WordPress specialist, which reads the account itself. You do not brief it on which account, campaign or page you mean.

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.

Official WordPress MCP vs open-source servers vs Sprites

Three ways to put WordPress behind Claude, ChatGPT or any other MCP client, and what each one can actually do.

Official WordPress MCP

There are two. WordPress.com hosts its own MCP server, with posts, pages, comments, categories, tags and media each switched on separately and every change confirmed in the chat. Self-hosted sites use the official WordPress/mcp-adapter plugin, which exposes the Abilities API in WordPress 6.9 as MCP tools.

Open-source servers

Both official routes are open source, and so is Automattic’s mcp-wordpress-remote, which bridges a client to a site running the adapter. They give an agent hands on WordPress; what to write is left to the model and your prompt.

Sprites MCP

Sprites reads Search Console and keyword data before it writes, works on self-hosted sites over an application password or the Sprites plugin, and holds every post and page edit as a draft or a diff, with going live a separate approval.

The full comparison is further down: WordPress.com’s own server and running your own.

Connect WordPress to your agent

One endpoint, five clients. Each guide is the exact path through that host's settings, the URL to paste, and the first prompt to run.

Your AI agent

Your ad accounts

ClaudeCursorCodexChatGPTGemini
Sprites
Google AdsMetaLinkedInTikTokWordPress
WordPress MCP for Claude

The only host that draws the Sprites approval card in the chat, so you edit a budget or a headline in place and approve it without leaving the thread.

Approval card in the thread
WordPress MCP for ChatGPT

Developer mode gives ChatGPT full read-and-write MCP tools rather than the search-and-fetch pair the built-in connectors are limited to, and the Apps SDK renders the Sprites card in the thread.

Approval card in the thread
WordPress MCP for Codex

Marketing work that belongs in a commit: Codex can read the landing page it is about to ship and brief Sprites on the campaign pointing at it, in one session.

Results as text · approve in Sprites
WordPress MCP for Cursor

The campaign and the page it points at live in the same window: change the pricing copy, then have Sprites update the ads that quote it, without a second tool.

Results as text · approve in Sprites
WordPress MCP for Grok

Grok reads the live timeline, so the same thread that spots a trend can brief the campaign that rides it.

Results as text · approve in Sprites
WordPress MCP for Gemini

The account and the analytics are already Google: Gemini reads Google Ads and GA4 alongside Search Console without leaving the family it belongs to.

Results as text · approve in Sprites
WordPress MCP for GitHub Copilot

Marketing data inside the editor where the tracking code lives, so a conversion event can be checked against what GA4 actually recorded before the pull request is opened.

Results as text · approve in Sprites
WordPress MCP for Google Antigravity

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.

Results as text · approve in Sprites

Official WordPress MCP vs Sprites MCP

Yes, there is an official one: WordPress.com runs its own MCP server at public-api.wordpress.com/wpcom/v2/mcp/v1. Here is what each covers.

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.

Prompts that work verbatim

Paste any of these into a connected client. Naming Sprites matters: without it, an agent will happily answer a WordPress question from public data rather than from your account.

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

What it reads, and what it can change

Reads happen on request. Writes never happen unasked: every change to WordPress is proposed, editable, and applied only when 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

The doors behind it

  • write_seo_blog_post — a researched post created as a WordPress draft, with metadata and internal links set
  • create_seo_page — a landing or service page created or edited, delivered as a diff
  • create_aeo_content — FAQ and comparison content written to be quoted by ChatGPT and AI Overviews
  • research — keyword volume, difficulty and what already ranks for the target
  • analyze — Search Console impressions, clicks and the pages that moved
  • schedule_task — a recurring content brief or refresh that runs on its own

Running your own WordPress MCP server

Community WordPress MCP servers exist and some are good. This is what the route costs, what it is genuinely good at, and the five things that end it — so the comparison is a decision rather than a pitch.

What you have to set up

  • WordPress 6.9 or later, which is where the Abilities API landed in core.
  • The WordPress/mcp-adapter plugin, installed and kept current on its own release cadence separate from core.
  • Abilities registered, and marked public, for whatever you actually want an agent to do — the adapter exposes only public abilities, and an empty registry is an empty tool list.
  • An application password for the WordPress user the agent acts as; the adapter follows that user’s capabilities, so it can do exactly what the user can.

What it is genuinely good at

  • Giving an agent write access to your own site through WordPress’s own abilities and permissions, rather than a third-party plugin.
  • Capability-scoped access: an editor’s password cannot do more than an editor can.
  • Custom abilities — the extension point is the reason this shipped in core rather than as a plugin API.

What breaks under production load

The old plugin is archived, and half the guides still name it

Automattic/wordpress-mcp was archived once the Abilities API landed. Installing it today gets you an unmaintained plugin with REST-API surface area.

It exposes WordPress, not what to say in it

The adapter can create a post. It cannot tell you which post to write, what already ranks for it, or which internal links exist — none of which is its job, and all of which you still need.

Abilities have to be registered before they exist

Out of the box the tool list is whatever core and your plugins happen to register. The interesting operations are usually the ones nobody registered.

Two release cadences

Core moves on its schedule and the adapter on its own. A protocol revision lands between them and the version that works is the one you have not upgraded to yet.

If you want an agent to be able to touch WordPress and you will supply the judgement yourself, the core Abilities API plus the adapter is the right foundation and it is genuinely well designed. If what you wanted was a post that ranks, the adapter is the last mile of a journey it does not make.

The servers people reach for: WordPress/mcp-adapter, @automattic/mcp-wordpress-remote.

WordPress MCP questions

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.

Do I need to install a plugin?

Not necessarily. Sprites connects over the WordPress REST API with an Application Password, which is native to WordPress and takes a minute to create. The plugin is there for sites that lock the REST API down.

Will it publish to my live site without asking?

No. Posts and pages are created as drafts. Publishing is a separate approval, and an edit to a page that is already live arrives as a diff you read before anything changes.

Does it work with WooCommerce, Yoast or Rank Math?

Yes. Metadata is written through the fields your SEO plugin already uses, so a post arrives with its focus keyphrase and description populated rather than flagged red in the editor.

Which agents can I use it from?

Claude, ChatGPT, Codex, Cursor, Gemini, Grok and every other client that speaks remote MCP. One endpoint, one sign-in, no per-client configuration.

The rest of the connector

One URL covers every channel. These are the ones most often used beside this page.

All channels
Google Ads

Live performance, search-term waste, campaign builds and budget moves — every write gated.

6 doors · 13 setup guides
Meta Ads

Creative fatigue per ad, learning-phase checks, new hooks previewed in the real placement.

6 doors · 13 setup guides
LinkedIn Ads

Cost per lead by job function, ABM account lists, sponsored content that converts.

4 doors · 13 setup guides
TikTok Ads

CPA and CTR for every ad, the next creative batch, and spend moved before the CPA drifts.

5 doors · 13 setup guides
Reddit Ads

Community targeting, subreddit-native copy, and the ad groups spending without converting.

5 doors · 13 setup guides
Google Analytics 4

Ask GA4 a question and get the answer — including which channel actually caused it.

4 doors · 13 setup guides
PostHog

Funnels, retention and trends by campaign, read-only, beside the spend that bought them.

4 doors · 13 setup guides
SEO and Search Console

Keyword research, posts written into your CMS, and page edits that arrive as a diff.

4 doors · 13 setup guides
AI visibility (AEO)

Who gets cited by ChatGPT and Perplexity for your prompts, and the pages that change it.

4 doors · 13 setup guides
Shopify

SEO titles across the whole catalogue, collection pages, and product copy that ships on approval.

5 doors · 13 setup guides
Google Business Profile

Performance per location, the listings missing fields, and posts that keep the map pack.

4 doors · 13 setup guides
Webflow

Researched CMS posts, page metadata and copy edits, each an approval before it applies.

6 doors · 13 setup guides
Framer

Researched posts and SEO fields written into your Framer CMS, added after you approve.

6 doors · 13 setup guides
Zoho CRM

Pipeline and lead-source reporting beside ad spend, with approved lead, deal and note writes.

4 doors · 13 setup guides

More on WordPress and MCP

The guides written for this channel first, then the pages that answer what this one assumes: what the protocol is, how it differs from an API, and which servers are worth connecting at all.

Point your agent at WordPress

One URL, one sign-in, and the next WordPress question you ask gets answered from the live account.