The Pro tier of Royal MCP: 100+ tools for solo devs, freelancers, and agencies. Built on top of the Free plugin: Divi 4 + Divi 5 native authoring, Elementor Pro depth, WooCommerce bulk ops, SEO Agency Suite, FormForge Pro operations, Royal Affiliate Pro operations, ACF Setup Suite, cross-plugin composers, custom Endpoint Profiles, universal audit log, and 72-168 hour undo tokens.
Free is safety-first WordPress MCP: reads, single-op writes, diagnostic tools. Pro is the reversible-runtime layer: depth, bulk ops, custom endpoints, composers, and every write logged with a 72-168 hour rollback path. Included with every Royally plan, alongside Royally in the cloud.
Royal MCP Pro works with every MCP-capable client out of the box and with any other AI platform via WordPress’s REST API.
The plugin on each site and the guardrails in the cloud, shown in five minutes.
Every Pro tool call is logged, undoable, and scoped by role. Here's what that looks like in your WordPress admin.
Everything about the site on one screen: your MCP URL with setup steps for Claude, ChatGPT, Claude Code, Codex, Cursor and VS Code, the tools each AI client gets, connected clients, safety mode and your license. Below that sit what needs attention, recent AI activity and the Royal plugins on the site.
When Royally manages a site, every other connection can only read, and only Royally can change the AI permissions. This page shows what each connection can do right now, the few settings Royally may change, and a PHP error record so you and your AI can see what broke.
Every MCP tool invocation logged with tool name, user, status, and undo state. Filter by tool, user, date range, or search. Export as CSV. Cross-linked into Royal AI Firewall for at-a-glance AI activity.
Weekly telemetry on every MCP request, including total volume, unique clients, protocol version split, top clients by name, and method-call frequency. Spot version drift, identify which agents hit hardest, and export the raw week as JSON.
Every destructive Pro tool call within the 72-168 hour undo window is listed here with an active Undo button. One click reverses the operation — no CLI, no rollback SQL.
Ship a locked-down Content Writer profile for a contractor, a read-only SEO Auditor for a client, or a full WooCommerce Manager for your team — each with its own scoped endpoint URL, all from the same install.
Other plugins' WordPress abilities become tools on your Royal MCP connection, a whole plugin or one ability at a time. Offer Rank Math's 404 log without the abilities that change its settings. Every ability is marked as reading or changing the site, and every call is logged.
Flip on Require approval before new AI clients can connect and every dynamically-registered client queues here before it can touch the site. Inspect the redirect URI, source IP, and user agent per row, then Approve or Reject. The admin bar carries a live count badge so requests never sit unnoticed.
Configure access-token time-to-live per WordPress role. Tighter windows for administrators, looser for contributors. Multi-role users default to the longest applicable TTL, filterable via royal_mcp_pro_oauth_role_ttl_policy.
Everything above runs on each WordPress site. Royally is the workspace across all of them: your AI agent asks, a person on your team approves, and every change ends in a receipt you can undo.
Claude or ChatGPT asks for a change on one site or many.
The change waits in your approvals inbox. Approve it, and Royally keeps the receipt.
The plugin applies it, logs it and holds the undo token.
See how Royally works → · Royally is optional: connect your AI agent straight to a site any time.
Free runs your AI's tools against WordPress. Pro governs every destructive call on each site, and Royally carries those guardrails across your whole fleet in the cloud: approvals, bulk actions, one record of every change, and undo. Runtime alone isn't enough for production.
The runtime. 270 tools (113 native + 157 integration) that read your site and make safe single-op writes, with format-aware handling across Divi, Elementor, and Gutenberg. Free on WordPress.org, forever.
.mcpb)Everything Free does, wrapped in production-grade guardrails on each site, plus Royally in the cloud to run and govern your whole fleet. Every write logged. Every destructive call reversible. Every session scoped. Plus deeper Divi, Elementor, WooCommerce, and SEO tools for real workflows at any scale.
One plugin install, included with every Royally plan. Everything in Free plus these workflow layers.
Both builder generations first-class. 9 Free-tier tools cover the read + safe-write surface — page clone, format detection, outline, image swap, template import, library reads, layout validation, find-and-replace. Pro adds 6 more on top: library CRUD (create / update / delete), divi_apply_global_preset for design-token bulk-apply, divi_convert_shortcodes_to_blocks for D4→D5 migration at scale, and native Divi 5 module authoring via divi5_scaffold_block.
Widget CRUD, Theme Builder operations, display conditions, template ops, bulk widget setting replace, plus V4 authoring: global variables and reusable classes as first-class tools, bulk atomic element operations (up to 50 create / update / move / delete per call with all-or-nothing rollback), and JSON-driven section composition. Additive to Elementor's own MCP module — not competitive.
Read the Elementor Pro guide →Bulk product update / delete, bulk stock management, bulk category assign, bulk price update (two-step commit), bulk order status, bulk variation updates, WC Subscriptions bulk price updates, plus first-class grouped-product children CRUD (list, set, add, remove simple-product members). HPOS-compatible. Store management at scale with an undo token on every batch.
Read the WooCommerce guide →Tools that compose across the Royal Plugins family — seo_optimize_for_launch (audit + auto-fix meta + schema verify + 301 redirects + IndexNow + GSC push + cache purge in one call, full LIFO rollback), wp_publish_and_promote_pro (publish + optional SEO automation block), wp_prepare_for_launch, wp_monthly_maintenance_report, wp_migrate_theme_assets. Plus wp_bulk_find_and_replace across post content, meta keys, Elementor JSON, and Gutenberg blocks — two-step commit, per-post pre-op snapshots, 72-168 hour undo.
Build your own AI-facing REST surface — pick which tools each profile exposes, gate by role or scope, filter what shows up in tools/list. Ship a locked-down "content-editor" profile for a client's site alongside your own full-access agency profile from the same install.
Pre-launch audit workflow that sweeps SEO gaps, broken links, missing schema, permalink issues, and redirect coverage in one composer call. Rollup report, rollback path via SiteVault snapshot integration, and IndexNow + Search Console push on the go-live step.
Read the launch readiness guide →Read individual entries and per-form analytics, paginated bulk entry export, bulk delete entries with 72-168 hour undo, form duplication, spin up new forms from templates, and re-fire email notifications for a batch of entries. Preview before every destructive write.
Full-lifecycle affiliate program management from your AI client. Read performance snapshots and referral records, review fraud incidents, create campaigns and challenges, bulk-upload creative assets, list and assign landing pages, bulk-approve affiliates or update referral status with undo, bulk-generate payouts and WooCommerce coupons, bulk-tag affiliates, bulk-update category and product commission rates, grant store credit, broadcast to segmented affiliate groups, force-fire monthly reports, and run fraud scans against historical visits and referrals — all with two-step preview + commit and 168-hour undo where reversible.
Ed25519-signed NDJSON audit exports with a standalone offline verifier, Legal Hold that survives retention pruning, GDPR field redaction with chain-of-custody event log, and Endpoint Profile templates + per-session version pinning. The compliance layer your auditor is going to ask about the first time an AI writes to a client’s site.
Field group CRUD (create, clone, update, delete), JSON round-trip import and export, field-level operations (add, update definition, delete, reorder), introspection (read full group config, list every supported field type), plus site-setup primitives — options pages, custom post types via ACF Pro’s CPT UI, and ACF Blocks that render via existing template files. Set up ACF end-to-end from your LLM of choice.
SEO Agency Suite, the Reversible Runtime layer (audit logs, undo function & OAuth TTLs), and the Governance layer each have their own sections below.
Portfolio-scale audits, bulk meta writers across every major SEO plugin, and Redirection plugin ops — all with two-step dry-run and full audit trail. Whichever SEO plugin your site (or your client’s site) already uses, your AI writes to it natively.
Two-step dry-run + commit token on every write — preview the diff, then commit if it looks right. Per-post rollback if you change your mind.
The universal fear with AI on WordPress: what if it deletes the wrong thing or wrecks a client’s site? Every destructive Pro tool issues an undo token. Every write goes to the universal audit log. Every session runs under a per-role OAuth time limit. This is the reversibility half of agentic WordPress — the safety net that comes standard.
Every destructive tool returns a dry-run manifest first, so you see every row, every field, every change before anything writes.
Approve the manifest with a commit token to actually run the operation. Nothing writes without your explicit go-ahead.
Every commit issues a 72-168 hour undo token. One call reverses the whole operation, whether it was a single write, a batch, or a bulk.
Every write captured with tool, user, MCP session, target, response status, and undo-token linkage. 90-day default retention. Admin viewer with filters + CSV export. GDPR-aware — deleted_user hook scrubs identifiers.
Every destructive Pro tool issues a 72-168h undo token. One-shot consumption. Cap-checked against the actor who ran the original operation. Dedicated royal_mcp_undo_last_operation tool for reversal.
Batch operations reverse in a single call. Builder-session collision guard soft-errors write tools when someone’s mid-edit in Divi, Elementor, or the block editor (_edit_lock detection).
Time-limit OAuth sessions per role — tokens can’t outlive their scope. Combines with Custom Endpoint Profiles to gate exactly which tools each connection can touch, per role, per site.
Every pattern below is a real class of failure with AI-to-WordPress tools that generate PHP against your site or write files directly. Our architecture is different by design and here’s what that means in practice.
An AI overwrites your entire post with a single heading when asked to add one section.
Every write is scoped to the specific element, block, or field named in the tool call, never a whole-document replace. The preview manifest surfaces every touch before commit.
An AI edits one widget setting and silently reorders unrelated elements on the same page.
Writes touch only the targeted widget’s known schema fields, so no whole-page re-serialization. If anything else drifts, the undo token restores exact prior state.
AI-authored PHP triggers a fatal error that crashes every request on your site until you restore from backup.
AI writes PHP only if an administrator turns on PHP snippets for Code Snippets or WPCode. Everything else goes through tested tools with strict input and output schemas.
A batch operation touches 50 products, half were wrong, and there’s no way to reverse just the affected rows.
Bulk operations issue a single undo token that reverses the entire batch in one call. Selective subsets reverse row-by-row from the Recent Operations page.
Two-step commit + universal audit log + 72-168 hour undo tokens combine so every AI action is previewed before commit, logged after commit, and reversible within the window. That’s the reversibility half of production-safe AI on WordPress.
The MCP wave has reached WordPress. Elementor ships an MCP server, and WooCommerce has one in developer preview. Every major plugin author is asking the same question — “should we ship our own MCP server?” — and for most of them the honest answer is yes.
Which puts the burden on you. Every plugin that ships its own MCP is another endpoint to configure in Claude Desktop, another OAuth flow to walk through, another token to rotate, another health surface to babysit. Multiply that across the plugins on a typical WordPress site, times the AI clients your team uses, times the number of client sites you manage — and you’re running a fleet of connectors instead of your actual work.
One connector, one OAuth, one health surface — running your whole plugin fleet. Whether that’s your one site, five client sites, or a hundred. That’s Royal MCP Pro.
Every architectural decision aimed at agencies that ship real client work — not usage caps you have to buy your way out of.
No daily quotas and no per-call charges. Every tool call is included on every plan. Royal MCP blocks abuse and runaway loops with a per-minute safety limit that normal and bulk work stays well under.
Claude, ChatGPT, and Cursor connect to your WordPress site directly, with no relay in the loop. Want approvals and receipts across sites? Connect the site to Royally too; it's your choice per site.
Every Divi tool works on both format versions — no "primary vs fallback" lane, no Divi 4 as legacy tail. Native block emission for Divi 5, native shortcode authoring for Divi 4, with a per-post format detector that reads _et_builder_version instead of guessing from the theme.
The universal fear with AI on WordPress: "what if it deletes the wrong thing or wrecks a client's site?" Endpoint Profiles let you pre-set exactly which tools an AI connection can touch — read-only for one profile, content edits for another, full agency access for you. Scoped per profile, per role, per site. The safety net comes standard.
Every Royally plan includes Royal MCP Pro on its sites. Whether you run three sites or a hundred, you get the same tools; plans differ only in sites and seats.
“Own sites, own edits, own AI stack.”
“Direct MCP. Read every line. Extend via hooks.”
“Fleet-scale flat rate. Every write reversible.”
100+ Pro-tier tools exposed via MCP JSON-RPC, grouped by integration. Click any category to see the exact tool names your AI client will see.
Every plugin Royal MCP Pro extends. Click any card to see the exact Pro-tier tools that light up when the plugin is installed.
Divi 4 + Divi 5 both first-class. Per-post format detector reads _et_builder_version.
Elementor Pro
14 tools
Additive to Elementor's own MCP module — not competitive. Both work side by side. Includes V4 authoring: global variables, reusable classes, bulk atomic element ops (up to 50 per call), and JSON section composition.
ACF Setup Suite
15 tools
Set up ACF end-to-end from your LLM of choice — field groups, JSON round-trip, field-level CRUD, custom post types, options pages, and ACF Blocks. Options pages, blocks, and CPT UI require ACF Pro (6.1+ for CPT).
WooCommerce Pro
12 tools
HPOS-compatible. Bulk delete has two-step confirm above 10 products + active-subscriptions safety guard. Grouped-product children (list, set, add, remove) now first-class CRUD.
WooCommerce Subscriptions
5 tools
List, pause, resume and cancel subscriptions and move the next payment date. Cancelling asks for a confirm step first.
Yoast SEO
6 tools
5 read and write tools from the free plugin, plus yoast_bulk_update_meta from the Pro SEO Agency Suite.
Rank Math
2 tools
SEOPress
1 tool
AIOSEO
1 tool
SEObolt
9 tools
The last seven appear when SEObolt Pro is installed.
FormForge Pro
7 tools
Requires FormForge Pro (separate Royal Plugin). Pro-tier tools light up automatically when installed.
Royal Affiliate Pro
25 tools
Requires Royal Affiliate Pro (separate Royal Plugin). Pro-tier tools light up automatically when installed. Full-lifecycle affiliate program management: read affiliate performance, campaigns, creatives, payouts, and audit log; write campaign and challenge creation, landing page assignment, bulk affiliate tagging, commission rate updates, store credit grants, targeted broadcasts, monthly report delivery, and fraud scans — every write ships with two-step preview and 168-hour undo where reversible.
UpdraftPlus
4 tools
Async dispatch pattern so the MCP transport doesn't time out on big backups.
WPForms
4 tools
Submission access requires WPForms Pro (Lite installs return an unavailable state).
Solid Security
4 tools
Also detects iThemes Security and Kadence Security Basic (same underlying class).
Wordfence
8 tools
Contact Form 7
3 tools
Submission access requires the Flamingo companion plugin.
MonsterInsights
4 tools
W3 Total Cache
3 tools
LiteSpeed Cache
4 tools
Duplicator
3 tools
BuddyPress
4 tools
Integration tools auto-load only when the host plugin is active — no overhead if you don't use them.
We built Royal MCP Pro assuming the ecosystem wouldn’t fix itself. The four numbers on the right come from published third-party research, not our marketing.
Pro adds a governance layer designed for agencies running multi-client environments: OAuth 2.1 with DCR on every install, per-tool permission gates plus custom rmcp_pro_* caps, a hash-chained activity log for every AI-initiated action, and the Ed25519-signed audit exports covered below. The pieces auditors actually ask for.
of MCP servers use OAuth.
Astrix Security audit, 5,200+ servers, October 2025.
publicly accessible MCP servers. Roughly half have no authentication in place.
Censys internet scan, May 2026.
zero-day vulnerabilities in an academic scan of 39,884 MCP repositories.
arXiv research, May 2026.
critical vulnerability in a popular MCP proxy shipped across 437,000+ environments.
CVE-2025-6514, NIST database.
Reversibility protects the site. Governance protects the story you tell about the site. Every activity row hash-chains to the previous one. Every export carries a cryptographic signature auditors can verify offline. Every retention rule respects Legal Hold overrides and GDPR erasure paths. This is what your compliance officer is going to ask about the first time an AI writes to a client’s WordPress install.
Newline-delimited JSON audit exports with an Ed25519 signature on every row and the manifest. A standalone verifier script ships in bin/ — an auditor validates the whole chain offline without touching the site. Chain integrity via sha256(prev_row_hash + canonical_json(row)).
Flag any row with a reason, timestamp, and who placed it. Held rows survive the retention prune regardless of age — useful the moment an investigation opens. Release requires the royal_mcp_pro_audit_unhold capability, granted separately from manage_options.
Surgical erasure of PII fields (IP, args, response text) inside audit rows. A companion event log records the SHA-256 of what was removed — chain-of-custody evidence without keeping the sensitive value. Redaction target is an allowlist so structural fields stay intact.
Endpoint Profile templates seed reusable per-client configurations with controlled override slots — ship the same governance baseline to every client, allow per-client customization only where you allow it. Version pinning freezes the profile shape per AI session so mid-flight edits don’t affect running conversations.
Walk-throughs for the workflows you'll build once and repeat weekly — Divi authoring, store bulk ops, SEO writes, plus the write history behind every AI edit.
_et_builder_version rather than guessing from the theme, so mixed-format sites work correctly. Divi 4 is not a "legacy fallback" lane — it's a shipping target on equal footing with Divi 5./wp-json/royal-mcp/v1/mcp past your cache and security plugin once, and it keeps working as we add more integrations. Your AI still sees "your WordPress site," not a growing list of URLs to babysit. And if a plugin ships its own MCP and you'd rather use their tools directly, Royal MCP Pro doesn't interfere — you can run both side by side.One plan covers both, from $89 a year. Every plan has every Pro tool and every future Pro release; plans differ only in sites and seats.
VAT invoices · Cancel any time · Already have a Pro license?