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 · 200+ tools | $0 · 100 tool calls/day |
| Paid entry | $79/year (Pro, 1 site) | $99/year (500 calls/day) |
| Top tier cap | 100 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 | Proprietary SaaS |
The Seven Differences That Matter
Site-count comparison note: Royal MCP Pro at $79/yr covers 1 site (Personal Founder). 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
- 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 Pro depth (10 tools)
- You need WooCommerce Pro bulk ops with two-step commit + 72-168h undo on every batch
- You run FormForge Pro or Royal Affiliate Pro and want AI-scriptable coverage on those (14 dedicated tools with 72-168h undo on every destructive write)
- Universal audit log on every write is required for client work
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 300 tools auto-register on WP 6.9+ | Consumes others’ abilities; own tools stay proprietary |
| OAuth 2.1 authorization code + PKCE-S256 | Application Password only (per WPVibe docs) | |
| Dynamic Client Registration (DCR) | N/A — non-OAuth flow | |
| Where credentials live | On your WordPress database | Vendor-managed dashboard |
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, run tunnel with --http-host-header, edit wp-config.php, authorize |
| Staging / VPN / firewalled site | Works out of the box | Cloudflared tunnel workaround required |
| Auth options | OAuth 2.1 (recommended) or API key | Application Password required |
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) | Further calls blocked until allowance resets |
| Cap shared across sites | No, per-site licensing | Yes, one daily bucket across every site on the account |
| Site count included | 1 / 5 / 100 (Personal / Professional / 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. |
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 | |
| Bulk stock management + variation batch updates | Dedicated tools | Manual REST composition |
| Undo on bulk operations (72-168h token) | Not mentioned | |
| Order-status writes | Bulk + audited | Via REST API |
Divi Coverage
| Capability | Royal MCP | WPVibe |
|---|---|---|
| Divi 4 (classic shortcode) support | Not mentioned | |
| Divi 5 (block) support | Global headers/footers | |
| 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) | Support included, count not published |
Elementor Coverage
| Capability | Royal MCP | WPVibe |
|---|---|---|
| Base editability (Elementor v4) | Full builder edits | |
| 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 | 10 tools | Support included, count not published |
Theme & Site Intelligence
| Capability | Royal MCP | WPVibe |
|---|---|---|
| Theme editing (draft, preview, publish) | Not shipped | Isolated draft workflow |
| Classic-theme builder with Tailwind | ||
| Site intelligence read (plugins, themes, PHP, health) | Diagnostic tools | |
| Unsplash image search | ||
| Safe code snippets via WPCode (PHP/JS/CSS) |
Safety Layer
| Capability | Royal MCP | WPVibe |
|---|---|---|
| 72-168 hour undo tokens on writes | Every destructive Pro tool | Not mentioned |
| Universal audit log | Every write logged | Not mentioned |
| Custom Endpoint Profiles (per-connection scoping) | Not mentioned | |
| Two-step commit pattern (dry-run then commit) | Bulk price + find-and-replace | Not mentioned |
| Builder-session collision guard | _edit_lock detection | Not mentioned |
SEO Plugin Coverage
| Capability | Royal MCP | WPVibe |
|---|---|---|
| Rank Math support | ||
| AIOSEO support | ||
| Yoast + SEOPress support | Both included | Not mentioned |
| Portfolio-scale SEO audit tool | wp_audit_seo_bulk | Not mentioned |
| Dedicated SEO Agency Suite | 11 tools | Generic REST |
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 |
Sources checked September 2026: 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 | $79/yr (Personal Founder, 1 site) | $99/yr (Pro tier) |
| Pricing model | Per-site licensing (unlimited calls) | Metered by daily tool call cap |
| Site-count structure | 1 / 5 / 100 site tiers | Unlimited sites, tier by call cap |
| Refund window | 30-day money-back guarantee | Not stated on homepage |
Comparison data accurate as of September 2026. WPVibe pricing verified at wpvibe.ai/mcp.wpvibe.ai. Feature scope and pricing tiers change, so check vendor sites for current details. Cells marked with × mean the feature is not available at this tier; “Not mentioned” means the feature is not documented on the vendor’s public marketing site at time of research. Spot an error? Reach out and we’ll correct it.
Deep work on a WordPress portfolio?
Direct-connect architecture, no daily cap, 80+ dedicated Pro tools, and 72-168 hour undo on every write. Try Royal MCP Free from WordPress.org, or start with Personal Founder at $79/yr.