Self-hosted WordPress MCP server plugin
Royal MCP vs WPVibe
How WPVibe compares with Royal MCP for people who want AI access to a self-hosted WordPress site without running their own MCP server.
TL;DR
Royal MCP is a capable self-hosted MCP server plugin with a strong security story — API-key auth, rate limiting, audit logging, and 120+ tools across core and popular plugins. WPVibe is the hosted alternative: connect your AI client to one remote MCP URL and authorize sites, with no server plugin to install, secure, or keep updated, plus WP-CLI-style commands and draft-first theme and file workflows. And because WPVibe connects over OAuth, you use the Claude or ChatGPT subscription you already pay for — no provider API keys to manage.
At a glance
How the two options compare
Primary job
WPVibe
A hosted remote MCP server you connect your AI client to.
Royal MCP
A plugin that turns each WordPress install into its own self-hosted MCP server.
Hosting model
WPVibe
Hosted by WPVibe; nothing to install, secure, or update on the server.
Royal MCP
Self-hosted; you install the plugin and run the MCP endpoint on your own WordPress.
Setup
WPVibe
Add the remote MCP URL, sign in, and authorize each site.
Royal MCP
Install the plugin, generate an API key, and point your client at your site's endpoint.
Security model
WPVibe
WordPress-native per-site authorization; the connection is managed in your account.
Royal MCP
API-key auth, 60 requests/min rate limiting, audit logging, and sensitive-data redaction, all on your server.
Tool surface
WPVibe
REST operations, media, plugin abilities, WP-CLI-style commands, rendered HTML inspection, and draft-first theme/file work.
Royal MCP
67 core tools plus around 59 more for WooCommerce, ACF, Elementor, and Royal's own plugins when installed.
AI clients
WPVibe
Claude, ChatGPT, Cursor, Claude Code, and other remote-MCP clients, sharing one connection.
Royal MCP
Wide client support (Claude, ChatGPT, Gemini, local models), each pointed at your self-hosted endpoint.
AI access
WPVibe
Connect over OAuth and use the AI subscription you already pay for — Claude, ChatGPT, Claude Code, or Claw.ai. No provider API keys to generate and no separate per-token API bill.
Royal MCP
Connect from an MCP client; whether you use an existing subscription or a provider API key depends on the client and model you choose.
Best when
WPVibe
You want WordPress AI workflows without running MCP infrastructure.
Royal MCP
You want full control of a self-hosted MCP server and are comfortable operating it.
| Dimension | WPVibe | Royal MCP |
|---|---|---|
| Primary job | A hosted remote MCP server you connect your AI client to. | A plugin that turns each WordPress install into its own self-hosted MCP server. |
| Hosting model | Hosted by WPVibe; nothing to install, secure, or update on the server. | Self-hosted; you install the plugin and run the MCP endpoint on your own WordPress. |
| Setup | Add the remote MCP URL, sign in, and authorize each site. | Install the plugin, generate an API key, and point your client at your site's endpoint. |
| Security model | WordPress-native per-site authorization; the connection is managed in your account. | API-key auth, 60 requests/min rate limiting, audit logging, and sensitive-data redaction, all on your server. |
| Tool surface | REST operations, media, plugin abilities, WP-CLI-style commands, rendered HTML inspection, and draft-first theme/file work. | 67 core tools plus around 59 more for WooCommerce, ACF, Elementor, and Royal's own plugins when installed. |
| AI clients | Claude, ChatGPT, Cursor, Claude Code, and other remote-MCP clients, sharing one connection. | Wide client support (Claude, ChatGPT, Gemini, local models), each pointed at your self-hosted endpoint. |
| AI access | Connect over OAuth and use the AI subscription you already pay for — Claude, ChatGPT, Claude Code, or Claw.ai. No provider API keys to generate and no separate per-token API bill. | Connect from an MCP client; whether you use an existing subscription or a provider API key depends on the client and model you choose. |
| Best when | You want WordPress AI workflows without running MCP infrastructure. | You want full control of a self-hosted MCP server and are comfortable operating it. |
Why people look for alternatives
Royal MCP is a well-built self-hosted MCP server plugin with a security-first pitch: API-key auth on every session, rate limiting, audit logging, sensitive-data redaction, and a large tool surface — 67 core tools plus around 59 more for WooCommerce, ACF, Elementor, and Royal’s own plugins. If you want a self-hosted MCP endpoint you fully control, it is a solid option.
The reason people compare is the operating model. A self-hosted server means you install the plugin, generate keys, and keep the endpoint patched and secured on every site. The recurring question in WordPress MCP threads is whether running your own server per site is worth it, or whether a managed connection would be simpler.
What WPVibe does instead
WPVibe is the hosted alternative. Instead of turning each install into its own MCP server, you connect your AI client to one remote MCP URL and authorize sites with a WordPress-native flow. There is no server plugin to install, secure, or update — and WPVibe connects through WordPress core REST and Application Passwords, so the optional WPVibe plugin is a progressive enhancement, not a requirement to connect.
On top of the connection model, WPVibe adds WP-CLI-style operations, rendered HTML inspection, and draft-first theme and file workflows, and the same connection works across Claude, ChatGPT, Cursor, and Claude Code. The trade is straightforward: Royal MCP gives you a server you own and operate; WPVibe gives you a workflow you connect to.
Honest fit
Choose based on the workflow
WPVibe is best for
- Teams that would rather connect to a hosted MCP server than install and maintain one on every site.
- People using several AI clients who want one WordPress connection to work across all of them.
- Builders who want WP-CLI-style operations and draft-first theme and file workflows, not only REST and tool calls.
- Owners who want guided skills and preview-before-publish safety on live sites.
Royal MCP is best for
- Developers who want a self-hosted MCP server they fully control on their own infrastructure.
- Sites that need on-box security controls like API-key auth, rate limiting, and audit logs.
- Users already in the Royal Plugins ecosystem (GuardPress, SiteVault, ForgeCache, Royal Links).
- Teams comfortable installing, securing, and updating an MCP plugin per site.
Setup or switching notes
If a self-hosted endpoint is a hard requirement — for compliance, network isolation, or because you want every byte to stay on your box — Royal MCP is built for that, and you can keep it. WPVibe is the better fit when the friction you want to remove is operational: no MCP server to stand up, secure, and patch on each site.
You can also run both: Royal MCP for a self-hosted endpoint on sites that need one, and WPVibe as the hosted connection your AI clients share day to day. Most teams settle on a single connection model once they see which trade-off they prefer.
FAQ
Common questions
Does WPVibe require installing a plugin like Royal MCP?
No. WPVibe is a hosted remote MCP server and connects through WordPress core REST and Application Passwords. The optional WPVibe plugin only adds progressive enhancements — it is not required to connect a site.
Is a hosted MCP server less secure than a self-hosted one?
It is a different trade-off. Royal MCP keeps the server on your box with its own auth and logging; WPVibe manages the connection layer with per-site WordPress authorization, so there is no MCP endpoint for you to harden and patch yourself.
Can Royal MCP and WPVibe coexist?
Yes. You can run a self-hosted Royal MCP endpoint and WPVibe's hosted workflow on the same site, though most teams pick one connection model in practice.
Do I need a provider API key to use WPVibe?
No. WPVibe connects over OAuth using the Claude or ChatGPT subscription you already pay for, so there are no provider API keys to generate and no separate per-token API bill to manage.
Disclaimer
This comparison is based on public product information and community discussions reviewed in June 2026. WPVibe is not affiliated with, endorsed by, or sponsored by Royal MCP or Royal Plugins.