Let your AI find, fix and verify WordPress SEO problems.
Connect ChatGPT, Claude, Codex or another AI agent to WordPress, Google Search Console and GA4. RefreshAgent supplies the evidence and controlled execution layer so your agent can propose exact changes, wait for approval, apply them, verify them live and roll them back safely.
APPROVE
What is WordPress MCP?
The original Automattic repository is archived and deprecated. The current official direction is the WordPress Abilities API plus the WordPress MCP Adapter ↗. RefreshAgent's native WordPress abilities are built for that architecture, while its signed REST bridge keeps the SEO execution workflow available on older supported WordPress installs too.
For the official architecture explanation, see WordPress's Abilities-to-AI-agents guide ↗. If you were looking for the old project, the archived source remains visible at Automattic/wordpress-mcp ↗.
Standalone experimental MCP implementation. Now archived/deprecated.
Capabilities are registered in WordPress, then exposed through the protocol layer.
ChatGPT · Claude · Codex
Your existing AI keeps the conversation, codebase and broader working context.
RefreshAgent
GSC + GA4 evidence, computed SEO operators, WordPress URL mapping, exact previews, permission gates and verification.
WordPress · Yoast · Rank Math
The system of record where an approved change is applied and later verified.
MCP is the pipe. The SEO loop is the product.
A generic WordPress MCP server can expose hundreds of CRUD actions. RefreshAgent is deliberately narrower: it connects a measurable SEO problem to the exact WordPress action that addresses it.
Search Console and GA4 identify a page worth attention. RefreshAgent computes the opportunity instead of simply dumping rows into the model.
The Search Console URL is resolved to WordPress, then the agent reads the real page and current Yoast/Rank Math state.
The model proposes a concrete change. RefreshAgent turns it into an exact before/after diff tied to a fingerprint of the current page.
You approve the exact diff. Only then does the workflow cross from read-only analysis into the separately-authorized write path.
WordPress is changed, the live rendered page is checked, and a rollback snapshot is retained.
/blue-widgets/ looks like a CTR opportunity
Illustrative data: ranking is relatively stable while CTR underperforms the site's own position-band baseline.
URL → page #481 → Yoast
wordpress_resolve_url maps the GSC URL to the editable page. The agent then reads the page and current SEO metadata before suggesting anything.
Exact proposed diff
RefreshAgent fingerprints the current state so this preview cannot be silently applied after someone else changes the page.
Approval unlocks the write path
Read and preview stay on seo:read. Applying the exact preview requires the separate seo:write permission.
The change is not “done” until it is verified
RefreshAgent checks WordPress state and fetches the public page. The before-state remains available for conflict-safe rollback.
Giving AI WordPress access should not mean giving it a loaded gun.
The semantic difference between reading and mutating should be impossible to miss. The write path is deliberately narrow, gated and reversible.
GSC · GA4 · page body · SEO metadata
Exact before / after values + fingerprint
You authorize this specific diff
Only the approved fields are mutated
Database state + rendered live page
Which WordPress MCP setup should you use?
RefreshAgent does not try to replace every WordPress MCP option. It adds an SEO-specific decision and execution layer where generic connectivity stops.
| Option | Best for | WordPress actions | GSC / GA4 evidence | SEO-specific safe loop |
|---|---|---|---|---|
| WordPress.com MCP | WordPress.com / eligible Jetpack workflows | Yes | Not its primary job | No dedicated evidence → change → outcome loop |
| Official MCP Adapter | Developers exposing WordPress Abilities | Yes, via registered abilities | No | No; it is infrastructure |
| Generic WordPress MCP plugin | Broad site administration from AI | Usually many | Varies | Varies |
| RefreshAgent | SEO work from ChatGPT, Claude or Codex | Focused SEO execution | GSC + GA4 | Preview → approve → apply → verify → rollback |
What can an AI SEO operator actually do?
The useful unit is not “a tool call.” It is a measurable workflow that starts with evidence and ends with a verified change.
Fix a CTR opportunity
Find pages with enough impressions to matter where CTR underperforms relative to the site's own position bands, inspect the WordPress page, then preview a title/meta change.
Investigate content decay
Compare Search Console periods, find pages losing clicks or visibility, map the affected URL to WordPress and read the page before deciding whether metadata or content needs work.
Make an approved metadata change
Preview a WordPress title, Yoast SEO title, Rank Math title or meta description and apply only after the user approves that exact before/after state.
Verify and undo
Confirm the values saved in WordPress, fetch the public page to inspect rendered metadata, and restore the original state if the change should be reversed.
Use WordPress MCP from the agent you already work in.
There are two layers: the WordPress plugin connects the site; RefreshAgent's MCP connection gives your AI the evidence and SEO execution tools.
ChatGPT MCP / plugin
- Install and connect the RefreshAgent WordPress plugin.
- Connect Google Search Console and GA4 to RefreshAgent.
- Add RefreshAgent to ChatGPT and authorize read access.
- Grant write permission only when you want ChatGPT to apply approved WordPress changes.
Claude MCP
- Connect WordPress to RefreshAgent.
- Add the RefreshAgent MCP endpoint to a Claude client that supports remote MCP.
- Ask for Search Console evidence first.
- Let Claude preview WordPress changes, then approve the exact diff you want.
Claude Code / Codex CLI
- Create a RefreshAgent API key.
- Run the RefreshAgent MCP bridge in your coding agent.
- Your agent keeps its repository/code context while gaining live SEO and WordPress tools.
- The model uses your existing agent plan; RefreshAgent supplies data + execution.
The tool surface shows where authority changes.
The abilities are ordered to make the security model visible: discovery and preview happen above the write boundary; mutation only happens after approval.
resolve-urlMap a GSC URL to the editable WordPress object.
get-contentRead page body and current WordPress context.
inspect-seo-stateRead Yoast, Rank Math or fallback metadata.
preview-seo-changeCreate the exact diff and bind it to current state.
apply-seo-changeseo:write · apply the approved preview only.
verify-seo-changeseo:read · confirm WordPress state and the public page after the write.
rollback-seo-changeseo:write · restore safely, refusing conflicts.
WordPress MCP questions
Answers to the terms people usually encounter when connecting ChatGPT, Claude and other AI agents to WordPress.
What is a WordPress MCP server?
A WordPress MCP server exposes structured WordPress capabilities to AI clients using the Model Context Protocol. The current official WordPress approach uses the Abilities API to define capabilities and the MCP Adapter to expose them through MCP.
Is the old Automattic WordPress MCP plugin still the right one?
No. The original Automattic/wordpress-mcp repository is archived and deprecated. For new integrations, follow the current WordPress Abilities API + official MCP Adapter architecture.
Can ChatGPT edit WordPress through MCP?
Yes, if the MCP connection exposes write-capable WordPress abilities and the user has authorized them. RefreshAgent separates read and write permission and requires an exact approved preview before its SEO mutation tools apply a change.
Can Claude use WordPress MCP?
Yes. Claude clients that support MCP can use WordPress MCP servers directly or use RefreshAgent's MCP endpoint for SEO-specific GSC/GA4 evidence and WordPress execution.
Does RefreshAgent support Yoast SEO?
Yes. RefreshAgent can inspect and update Yoast SEO title and meta-description fields through its controlled preview/apply workflow.
Does RefreshAgent support Rank Math?
Yes. Rank Math title and description metadata are supported. If Yoast and Rank Math are both active and the intended provider is ambiguous, RefreshAgent refuses to guess.
Why not just give an AI generic WordPress CRUD access?
Generic access solves connectivity, but it does not decide which SEO change is justified, preserve the evidence behind the decision, require an exact approved diff, verify the rendered result or protect later human edits during rollback.
Do external agents use RefreshAgent AI tokens?
Not for the external MCP workflow. ChatGPT, Claude, Codex or your chosen agent supplies the reasoning. RefreshAgent supplies live data, deterministic SEO operators and controlled WordPress execution.
Keep the conversation in your AI. Let RefreshAgent control the risky part.
Give the agent you already use enough evidence to make a good SEO recommendation, then let RefreshAgent turn the approved recommendation into a verified, reversible WordPress change.