Add Sprites to Claude
Available on Free (one custom connector), Pro, Max, Team and Enterprise, on claude.ai, Claude Desktop and Claude Code. You need a Sprites account with WordPress already connected — the connector acts on that connection, so Claude never handles a WordPress credential.
Open the connector settings
On a Free, Pro or Max plan, go to Settings, then Customize, then Connectors. On Team and Enterprise an Owner adds the connector once for the whole workspace under Organization settings → Connectors, and everyone else only clicks Connect.
ClaudeSettingsCustomizeConnectorsAdd a custom connector
Click the + button, then Add custom connector. On Team and Enterprise, hover Custom and choose Web. Paste the Sprites endpoint and click Add. Leave Advanced settings alone — Sprites publishes its own OAuth client metadata, so there is no client ID or secret to fill in.
Add custom connectorNameSpritesRemote MCP server URLhttps://mcp.sprites.ai/mcpSign in and approve the scopes
Click Connect. Claude opens the Sprites consent screen in a new tab. Sign in with the account your ad platforms are already connected to, review what Sprites is being allowed to do, and approve. The grant is revocable from Claude settings or from Sprites at any time, and the very next tool call after a revoke fails closed.
Spriteswants access on behalf of Claude- Read your connected ad accounts and site data
- Draft campaigns, creatives and pages for your approval
- Apply only the changes you approve
AllowCancelOr add it to Claude Code in one line
The terminal client takes the same endpoint. Run the command, then type /mcp inside Claude Code to finish the browser sign-in.
Terminalclaude mcp add --transport http sprites https://mcp.sprites.ai/mcp
Run the first prompt
Ask Claude 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.
Type "what can Sprites do?" — Claude lists the doors it can see. If it names analyze, launch and optimize, the connector is live.
What Claude can do with WordPress
The same doors, whichever client you are in. 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.
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
Claude draws the Sprites approval card in the thread. A WordPress change arrives with its before and after filled in, editable in place, and applies when you click approve.
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 Claude
Three things go wrong in this client specifically, and each has a one-line fix.
The connector is added but Claude says it has no tools.
The OAuth handshake completed but the token is not being accepted. Disconnect and reconnect from Settings → Connectors; a stale grant from a previous session is the usual cause.
Claude asks which ad account you mean before it calls anything.
Tell it to just call Sprites. Sprites reads the account itself — it does not need the account named, and answering the question costs you a turn.
On Team or Enterprise the Connectors page has no Add button.
Only an Owner or Primary Owner can add a workspace connector. Ask them to add it once under Organization settings → Connectors; after that every member sees a Connect button.
WordPress and Claude: questions
Which URL do I paste into Claude?
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 Claude change my WordPress account without asking?
Claude draws the Sprites approval card in the thread. A WordPress change arrives with its before and after filled in, editable in place, and applies when you click approve.
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. Claude never sees a credential for it.
Why Claude for WordPress specifically?
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.
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 Claude connector reaches every other channel — nothing else to add.
WordPress, from Claude
Paste one URL, sign in once, and the next WordPress question you ask Claude gets answered from the live account.