Royal MCP Pro Documentation PRO

What Royal MCP Pro Adds

Royal MCP Pro bundles the free codebase and adds a Pro tier of tools designed for agencies and power users running WordPress work at scale. Every Free tool continues to work exactly as before — Pro is net-new capability, not features held back.

The six Pro pillars

Universal Audit Log

Every Pro tool call — successful, errored, or undone — writes a row to the Universal Audit Log. Free-tier tools also write to the log when Pro is active on the same site. The result is a complete, filterable, exportable trail of every AI-driven change to your site.

What's captured

• Who — WP user + auth method (API key or OAuth) + session identifier
• What — tool name, full serialized arguments (sensitive fields scrubbed), affected object type + ID
• When — timestamp, response status (success / error / undone), tool response summary
• Undo state — token, expiration, whether the operation was later reversed
• Client fingerprint — Claude Desktop / Cursor / ChatGPT / etc. with version

Admin viewer

The audit log lives at Royal MCP Pro → Audit Log in wp-admin. Paginated 50 rows per page. Filters for user, tool, date range, response status, and undo state. Per-row actions include "View full args" (JSON viewer) and "Undo this operation" for rows still within the 72-hour undo window.

Export

Filtered results export to CSV. The export is safe against CSV-injection attacks — leading =, +, -, and @ characters are quoted so Excel/Sheets don't execute them as formulas.

Retention

Default retention is 90 days. A daily cron prunes older rows. To change the retention window, use the royal_mcp_pro_audit_retention_days filter:

add_filter( 'royal_mcp_pro_audit_retention_days', function( $days ) {
    return 180; // Keep audit rows for 180 days
} );

Full concept guide: Understanding the Universal Audit Log →

72-Hour Undo Tokens

Every destructive Pro tool returns an undo block at the top level of its MCP tool-call response:

{
  "isError": false,
  "content": [{"type": "text", "text": "Bulk price update on 47 products — 12% off"}],
  "structuredContent": {...tool-specific fields...},
  "undo": {
    "token": "<64-character-hex-token>",
    "expires_at": "2026-08-08T14:23:15Z",
    "ttl_hours": 72
  }
}

Call royal_mcp_undo_last_operation with that token to reverse the operation. The undo store keeps the full payload needed to revert — original values, deleted rows, prior state — for the token's TTL.

Which tools support undo?

Every Pro tool that writes, edits, or deletes returns an undo token. Non-destructive read tools return the token block with a no-op flag for API consistency. Free-tier destructive tools also become undoable when Pro is active on the same site — wp_delete_post, wp_reorder_menu_items, and Gutenberg custom-CSS updates all get 72-hour recovery windows once Pro is licensed.

Who can trigger undo?

An undo call is authorized when the caller is any of the following: the original actor who ran the operation, a user with the explicit royal_mcp_pro_undo_any capability, a user with manage_options (single-site admins), or a super-admin on multisite. This lets your normal admin team recover from mistakes without giving every user the power to reverse each other's work — grant royal_mcp_pro_undo_any selectively if you want to tighten it further.

Full concept guide: Undo Tokens & Reversibility →

Builder Session Safety

Royal MCP Pro's Builder_Safety layer detects when the WordPress editor or a page builder (Divi 4, Divi 5, Elementor, block editor, Bricks, Beaver Builder, Oxygen) has an active editing session on a post. Write tools soft-error rather than clobber unsaved in-editor changes.

The mechanism is WordPress core's _edit_lock post meta — set by wp_set_post_lock(), read by wp_check_post_lock(). Because the guard hangs off core rather than any builder vendor, it works identically for every editor that respects the core lock.

Write-tool guard

Write tools return a soft error when an active session is detected:

{
  "error": "builder_session_active",
  "builder_session": { "active": true, "since": 1723029815, "source": "edit_lock", "editor_user_id": 3 },
  "hint": "Close the editor session on this post or pass force=true to override."
}

Pass force: true to bypass the guard when you know it's safe. See Builder Session Detected — When to Force Override for the decision framework.

In-flow Upgrade Prompts

When a Free-tier install attempts to call a Pro-only tool, the MCP response contains an agent-directive text block that surfaces the upgrade path as chat content in Claude, ChatGPT, Cursor, and other clients. The response is a successful envelope (isError: false) so the LLM presents it to the user, not routes around it as a failed tool call.

If you see the upgrade prompt in your Pro-licensed site, that's a bug — see Pro Tool Returned Upgrade Prompt with Valid License for the full diagnostic path.

Pro Tool Inventory

41 Pro tools ship in Royal MCP Pro 1.0.2 (plus the royal_mcp_undo_last_operation meta-tool). Grouped by category with links to per-category documentation:

Divi Pro (8 tools)

Elementor Pro (10 tools)

WooCommerce Bulk (6 tools)

Cross-plugin Composers (5 tools)

SEO Agency Suite (11 tools)

Undo (1 tool)

Troubleshooting

Pro-specific troubleshooting starts with Troubleshooting — Start Here, which extends the free-tier Royal MCP troubleshooting guide with Pro-specific triage.

Common Pro-specific issues:

• License activation fails — full diagnostic tree covering DNS, firewalls, license-server reachability, and seat conflicts
• Pro tool returned upgrade prompt with valid license — license-server sync issues, object cache, tier-check middleware
• Undo failed — token expired, consumed, handler missing, capability mismatch
• Builder session detected — when to close the editor vs. pass force=true

If your issue is with the underlying MCP connection (Claude.ai can't connect, ChatGPT DCR fails, host WAF blocks OAuth) — start with the free-tier troubleshooting guide. Those docs cover the same underlying MCP surface Pro uses.

Still Stuck? Two-Step Support Path

If a Pro tool isn't working, an activation is failing, or something you expected to happen didn't, work through these two steps in order — most Pro-tier failures resolve at Step 1 because they're actually the same underlying MCP-connection or host-layer issues covered in the shared Royal MCP troubleshooting flow.

Step 1: Start with the Royal MCP Troubleshooting Guide

Royal MCP Troubleshooting — Start Here covers the 4-step diagnostic checklist for MCP-layer issues: edge/host probes, cache and WAF interference, OAuth discovery failures, and connector-side error codes. If your issue is that Claude can't connect, the connector fails, or you're seeing an ofid_xxxxx error, that guide is where to start.

For Pro-specific patterns not covered there, see:

• License activation fails — full diagnostic tree covering DNS, firewalls, license-server reachability, and seat conflicts
• Pro tool returned upgrade prompt with valid license — license-server sync issues, object cache, tier-check middleware
• Undo token errors — expired, consumed, handler missing, capability mismatch
• Builder session detected — when to close the editor vs. pass force: true

Step 2: Email priority support

If you've worked through Start Here and the relevant Pro-specific doc and the issue still isn't resolved, email priority support from your purchase email address at support@royalplugins.com. Priority email support is included with your license — typical response within 24 hours. Never include your license key in email; we look it up from your purchase address.

Frequently Asked Questions

Do I need to remove the free Royal MCP plugin before installing Pro?

No. Royal MCP Pro bundles the free codebase and automatically deactivates the free plugin on activation. Your existing settings, OAuth clients, and API keys are preserved. Uninstall the free plugin at your convenience once Pro is running.

Which MCP clients work with Royal MCP Pro?

Every MCP-compliant client that works with the free plugin also works with Pro. Claude.ai web, Claude Desktop, ChatGPT, Cursor, Windsurf, VS Code, Zed, JetBrains AI, LM Studio, and Ollama frontends all connect the same way. Pro tools appear in the same tools/list response once your license is active.

What happens if my Pro license expires?

When your license expires, Pro tools return a short service message directing you to renew. Admin notices appear in the 30 days leading up to expiration so it's not a surprise. Free tools continue to work indefinitely — Pro never disables the free feature set. Renew any time from your account dashboard and Pro tools resume immediately.

Are Pro operations reversible?

Every destructive Pro tool returns a 72-hour undo_token in its response. Call royal_mcp_undo_last_operation with that token to reverse the operation. The full history lives in the Universal Audit Log with per-row undo actions.

How many sites can I run Pro on?

Personal tier covers 1 site ($99/yr). Professional covers 5 sites ($249/yr). Agency covers 100 sites ($999/yr). Above 100 sites is Enterprise territory — contact us for a partnership conversation. Seats can be moved between sites at any time from your account dashboard at my.royalplugins.com.

The first 100 Founding Members rate-lock the Personal tier at $79/yr — the rate never increases at renewal. (The license itself is still an annual subscription like every other tier; "rate-lock" refers to the price, not the renewal cycle.)

Do Pro tools affect front-end performance?

No. Royal MCP Pro only activates when an MCP client makes a tool call. There is no front-end footprint on regular visitors.

Can I get a refund if Pro doesn't fit my workflow?

Yes. 30-day money-back guarantee — reach out to support with your reason and we'll process a full refund within 3-5 business days. Full refund policy.