by Royal Plugins 5 (7 reviews)

Royal MCP – Secure AI Connector for Claude, ChatGPT & any LLM via MCP

Name: Royal MCP – Secure AI Connector for Claude, ChatGPT & any LLM via MCP
Rating: 5.0 (7 reviews)
Author: Royal Plugins

200+ MCP tools. OAuth 2.0 + WebMCP. Connect Claude, ChatGPT, Perplexity, Gemini or any MCP agent to your WordPress site. 100% self-hosted.

Royal MCP ranks #1,717 among WordPress.org plugins with 10,000+ active installations, a 5/5 rating from 7 reviews, and was last updated Sep 29, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Compatible with WP 7.1.2

v1.5.6 Current Version v1.5.6

Updated 6 days ago Last Update on 29 Sep, 2026

Refreshed 9 hours ago Last Refreshed on

Top 5% by installs Downloads -45.3% this week Actively maintained

View on WordPress.org

Rank

#1,717

— No change

Active Installs

10K+

+111011.1%

KW Avg Position

— No change

Downloads

142.6K

+527 today

Support Resolved

69%

— No change

Rating

100%

Review 5 out of 5

5 (7 reviews)

Next Milestone 20K

Total Progress 62.5%

10K+ 20K+

303

Ranks to Climb

Growth Needed

8,000,000

Active Installs

Pro

Unlock Exact Install Count

See the precise estimated active installs for this plugin, calculated from real-time ranking data.

Exact install estimates within tiers
Track install growth over time
Milestone progress predictions

Upgrade to Pro

Need 3,750 more installs to reach 20K+

Rank Changes

Current #1,717

Change

Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Upgrade to Pro

Active Installs 0,000,000+

Growth +0.0%

Peak 0,000,000

Downloads Growth

Downloads

Growth

Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

5.0

7 reviews

Overall 100%

7 (100%)

0 (0%)

Support Threads Overview

Resolved

Unresolved

Total Threads

Resolved

Unresolved

69%

Resolution Rate

Security History

Source: WPVulnerability

3 known vulnerabilities on record · 3 in the last 24 months · checked 1 week ago

Jul 1, 2026

Royal MCP – Secure AI Connector for Claude, ChatGPT & any LLM via MCP [royal-mcp] < 1.4.26

CVE-2026-10750 · Fixed in v1.4.26
Jun 18, 2026

Royal MCP – Secure AI Connector for Claude, ChatGPT & any LLM via MCP [royal-mcp] < 1.4.26

CVE-2026-54842 · Fixed in v1.4.26
Apr 21, 2026

Royal MCP – Secure AI Connector for Claude, ChatGPT & any LLM via MCP [royal-mcp] < 1.4.3

CVE-2026-40775 · Fixed in v1.4.3

Track This Plugin

Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.

Start Tracking Free

Plugin Details

Version: 1.5.6
Last Updated: Sep 29, 2026
Requires WP: 5.8+
Tested Up To: 7.1.2
PHP Version: 7.4 or higher
Author: Royal Plugins

Support & Rating

Rating: ★ ★ ★ ★ ★ 5
Reviews: 7
Support Threads: 16
Resolved: 69%

Keywords

AI ChatGPT Claude elementor mcp

Upgrade to Pro

Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.

Upgrade Now

Similar Plugins

Adminify – White Label, Admin Menu Editor, Login Customizer

6K+ installs

#2,742

Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits

30K+ installs

#1,015

TL;DR

AI summary of the plugin's readme

This plugin is for WordPress site owners who want AI platforms like Claude, ChatGPT, and Gemini to access their site content. It solves the problem of securely connecting WordPress content to multiple AI platforms via the Model Context Protocol with authenticated REST API access.

Multi-platform AI support
REST API access to posts, pages, media, users
API key authentication
Activity logging of AI interactions
Claude Desktop integration
Supports Mistral, Perplexity, Groq
Supports Cohere, Together AI, DeepSeek
Supports Ollama/LM Studio and custom MCP servers

Frequently Asked Questions

Common questions about Royal MCP – Secure AI Connector for Claude, ChatGPT & any LLM via MCP

Model Context Protocol (MCP) is an open standard created by Anthropic that lets AI assistants interact with external data sources. Without MCP, AI tools like Claude or ChatGPT can only work with content you copy and paste into them. With Royal MCP installed, these AI platforms can directly read your WordPress posts, create new content, manage your WooCommerce products, check your security status, and trigger backups — all through a structured, authenticated protocol.

Security. Most MCP plugins (and 41% of all public MCP servers) have no authentication at all. Royal MCP requires an API key for every session, rate-limits requests to prevent abuse, logs every interaction for audit purposes, and filters sensitive data (emails, PHP version, admin credentials) from responses. We built this plugin with the same security standards we apply to GuardPress, our WordPress security plugin used on thousands of sites.

No. WordPress 6.9 added the Abilities API (a primitive for registering AI-callable functions), and the wordpress/mcp-adapter package bridges abilities to the MCP protocol. Royal MCP is a full MCP server with the security layer, connector flows, and plugin integrations the bare primitive does not include: enforced API key auth, OAuth 2.0 for Claude Desktop, per-IP rate limiting, audit logging, sensitive-data redaction, 89 ready-to-use WordPress core tools, and 124 integration tools for WooCommerce, GuardPress, Royal AI Firewall, SiteVault, ForgeCache, Royal Ledger, Royal Links, Elementor, Divi, ACF, Yoast SEO, UpdraftPlus, WPForms, Redirection, Solid Security, Contact Form 7, MonsterInsights, W3 Total Cache, Duplicator, and BuddyPress.

Yes. When WooCommerce is active, Royal MCP automatically adds 29 MCP tools spanning product management (simple and variable, including variation CRUD and global attribute management), full coupon management (list/get/create/update/delete + bulk trash purge), order management (view, create, update, add notes, update status), customer data, and store statistics. No additional configuration is needed — the tools appear automatically in the MCP tools list.

Yes, with safety controls. Royal MCP exposes two tools for plugin configuration: wp_get_plugin_settings lets AI read any plugin's stored settings by slug. Sensitive values (API keys, secrets, tokens, passwords, license keys, OAuth credentials) are automatically replaced with [REDACTED] before they leave your server, so AI assistants can understand a plugin's configuration without ever seeing stored credentials. wp_update_option lets AI write to WordPress options, but only after passing three security gates: The site admin must enable the "Allow AI to write WordPress options" toggle on the Royal MCP settings page (off by default) The option name must be in a runtime allowlist. The default allowlist is intentionally tiny — blogname, blogdescription, posts_per_page, date_format, time_format, show_on_front, page_on_front. Plugin authors opt their own settings in via the royal_mcp_writable_options filter. A hard denylist permanently blocks writes to sensitive option names (siteurl, home, license keys, secrets, salts, etc.) regardless of the allowlist or the toggle. Plugin authors can opt in their settings with one line: add_filter('royal_mcp_writable_options', fn($opts) => array_merge($opts, ['my_plugin_settings']));

Install Royal MCP, go to Royal MCP → Settings, and copy your API key and MCP server URL. In Claude Desktop, add a new MCP server configuration with the URL and include the X-Royal-MCP-API-Key header with your API key. Full step-by-step guide at royalplugins.com/support/royal-mcp/. If the connection fails, see the next FAQ.

About 90% of "can't connect" / "OAuth failed" / "tools missing" issues resolve in a basic 4-step pass before any host-specific fix is needed. In order: (1) update Royal MCP to the latest version (every recent release fixes meaningful OAuth edge cases), (2) run a conflict test — deactivate all other plugins, switch to a default theme like Twenty Twenty-Five, and purge every cache layer (any cache plugin, your host's server-level cache, Cloudflare/CDN, and browser cache), (3) wipe stale OAuth state — use the Reset OAuth State button in Royal MCP → Settings if you're on 1.4.17 or newer, or run the four DELETE SQL queries documented in our support article, (4) check Royal MCP → Activity Logs for the most recent oauth: row, which records exactly which validation rule fired. Full walk-through with copy-pasteable commands at royalplugins.com/support/royal-mcp/troubleshooting-start-here.html. Only proceed to host-specific fixes (Cloudflare AI Bots toggle, SiteGround /.well-known/ static files, edge-cache exclusions) after the four basics are ruled out — most "advanced infrastructure" tickets we receive actually resolve in those four steps.

When you restore from backup, the OAuth client credentials Claude was holding no longer match anything on the WordPress side, so Claude's connector ends up with a stale token that no Royal MCP installation will accept. The fix in Royal MCP 1.4.17+ is one click: go to Royal MCP → Settings and click the Reset OAuth State button. This wipes all stale OAuth clients, issued access/refresh tokens, and pending authorization codes. Then in Claude, delete the existing connector entirely, wait 30 seconds, and re-add it from scratch — the full OAuth flow runs fresh against the cleaned-up state and the connection works. On 1.4.16 or older the same effect can be achieved by running four DELETE SQL queries documented at royalplugins.com/support/royal-mcp/troubleshooting-start-here.html. The plugin's settings, API key, and Activity Log are not affected by Reset OAuth State — only the OAuth handshake state.

Both messages (plus "no tools available" in Claude.ai after connecting) usually mean one of Royal MCP's OAuth or sessions database tables is physically missing. The fix is to update Royal MCP to 1.4.29 or newer — the new runtime healer detects missing tables and recreates them automatically on the next pageload, with no deactivate/reactivate required. After updating, delete the existing Royal MCP connector in Claude, wait 30 seconds, then re-add it fresh. If you can't update yet and need to recover immediately, the manual workaround is wp option delete royal_mcp_db_version followed by loading any wp-admin page. Full symptom diagnostic (phpMyAdmin / WP-CLI), the auto-heal explanation, and the manual recovery walkthrough are at royalplugins.com/support/royal-mcp/oauth-tables-missing.html.

By design, Royal MCP's OAuth endpoints (/register, /token, /authorize) are registered as top-level WordPress rewrite rules at the site root, not as REST API routes under /wp-json/royal-mcp/v1/. This is required by the OAuth 2.0 specification (RFC 6749) and the MCP discovery specs (RFC 8414 and RFC 9728), which mandate predictable site-root paths so OAuth-discovery-aware clients can find them without per-plugin configuration. If you're auditing rewrite rules instead of REST routes, you can see ours via wp rewrite list | grep royal_mcp_oauth from WP-CLI. The /wp-json/royal-mcp/v1/ namespace contains the JSON-RPC tool endpoint at /mcp plus supporting REST routes (/posts, /pages, /site, etc.) — but not the OAuth handshake endpoints themselves. Both routing layers are normal and both need to be reachable for the connector to work end-to-end.

Royal MCP – Secure AI Connector for Claude, ChatGPT & any LLM via MCP

Next Milestone 20K

Unlock Exact Install Count

Rank Changes

Upgrade to Pro

Active Installs Growth

Downloads Growth

Upgrade to Pro

Reviews & Ratings

Support Threads Overview

Security History

Track This Plugin

Plugin Details

Support & Rating

Keywords

Upgrade to Pro

Similar Plugins

TL;DR

Frequently Asked Questions

Sign In / Register