Royal MCP vs WPVibe
How Royal MCP compares with WPVibe for WordPress users who want a full access bridge to their site, without a per-day cap or third-party cloud relay.
| Numbers that decide it | Royal MCP | WPVibe |
|---|---|---|
| Free tier | $0 forever · unlimited tool calls · 250+ tools | $0 · 100 tool calls/day |
| Paid entry | $89/year (Royally Solo with Pro, 3 sites) | $99/year (500 calls/day) |
| Top tier cap | 250 sites, unlimited tool calls | $899/year, 10,000/day hard cap |
| Data path | Direct: your WordPress to your AI client | Cloud relay: through wpvibe.ai servers |
| Local / staging / firewalled sites | Works out of the box | Requires cloudflared tunnel setup |
| License | GPL, open source project | GPL plugin, closed-source hosted service |
Data pulled: October 2026
The Seven Differences That Matter
Site-count comparison note: Royal MCP Pro comes with every Royally plan; Solo at $89/yr covers 3 sites. WPVibe Pro at $99/yr covers unlimited sites at a metered daily tool call cap on the account. If you manage many sites but call each one lightly, WPVibe's account-wide cap is designed for that shape. If you work deep on fewer sites, Royal MCP Pro's per-site licensing removes the daily-cap ceiling entirely. See the Usage Caps table below for the exact Pro-tier number.
When to Pick Which
Both plugins ship real capability. They're built for different agency shapes. Here's how to know which one is yours.
You spread light activity across many sites
- You manage 20-60 client sites but only touch each one occasionally
- Your typical monthly call volume per site fits comfortably under a shared daily cap
- You prefer a hosted service — someone else's uptime, someone else's OAuth infrastructure, and a wide list of supported AI clients
- You're OK with client-site content flowing through a third-party relay endpoint on every tool call
- You're already in the Awesome Motive ecosystem and want another tool from that vendor
- You want metered pricing that fits light-touch, occasional-use workflows
You work deep on portfolio sites
- You run bulk migrations, active builds, or cross-plugin composers on a smaller set of client sites
- You need unlimited daily tool calls per site — no ceiling on how much AI-driven work you push through
- Client data can't route through a third-party relay for compliance, contract, or trust reasons
- You need first-class Divi 4+5 depth (15 Divi tools total: 9 Free-tier + 6 Pro-tier including the shortcode-to-blocks migrator) or Elementor depth (28 tools: 14 Free-tier + 14 Pro-tier)
- You need WooCommerce Pro bulk ops with two-step commit + 72-168h undo on every batch
- Each client or teammate gets their own connection that only sees the tools you allow (Custom Endpoint Profiles)
- Universal audit log on every write is required for client work
- You look after several client sites and want them in one place: Royally, included with every plan, gives you one dashboard, approval before AI changes go out and one record of every change with undo
Architecture & Data Routing
| Capability | ProRoyal MCP | ProWPVibe |
|---|---|---|
| Client-to-WordPress connection | Direct — AI client to your WordPress | Via hosted relay (mcp.wpvibe.ai) |
| Where the MCP server runtime lives | On your WordPress install (self-hosted plugin) | On vendor infrastructure (SaaS relay) |
| Third-party endpoint in critical path | None | Vendor-operated dashboard host |
| Access paths / transport surfaces | 3 — native MCP + WP Abilities REST + WordPress MCP Adapter | 1 — proprietary relay endpoint |
| Tools exposed as WordPress Abilities API standard | Yes — all 400+ tools auto-register on WP 6.9+ | Runs other plugins’ abilities; own tools not documented as abilities |
| OAuth 2.1 authorization code + PKCE-S256 | OAuth for the AI client; site linked by Application Password | |
| Dynamic Client Registration (DCR) | Not documented | |
| Where credentials live | On your WordPress database | Encrypted Application Password stored by WPVibe |
Data pulled: October 2026
Setup Complexity
| Scenario | Royal MCP | WPVibe |
|---|---|---|
| Production WordPress (public URL) | Install, grab MCP URL, create connector, authorize | Install + authorize |
| Local WordPress (Local by Flywheel, MAMP) | Install, grab MCP URL, create connector, authorize | Install cloudflared and run a tunnel with --http-host-header; MAMP and similar also need a wp-config.php edit |
| Staging / VPN / firewalled site | Works out of the box | Cloudflared tunnel workaround required |
| Auth options | OAuth 2.1 (recommended) or API key | OAuth for the AI client, Application Password for the site |
Data pulled: October 2026
Usage Caps
| Capability | Royal MCP | WPVibe |
|---|---|---|
| Daily tool call limit | No cap on any tier | 100 Free · 500 Pro · 2,000 Power · 5,000 Agency · 10,000 Scale |
| Cap enforcement behavior | N/A (no cap) | Calls blocked until the rolling 24-hour window frees up; one-time Scale Day boost available |
| Cap shared across sites | No, per-site licensing | Yes, one daily bucket across every site on the account |
| Site count included | 3 / 5 / 25 / 100 (Solo / Freelancer / Studio / Agency) | Unlimited sites (account-wide cap) |
| What counts as a tool call | N/A | List/edit content, file changes, WP-CLI, media uploads. Connecting a site and failed calls don’t count. |
Data pulled: October 2026
WooCommerce Coverage
| Capability | Royal MCP | WPVibe |
|---|---|---|
| WooCommerce reads (products, orders, customers) | Via REST API | |
| Dedicated bulk operation tools | 6 dedicated tools | Generic REST-driven |
| Two-step commit on bulk writes (dry-run token) | On bulk price updates | Approval prompt on destructive operations |
| Bulk stock management + variation batch updates | Dedicated tools | Manual REST composition |
| Undo on bulk operations (72-168h token) | No undo (trash only) | |
| Order-status writes | Bulk + audited | Via REST API |
Data pulled: October 2026
Divi Coverage
| Capability | Royal MCP | WPVibe |
|---|---|---|
| Divi 4 (classic shortcode) support | Divi support listed; version not specified | |
| Divi 5 (block) support | Divi support listed; version not specified | |
| Shortcode-to-blocks migrator (D4 to D5) | Dedicated tool | Not mentioned |
| Page cloning workflow | Dual-format aware | Not mentioned |
| Library CRUD (create / update / delete) | Not mentioned | |
| Global preset apply (bulk) | Not mentioned | |
| Template import | Not mentioned | |
| Total dedicated Divi tools | 15 tools (9 Free + 6 Pro) | No dedicated tools; edits through Divi’s own save pipeline |
Data pulled: October 2026
Elementor Coverage
| Capability | Royal MCP | WPVibe |
|---|---|---|
| Base editability (Elementor v4) | Full builder edits (also Bricks, Breakdance, Beaver Builder) | |
| Widget CRUD (create / update / delete by ID) | Dedicated tools | Not mentioned |
| Theme Builder operations | Not mentioned | |
| Display conditions | Not mentioned | |
| Bulk widget setting replace across pages | Not mentioned | |
| Total dedicated Elementor tools | 28 tools (14 Free + 14 Pro) | No dedicated tools; Elementor guidance skill plus save pipeline |
Data pulled: October 2026
Theme & Site Intelligence
| Capability | Royal MCP | WPVibe |
|---|---|---|
| Theme editing (draft, preview, publish) | Not shipped | Isolated draft workflow |
| Classic-theme builder with Tailwind | Classic theme builder; Tailwind not stated | |
| Site intelligence read (plugins, themes, PHP, health) | Diagnostic tools | |
| Unsplash image search | ||
| Safe code snippets via WPCode (PHP/JS/CSS) |
Data pulled: October 2026
Safety Layer
| Capability | Royal MCP | WPVibe |
|---|---|---|
| 72-168 hour undo tokens on writes | Every destructive Pro tool | No general undo (trash, draft-first posts, theme backups) |
| Universal audit log | Every write logged | Approval Log of approved operations |
| Custom Endpoint Profiles (per-connection scoping) | Not mentioned | |
| Two-step commit pattern (dry-run then commit) | Bulk price + find-and-replace | Approval prompt with preview on deletes, SQL and search-replace |
| Builder-session collision guard | _edit_lock detection | Not mentioned |
Data pulled: October 2026
SEO Plugin Coverage
| Capability | Royal MCP | WPVibe |
|---|---|---|
| Rank Math support | Generic REST plus an SEO skill | |
| AIOSEO support | Generic REST plus an SEO skill | |
| Yoast + SEOPress support | Both included | Generic REST plus an SEO skill |
| Portfolio-scale SEO audit tool | wp_audit_seo_bulk | Not mentioned |
| Dedicated SEO Agency Suite | 11 tools | Generic REST |
Data pulled: October 2026
Modern MCP spec + Agent Readiness signals
Royal MCP Pro inherits every connection path from Royal MCP Free, including the WebMCP browser-agent standard and the standard well-known discovery documents that Cloudflare Agent Readiness, Vercel is-agentic, and Chrome Lighthouse 13.3+ Agentic Browsing all check for. WPVibe's public materials describe a hosted-gateway architecture with OAuth onboarding but do not mention any of these signals.
| Capability | Royal MCP | WPVibe |
|---|---|---|
| WebMCP browser-agent standard (cookie + nonce) | One toggle in settings | Not mentioned |
MCP Server Card at /.well-known/mcp/server-card.json |
Auto-published on install | Not mentioned |
Agent Skills Index at /.well-known/agent-skills/index.json |
Auto-published on install | Not mentioned |
RFC 8288 Link headers on /mcp responses |
Emitted on every response | Not mentioned |
| OAuth Protected Resource metadata (RFC 9728) | Published at RFC 9728 path | Not mentioned |
| MCP 2026-07-28 spec revision + multi-version negotiation | 4 revisions supported (2024-11-05, 2025-06-18, 2025-11-25, 2026-07-28) | Not mentioned |
Data pulled: October 2026
Sources: wpvibe.ai, wp.org plugin listing, public GitHub repo. See the Agent Ready feature page and Ways to connect feature page for the Royal MCP side.
Pricing
| Capability | Royal MCP | WPVibe |
|---|---|---|
| Free tier available | WordPress.org (unlimited sites) | 100 calls/day (unlimited sites) |
| Starting paid price | $89/yr (Royally Solo, 3 sites) | $99/yr (Pro tier) |
| Pricing model | Plans priced by site count (unlimited calls) | Metered by daily tool call cap |
| Site-count structure | 3 / 5 / 25 / 100 site plans | Unlimited sites, tier by call cap |
| Refund window | 30-day money-back guarantee | 14 days on first paid subscription |
Data pulled: October 2026
Running more than one AI plugin?
Royal MCP works next to the AI plugins you already run
SEO, AI and MCP plugins now ship their own AI sign-in. Royal MCP signs Claude and ChatGPT in at its own address, answers its own sign-in documents first and names any plugin that collides, so you can keep the plugins you rely on.
How Royal MCP works next to other MCP plugins →Deep work on a WordPress portfolio?
Direct-connect architecture, no daily cap, 100+ dedicated Pro tools, and 72-168 hour undo on every write. Try Royal MCP Free from WordPress.org, or get Pro with any Royally plan from $9 a month.