Royal MCP – Secure AI Connector for Claude, ChatGPT & Gemini

Royal MCP – Secure AI Connector for Claude, ChatGPT & Gemini

توسط

Royal MCP is a security-first Model Context Protocol (MCP) server for WordPress. It gives AI platforms like Claude, ChatGPT, and Google Gemini structured access to your WordPress content — with authentication, rate limiting, and audit logging that most MCP implementations skip entirely.

According to recent security research, 41% of public MCP servers have no authentication and respond to tool calls without any credentials. Royal MCP takes the opposite approach: every MCP session requires an API key, every request is rate-limited, and every interaction is logged.

Why Security Matters for MCP

MCP gives AI agents the ability to read, create, update, and delete your WordPress content. Without proper authentication, anyone who discovers your MCP endpoint can:

  • Read all your posts, pages, and media
  • Create or delete content
  • Access user data and plugin information
  • Overwhelm your server with rapid-fire requests

Royal MCP prevents all of this with API key authentication on session initialization, timing-safe key comparison, per-IP rate limiting (60 requests/minute), and a full activity log of every MCP interaction.

67 Core Tools + 32 Integration Tools

WordPress Core (67 tools):

  • Posts — create, read, update, delete, search, count (any registered public post type, featured images supported)
  • Pages — full CRUD with parent page support
  • Post Types — discover all registered public post types on the site
  • Post Revisions — list revision history and roll a post back to any prior version
  • Media — browse, upload from URL or base64, update alt text/caption/title/description, set as featured image, delete
  • Comments — create, read, delete; full moderation suite (list pending, approve, mark spam, trash)
  • Users — display names and roles (emails and usernames are not exposed)
  • Categories & Tags & Custom Taxonomies — create, update (rename/re-slug/edit/move), delete, assign, count, discover all registered taxonomies
  • Term Meta — read, update, delete (most useful for Yoast / Rank Math / AIOSEO term-level SEO meta)
  • Menus — list menus, list menu items, create / update / delete / reorder menu items
  • Post Meta — read, update, delete custom fields (works with ACF, MetaBox, JetEngine, Pods, CPT UI)
  • SEO Meta — read and write Yoast SEO or Rank Math title/description/focus keyword/robots/OG fields (auto-detects active SEO plugin)
  • Site Info — site name, description, WordPress version, timezone
  • Plugins & Themes — list installed plugins and themes with active status
  • Theme Appearance — get active theme, read/write theme mods (gated by admin toggle + allowlist), read/write Custom CSS
  • Search — full-text content search across post types
  • Permalink Structure — read and update permalink settings (gated by admin toggle)
  • Options — read allowlisted core options, read full plugin settings by slug (sensitive keys redacted), and write to allowlisted options when an admin enables it

Plugin Integrations (Conditional)

Royal MCP automatically detects compatible plugins and adds specialized MCP tools. No configuration needed — if the plugin is active, the tools appear.

WooCommerce Integration (9 tools):
When WooCommerce is active, AI agents can manage your store:

  • Browse and search products by category, status, or type
  • Create and update products with prices, SKUs, stock levels
  • View orders, order details, and update order status
  • List customers with order count and total spent
  • Get store statistics — revenue, order count, average order value by period

GuardPress Integration (7 tools):
When GuardPress is active, AI agents can monitor your site security:

  • Get current security score and grade with factor breakdown
  • View security statistics — failed logins, blocked IPs, alerts
  • Run vulnerability scans and review results
  • List blocked IP addresses and failed login attempts
  • Browse the security audit log filtered by severity

SiteVault Integration (6 tools):
When SiteVault is active, AI agents can manage your backups:

  • List available backups filtered by status or type
  • Trigger new backups (full, database, files, plugins, themes)
  • Check backup progress in real time
  • View backup statistics — total size, last backup, counts
  • List and review backup schedules

ForgeCache Integration (3 tools):
When ForgeCache is active, AI agents can manage your page cache:

  • Clear the entire cache, or purge a specific URL
  • View cache statistics — hit rate, file count, total size

Royal Ledger Integration (4 tools):
When Royal Ledger is active, AI agents can review your software costs and license data:

  • List recurring software costs and renewal dates
  • Get cost summaries grouped by month, vendor, or category
  • List stored license keys (key VALUES are never exposed — only masked previews; decryption requires logging into wp-admin)

Royal Links Integration (3 tools):
When Royal Links is active, AI agents can manage your branded short links:

  • List existing links with click counts and target URLs
  • Create new branded short links
  • Get click statistics for any link

Royal MCP and the WordPress Core Abilities API

WordPress 6.9 shipped the Abilities API in November 2025 — a primitive that lets plugins register typed capabilities AI agents can call. Core ships three default abilities (site info, user info, environment info) and the wordpress/mcp-adapter package bridges abilities to the MCP protocol.

Royal MCP is a complete, production-ready MCP server that predates the official adapter. It runs the full Streamable HTTP transport, enforces API key authentication on every request, ships OAuth 2.0 for Claude Desktop’s native connector flow, rate-limits per-IP, redacts sensitive data, and logs every interaction. Out of the box it includes 67 tools for WordPress core operations plus 32 integration tools that auto-load when WooCommerce, GuardPress, SiteVault, ForgeCache, Royal Ledger, or Royal Links is active.

Supported AI Platforms

  • Claude (Anthropic) — Full MCP support via Claude Desktop, Claude Code, and VS Code
  • OpenAI / ChatGPT — GPT-4o, GPT-4 Turbo, GPT-3.5 Turbo
  • Google Gemini — Gemini 1.5 Pro, 1.5 Flash
  • Groq — Llama 3.3, Mixtral, Gemma 2
  • Azure OpenAI — Azure-hosted OpenAI deployments
  • AWS Bedrock — Claude, Llama, Titan models
  • Ollama / LM Studio — Local self-hosted models (no external data transmission)
  • Custom MCP Servers — Connect to any MCP-compatible endpoint

Compatible Clients & Frameworks

Royal MCP works with any MCP-compliant client, IDE, or AI agent framework — no per-tool configuration required:

  • Desktop AI apps — Claude Desktop (native MCP connector via OAuth 2.0), ChatGPT Desktop, Gemini Advanced.
  • AI code IDEs — Claude Code, VS Code (with MCP extension), Cursor, Windsurf, Continue, Cline, Zed, JetBrains AI Assistant.
  • API testing tools — Postman, Bruno, Insomnia (use the API key in the X-Royal-MCP-API-Key header).
  • Custom field plugins — Advanced Custom Fields (ACF), MetaBox, JetEngine, Pods, CPT UI, Custom Field Suite. The wp_get_post_meta / wp_update_post_meta tools read and write any custom field, so AI agents can populate ACF fields just like a human editor.
  • Page builders — Elementor, Divi, Beaver Builder, Bricks, Gutenberg, Spectra, Stackable. Post content stored by builders is fully readable and writable by AI.
  • Multilingual — WPML, Polylang, TranslatePress, qTranslate. Translated posts appear as separate posts and can be read or written via the standard post tools.
  • AI agent frameworks — LangChain, AutoGen, CrewAI, LlamaIndex, Haystack — any MCP-compatible framework can call Royal MCP’s tools.
  • AI app platforms — Anthropic Console, OpenAI Playground, Google AI Studio, Vertex AI, Azure AI Studio, Amazon Bedrock Console.

MCP Spec Compliance

Royal MCP implements the MCP 2025-11-25 Streamable HTTP transport specification:

  • Single /mcp endpoint for all JSON-RPC communication
  • POST for client messages, GET for server-sent events, DELETE for session termination
  • Cryptographically secure session IDs with transient-based storage
  • Origin header validation to prevent DNS rebinding attacks
  • Proper CORS handling for browser-based MCP clients

External Services

This plugin connects to third-party AI services to enable AI platforms to interact with your WordPress content. No data is transmitted until you explicitly configure and enable a platform connection.

What data is sent: Your WordPress content (posts, pages, media metadata) as requested by the connected AI platform through authenticated MCP tool calls.

When data is sent: Only when you have configured a platform with API credentials AND enabled that platform connection AND the AI platform makes an authenticated request.

Supported services and their policies:

  1. Upload the royal-mcp folder to /wp-content/plugins/
  2. Activate the plugin through the ‘Plugins’ menu in WordPress
  3. Go to Royal MCP Settings to configure
  4. Copy your API key — you will need this to authenticate MCP connections
  5. Add your AI platform(s) and enter their API keys
  6. In your AI client (Claude Desktop, VS Code, etc.), configure the MCP server URL and API key

Full setup guides for each platform are available at royalplugins.com/support/royal-mcp/.

سوالات متداول

What is MCP and why does my WordPress site need it?

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.

How is Royal MCP different from other WordPress MCP plugins?

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.

Does Royal MCP duplicate what WordPress core now does?

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 that 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, 67 ready-to-use WordPress core tools, and 32 integration tools that auto-load for WooCommerce, GuardPress, SiteVault, ForgeCache, Royal Ledger, and Royal Links.

Does Royal MCP work with WooCommerce?

Yes. When WooCommerce is active, Royal MCP automatically adds 9 additional MCP tools for product management (create, update, search), order management (view, update status), customer data, and store statistics. No additional configuration is needed — the tools appear automatically in the MCP tools list.

Can AI assistants configure my plugins for me?

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:

    1. The site admin must enable the “Allow AI to write WordPress options” toggle on the Royal MCP settings page (off by default)
    2. The option name must be in a runtime allowlist. The default allowlist is intentionally tiny — blogname, blogdescription, posts_per_page, date_format, time_format. Plugin authors opt their own settings in via the royal_mcp_writable_options filter.
    3. 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']));

How do I connect Claude Desktop to WordPress?

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/.

Is my content safe?

Royal MCP is designed with defense in depth. API key authentication is required for all MCP sessions. Rate limiting prevents abuse (60 requests per minute per IP). Activity logging records every tool call. Sensitive data is filtered — user emails, usernames, admin email, PHP version, and stored credentials inside plugin settings (api keys, secrets, tokens, passwords) are never exposed through MCP. Comment creation respects your WordPress moderation settings. Post meta values are sanitized before storage. Option writes are disabled by default and gated by three independent checks (admin toggle, allowlist, hard denylist) when enabled. The plugin itself starts disabled by default — nothing is accessible until you explicitly enable it.

Can I use local AI models instead of cloud services?

Yes. Royal MCP supports Ollama and LM Studio for fully local AI inference. When using local models, no data leaves your server — the AI model runs on your own hardware and communicates with WordPress through the MCP protocol on localhost.

What happens if I uninstall Royal MCP?

Royal MCP performs a clean uninstall. All plugin options, database tables (activity logs), transients, and user meta are removed. No orphaned data is left behind.

Does Royal MCP work with Claude Code, VS Code, Cursor, Windsurf, or other AI IDEs?

Yes. Any MCP-compliant client can connect to Royal MCP. Configure your IDE or client with the MCP server URL (https://yoursite.com/wp-json/royal-mcp/v1/mcp) and the API key (sent in the X-Royal-MCP-API-Key header). Claude Desktop additionally supports the native “Add Connector” OAuth 2.0 flow, which Royal MCP handles via Dynamic Client Registration (RFC 7591) — no manual API key management required on that path. The same OAuth flow works in any client that follows the MCP 2025-11-25 spec.

Does Royal MCP work with custom fields, ACF, MetaBox, JetEngine, Pods, or CPT UI?

Yes. Royal MCP exposes WordPress’s standard wp_get_post_meta, wp_update_post_meta, and wp_delete_post_meta tools, which read and write any custom field — including Advanced Custom Fields (ACF), MetaBox, JetEngine, Pods, CPT UI, and Custom Field Suite. AI agents can populate ACF fields, set repeater rows, update flexible content blocks, and read computed fields just like a human editor working in the WordPress admin.

Will Royal MCP slow down my WordPress site?

No. The MCP endpoint is a REST route that runs only when an authenticated AI client makes a request — it does not run on visitor-facing pages, frontend templates, or admin screens (except its own settings page). The activity log uses a single indexed database table and writes asynchronously after the response is sent. Rate limiting (60 requests/minute per IP) prevents accidental overload.

Does Royal MCP work on WordPress multisite networks?

Yes, on a per-site basis. Each site in a multisite network has its own API key, its own activity log, and its own settings. AI clients connect to a specific site’s MCP endpoint — Royal MCP does not bridge requests between sites in the network.

Can I limit which posts, pages, or post types AI can access?

Yes. The wp_get_posts and wp_create_post tools accept a post_type parameter and validate it against registered public post types, so private or internal post types are not exposed. Plugin authors can disable specific tools entirely with the royal_mcp_disabled_tools filter, or scope the option-write allowlist with royal_mcp_writable_options. WordPress’s standard capability checks also apply to every tool call.

Does Royal MCP work with WPML, Polylang, or TranslatePress for multilingual content?

Yes. Translated posts appear as separate WordPress posts (each with its own ID and language meta) and are readable or writable via the standard wp_get_posts, wp_create_post, and wp_update_post tools. AI agents can list posts in a specific language by filtering on the language meta key, or translate a post and write the corresponding translation by ID.

How do I monitor what AI is doing on my site?

Every authenticated MCP request is logged to the Royal MCP activity log with timestamp, client IP, tool name, parameters (sensitive values redacted), and response status. The log is filterable by time range, client, tool, or status code, and exportable to CSV. The log page refreshes via AJAX so you can watch active sessions in real time.

×
نظری برای این آیتم موجود نیست.
0 0 رای ها
امتیازدهی
اشتراک در
اطلاع از
0 نظرات
قدیمی‌ترین
تازه‌ترین بیشترین رأی
نسخه حجم فایل SHA256 تغییرات دانلود
1.4.12 98 کیلوبایت -
دانلود
×
★★★★★
★★★★★
5.0 /5 (3 نظر)

قیمت:

رایگان

نگارش

1.4.12

آخرین انتشار

14 اردیبهشت 1405

آخرین بروزرسانی

3 ماه پیش

نصب های فعال

1,000+

نگارش وردپرس

وردپرس 5.8+

تست شده از نسخه

وردپرس 7.0

نگارش PHP

PHP 7.4+

نسخه ها

1 نسخه