Most of the AI tooling that lands in my inbox wants to write your content for you. Far more interesting, at least from where I sit, is a tool that lets an AI client do real work inside a site you already run.
That is the job an MCP server does, and there are more of them appearing for WordPress every month. That’s why I’m sharing Royal MCP Pro today.
Royal Plugins has just opened Founding Member pricing on the Pro version. The seats are capped, the rate you sign up at is the rate you keep, and once the seats fill the plugin moves to standard pricing. So while the offer is still hot, here’s what it actually does and what the offer covers.
What Royal MCP Pro Does
Royal MCP Pro is a self-hosted MCP server for WordPress. It connects to Claude, ChatGPT, Gemini, Perplexity, or any other MCP-compatible client, and gives that client structured access to your site through 300+ tools.
The scope is wider than most WordPress MCP servers I’ve seen. It covers WooCommerce bulk operations, authoring and editing in both Elementor and Divi, along with a full SEO suite aimed at agency work.
Authentication runs through OAuth 2.0 with PKCE, straight from your AI client to your site. There is no proxy in the middle, no telemetry going anywhere, and no third party sitting on your content while it moves.
Plenty of AI integrations route your site data through someone else’s infrastructure, and if you ‘re working on client sites under contract, that’s a conversation you probably don’t want to have, so the last point above becomes even more important.
The Undo Token Is the Real Feature
Read access is easy to feel comfortable with, but write access is where people hesitate, and they are right to.
Giving an AI client permission to bulk edit 400 WooCommerce products is a lovely idea until it does exactly that and you cannot remember what the prices were an hour ago.
Royal MCP Pro handles this in two ways.
- Every tool call gets recorded in a searchable activity log, so you can see what was run, when, and against what.
- Every destructive operation returns an undo token that you can use for up to 72 hours after the fact.
Three days is a sensible window since it can cover both the mistake you spot immediately and the one a client emails you about on Monday morning.
I would still want that log reviewed rather than trusted blindly, but per-tool reversibility changes the risk calculation on bulk work in a way that access controls alone never do.
The Composer That Collapsed Five Tool Calls Into One
Version 1.0.8 shipped on 2 September and introduced the piece I find most interesting for agencies, which is a composer called seo_optimize_for_launch.
One AI call runs an SEO audit on a post, fixes the meta, verifies schema, sets up 301 redirects, pushes to IndexNow, notifies Google Search Console, and purges the cache. If any step in that chain fails, the whole thing rolls back.
That workflow previously took five or more separate tool invocations, which meant five or more chances for the AI to wander off script halfway through. Chaining it into one call with a single rollback path is the kind of practical thinking that suggests someone on that team has actually launched content for clients.
There are cross-plugin composers beyond that one, along with custom endpoint profiles for restricting what a given client can touch.
What Founding Member Pricing Covers
The free version on WordPress.org has passed 10,000 active downloads, and it remains the sensible way to test whether MCP fits how you work. Pro is there to reach for once you’re running bulk operations across a fleet of sites and need every write logged with a way back.
Founding Member pricing looks like this:
- Personal tier at $79 per year for a single site licence, aimed at bloggers, freelancers, and anyone running their own store.
- Agency tier at $500 per year for the first five buyers, covering 100 sites. The next five seats go at $750 per year.
- Your rate is locked for life. Whatever you sign up at becomes your permanent renewal price, with no increase when the founder window closes.
If you’43 an agency maintaining anything close to 100 sites, the maths on the $500 tier is not really a debate. For a single site owner, the question is whether you’re running enough repetitive work through an AI client to justify $79 a year over the free version, which in most cases is likely going to be a “yes”.
Worth a Look If You’re Already Experimenting
MCP servers for WordPress are still early enough that most of the products in this space are competing on how many tools they expose. Royal MCP Pro is competing on what happens after those tools run, and I think that’s a smart position to hold as more people hand write access to their AI clients.
The Founding Member window is live now on the Royal MCP Pro website, and given how few seats are on the agency tier, it will not stay open long.
If you’ve already connected an AI client to a WordPress site you are responsible for, I’d love to know what you put in place before you allowed it to write anything. Log everything, restrict the tools, keep it on staging, or something else entirely?
