WordPress MCP server pluginYour agent edits the live site. You keep the final say.
A client wants Claude on their site and you’d rather not hand over admin. AgentedSEO is a WordPress MCP server plugin scoped to SEO: your agent gets 72 SEO and content tools under its own login, you see every change as before and after, approve it where you choose, and undo any of it from the change log.
- Works with 4 agentsClaude, Cursor, Codex, Hermes
- No bridge pluginAnd no AI credits
- Agent limited to SEORisky edits ask you first
- 3 → 12 pages a monthJoy’s test on 10 sites
Approving isn’t one of the agent’s tools. Only a person decides.
Try it: approve the change, then undo it.
Why your WordPress MCP server still lives on staging.
A client emails: “please set up Claude on our WordPress site.” Connecting a WordPress MCP server takes an afternoon. Deciding what it may write to a live business takes longer. With most setups you approve the connection once, and after that the agent writes with whatever access its account has.
That is why agencies keep agents on staging. The cost is real hours. Snapshots before every run, diffs after, and when one meta description goes wrong you restore a whole backup to fix a single field. A contributor to the official MCP Adapter summed up the owner’s side: “wp-admin shows neither what’s connected nor what changed.”
I hit the same wall on my own site. On classicmonks.com my agent researches keywords, writes the posts and publishes them, and I still could not see at a glance what it had changed. So I built the rules first.
One agency developer described the routine:
“we don’t let agents touch production at all, staging only. even then we snapshot before the agent runs and diff the changes after.”
Another put the rule in one line:
“The problem is not integration, but scope. Never allow AI to directly write a production system without user approval.”
AgentedSEO gives the agent a narrower door.
It works on the live site through an SEO-only login, the areas you pick wait for your approval, and every change sits in a change log you can undo from. WordPress’s own developer blog gives the same advice for production: “create a specific role/user with limited capabilities.”
Read what your agent can and can’t do before you connect it.
The rules are published, and the plugin enforces them for every agent connection. You can change the second column per area in AgentedSEO › Agents › Approval rules. The last two columns can’t be switched off.
- New drafts
- Edits to drafts
- Titles, descriptions and other meta
- Schema
- Redirects
- Sitemaps and robots settings
- Focus keywords and alt text
- Edits to published posts, and publishing
- Bulk changes over 20 items in one call
- Robots.txt edits
- Noindex on a page with traffic (until traffic data is connected, every page counts)
- Deleting redirects or schema
- Trashing or unpublishing content
- Hiding a whole post type, taxonomy or the author archive from search
- Users and roles
- Plugins and themes
- Header and footer code
- Permanent deletes
- Every REST route outside AgentedSEO, and XML-RPC sign-in
Every change is logged with who made it, person or agent, when and through which door, and each one can be undone, including whole batches.
A WordPress MCP plugin that gives your agent SEO tools, not the whole site.
When you connect an agent, it gets 72 tools for SEO and content and nothing for users, plugins or themes. The agent can’t wander into the parts of the site that keep a client’s business running, so you can say yes to “set up Claude” without lying awake over it.
- 72
- tools for SEO and content
- 4
- ways in: MCP, REST, WP-CLI, Abilities API
- 0
- tools for users, plugins or themes
What the agent can reach
- 72 tools in plain groups: content, on-page meta, breadcrumbs, schema, technical (redirects, 404s, sitemaps, robots.txt, llms.txt, IndexNow), site checks, broken links, image alt text, your keyword plan, change control, settings and importers. Six Search Console tools return data once Search Console arrives (coming soon).
- The same 72 tools answer through the built-in MCP endpoint, the REST API, WP-CLI and the WordPress Abilities API, so a script and a chat client see the same rules.
- The agent’s user is refused on every REST route outside AgentedSEO and can’t sign in over XML-RPC, so the tool list is the whole of what it can reach.
- Each tool is marked read-only or destructive, so your client can tell a lookup from a change before it runs it.
- The first call, get-capabilities, returns every field the agent may write, its limits and what its user is allowed to do. Nothing is hidden from the agent or from you.
See each change as before and after, and approve it before it goes live.
Your agent proposes a change and you see the old value next to the new one, with the checks it passed. You approve it, reject it with a reason the agent reads, or approve a whole batch on one screen. Approval rules per area decide what may run alone.
How approval works
- Every write can run as a preview first: the agent gets the before and after back and nothing is written.
- Approval rules cover 11 areas (meta, schema, redirects, sitemaps, keywords, alt text, new drafts, draft edits, published edits, publishing, bulk). Out of the box, everything except new drafts and draft edits asks first.
- Approve all or Reject all, up to 100 at once, or a whole batch. Changes from one agent call are grouped, in Approvals and in the editor’s Agent view.
- A rejection can carry a reason, and the agent gets it back, so the next try fixes what you objected to. The change log shows who approved each change.
- If the page changed after the agent proposed, the proposal is flagged as stale instead of overwriting your edit. Approving and rejecting are not tools: only a person decides.
Undo any agent change days later, even after the chat is gone.
Any change, or a whole batch, goes back from the change log in AgentedSEO, with redo if you change your mind. The undo lives on your site, so it does not depend on the AI tool still remembering the old value. One bad change is a click, not a backup restore.
Every change is logged with who made it (person or agent), when, and through which door, and can be undone; batch undo for imports and bulk jobs.
The chat is closed. The undo lives on your site.Undone · 12 values back as they were · logged
What the log records
- The change log (AgentedSEO › Dashboard › Change log) records who made each change, you or the agent, who approved it, when, and through which door: MCP, REST, WP-CLI or the dashboard.
- Undo one change or a whole batch. Redo after an undo. Rewritten posts come back from their WordPress revision.
- Agents › Activity records every agent request, reads and refused attempts included, and exports to CSV for a client report.
- Undo keeps working if a yearly licence lapses. Your data and the change log stay on your site.
Each agent gets its own login, never your admin password.
Connecting an agent creates a separate WordPress user with the SEO Agent role. It signs in with an application password or an OAuth grant made for that user, never your login. Revoking it is one click, and the work it did stays with you.
The SEO Agent role cannot touch users, plugins, themes, header and footer code; robots.txt edits, noindex, trash and deletes always ask first.
Get AgentedSEOHow the login works
- Two ways in. “Add a custom connector” signs in with OAuth 2.1, so no password is pasted anywhere; “Desktop or code app” makes an application password for Claude Code, Cursor, Codex or Hermes, shown once.
- Each connection is its own user with its own Last activity and its own Revoke. OAuth access tokens last one hour and refresh tokens 30 days, and they rotate.
- Revoke deletes the agent’s user and its password or sign-in. The change log stays, and any content the agent created is handed to you.
- An address is locked out after ten failed sign-ins, and agent users can’t sign in over XML-RPC.
- The server tells every agent that site content is data, not instructions, so text hidden in a post is not a command.
A WordPress MCP server for Claude, Cursor, Codex and Hermes, with no bridge.
You add your site’s MCP URL to the AI client you already use, and it connects to the same 72 tools. The endpoint is built into the plugin, so there is no second plugin to install and no proxy to run. You keep using the AI plan you already pay for.
- The endpoint is https://your-site.com/wp-json/agentedseo/mcp. AgentedSEO › Agents › Connections shows it with your domain filled in, plus a config to paste.
- Claude (web and desktop) connects through its connector settings and signs in with OAuth. Claude Code, Cursor, Codex and Hermes use the application password config.
- No AI credits to buy. The optional AI helpers inside the plugin are off by default and run on your own key.
- Scripts get the same tools over REST, with an OpenAPI 3.1 file at /wp-json/agentedseo/v1/openapi.json, and over WP-CLI.
Your MCP URL
https://your-site.com/wp-json/agentedseo/mcpClaude, Cursor, Codex and Hermes are the clients we have tested, and each has a step-by-step guide in the docs.
One connection for the post and its SEO, with publishing waiting for your yes.
The agent can create drafts, edit posts and blocks, upload media and schedule posts, with the SEO fields set in the same pass. New posts are always drafts. Publishing and edits to live posts go through approval, and every rewrite can go back through its revision.
What it can write
- Create, edit, edit blocks, publish, schedule, trash and upload media, on the post types you allow.
- Markup must be valid block markup or HTML WordPress allows in posts. Scripts and iframes are refused.
- If someone has the post open in the editor, the agent’s edit becomes a proposal instead of overwriting them.
- Pages built with Bricks, Elementor, Breakdance or Oxygen are read-only for agents. Their SEO fields still change.
- Media the agent uploads that is never approved is deleted after a week, so rejected work does not pile up.
Which WordPress MCP server plugin fits your job? Compared on facts.
The best WordPress MCP server depends on what you want the agent to touch. If it should manage the whole site, a general server is the better pick. If it should do SEO and content on a live client site, scope matters more than tool count.
| Question | General-purpose WordPress MCP servers (examples) | AgentedSEO |
|---|---|---|
| What can the agent reach? | Site-wide tool sets. Tool counts by each vendor’s own figure: Easy MCP AI 280+, AI Engine “more than fifty”, WPVibe 37, Royal MCP 200+, Secure MCP Server 300+ | SEO and content only: 72 tools. Users, plugins, themes and header code are blocked |
| What needs your approval? | Varies. WPVibe pauses destructive operations for an in-chat approval with a dry-run preview, on by default | Every change in the areas you set to ask, approved in wp-admin. Fixed rules for robots.txt, noindex, deletes and trash can’t be switched off |
| Can a change be undone? | Varies. Easy MCP AI keeps a change history the AI can restore from (since 2.1.0) | A person can undo one change or a whole batch from the change log, with redo, without the chat |
| Who does the agent sign in as? | Varies. Secure MCP Server maps tools to WordPress roles | Its own SEO Agent user per connection, with its own Revoke |
| Is it also your SEO plugin? | None of the five in the source is an SEO plugin. SEO fields come from the one you run | Yes: titles, schema checked for 22 types before it saves, sitemaps, redirects, site check |
| Price | All five are on WordPress.org. Easy MCP AI is free | Paid licence. Early Adopter Lifetime from $49 |
Sources: tool counts and features as quoted in “5 Best WordPress MCP Server Plugins in 2026” (themeisle.com, updated 7 October 2026, read 30 October 2026), themeisle.com/blog/best-wordpress-mcp-server-plugins. Each vendor’s own figure; check their pages for changes.
If you want the agent to manage users, plugins, WooCommerce orders or page layouts.
If you want the agent on SEO and content, with your approval on the parts you choose.
“Sometimes a focused plugin is exactly the right answer, and sometimes you need the whole toolbox. I built AgentedSEO for the day a client’s live site is on the line.”
JoyFrom the team behind Classic Monks · building WordPress sites since 2017From install to the first change you approve, in three steps.
- 01
Install AgentedSEO and run the setup wizard.
Coming from another SEO plugin? The importer previews what will move and undoes in one click.
- 02
Connect your agent and run the self-test.
In AgentedSEO › Agents › Connections, pick “Add a custom connector” for Claude.ai or “Desktop or code app” for the others, paste the URL into your client, then click Run test under Test the connection.
- 03
Give it a first job and approve it.
Ask for one meta description, open Dashboard › Approvals, check the before and after, and click Approve. Undo it from the change log if you like.
Questions people ask before they connect an MCP server to a live site.
Still unsure? Try it in a sandbox.
Yes, several. The official MCP Adapter is a bridge that passes along abilities other plugins register. General-purpose WordPress MCP server plugins ship their own tools for the whole site. AgentedSEO ships one scoped to SEO and content at /wp-json/agentedseo/mcp, built into the plugin.
Any client that connects to a remote MCP server over HTTP. The docs have step-by-step guides for Claude, Cursor, Codex and Hermes, the four clients we have tested. Scripts can use the REST API or WP-CLI instead.
Yes. Each connection gets its own SEO Agent user, its own Last activity and its own Revoke. Claude on your laptop and Hermes on a server show up as two agents, and the change log says which one made each change.
No. The MCP endpoint is built into AgentedSEO, so there is no second plugin. Its tools are also registered with the WordPress Abilities API, so the Adapter can list them for your own account, but agent users only reach AgentedSEO’s endpoint.
The server tells every agent that site content is data, not instructions. That is guidance a model can still get wrong, so the hard limits sit on your site: the agent’s user can’t reach users, plugins or themes, risky changes always ask first, and everything is logged and undoable.
No. Users, roles, plugins, themes, header and footer code and permanent deletes are blocked for the SEO Agent role, whatever the approval rules say. It is also refused on every REST route outside AgentedSEO.
Yes. 100 items per bulk write, 1 MB of content, a 10 MB media upload, a 512 KB MCP request and batches of up to 20 MCP messages. Bulk changes over 20 items ask first by default.
No. AgentedSEO is a complete SEO plugin from the dashboard. While another SEO plugin is active, AgentedSEO holds back its own head output, so you can try it without two plugins printing tags. Importers for 10 SEO plugins preview first and undo in one click. See the switching pages
The one scoped to the job. For managing a whole site, a general-purpose server fits. For SEO and content on a live client site, with approval and undo, AgentedSEO fits. The comparison above lists the facts with sources.
The endpoint only runs when an agent calls it. AgentedSEO adds no JavaScript to your front end, and heavy work runs in the background, not on page load.
You have 15 days to ask for a refund, and you get 80% of what you paid back. Questions first? Write to [email protected].
An MCP server scoped to SEO, with the final say kept by you.
Early Adopter Lifetime: pay once, for 1, 25 or unlimited sites. Runs from 1 November to 1 December 2026, 23:59 PT, then closes.
Every licence includes the full plugin, the agent connection, every future update and support.
From 2 December: Solo $49 a year, Studio $99 a year, Agency $149 a year or $499 lifetime.
15-day refund (80% back)Questions? [email protected]
“I tested the agent workflow on 10 WordPress sites over 90 days. Published pages went from 3 to 12 a month, and my time went from 6 hours a month to 1.5.”
JoyFrom the team behind Classic Monks, building WordPress sites since 2017