Three layers, one protocol, direct data path. Your WordPress site talks to your AI Agent through Royal MCP without any cloud middleman, granting full tool access once connection is established. The tools you have installed decide what your AI can actually do.
Royal MCP is a translator between two worlds. WordPress speaks in posts, pages, users, options, orders, coupons. AI Agents like Claude and ChatGPT speak in prompts and tool calls. Royal MCP sits on your WordPress site, receives tool calls from the AI over the Model Context Protocol, validates the request against your OAuth-issued credentials, dispatches to WordPress core or your active plugins (WooCommerce, Elementor, Divi, and others), and returns the result. The AI Agent talks directly to your site. Nothing routes through Royal Plugins servers.
5 minutes or less.
No developer required. Install from WordPress.org, copy your MCP URL, add as a connector in Claude or ChatGPT. Done.
Your AI Agent talks to Royal MCP over the Model Context Protocol. Royal MCP talks to WordPress over standard PHP function calls. Data flows in both directions.
Your site · content · store data
The translator layer
Claude · ChatGPT · Cursor
One prompt, five steps under the hood. Everything happens in milliseconds. You only see the final answer.
Type the request in plain English. Claude parses your intent.
Chooses the right MCP tool from 200+, packages the arguments as JSON-RPC.
OAuth check, WordPress capability check, rate-limit check. All in your PHP layer.
The tool runs against your database using WordPress's native APIs, generating an undo token.
Response envelope with count, undo token, and a plain-English summary Claude reads to you.
Every write emits a 72-hour undo token. If Claude misinterpreted your prompt, one call to mcp_undo_last_operation reverses it.
Royal MCP is direct-connect. Your WordPress site and your AI Agent talk to each other. Nothing sits in the middle.
Some WordPress plugins are starting to ship their own MCP modules. Royal MCP doesn't fight them. It consolidates the ones you'd otherwise be setting up one at a time.
e_wp_abilities_api flag. When it graduates, it lives at a different endpoint than Royal MCP. Both can run side by side. Your AI Agent sees tools from whichever endpoints you connect. Royal MCP just consolidates the ones that matter today into one setup, one auth flow, one WAF rule.
Install a plugin Royal MCP supports and its tools appear automatically. Deactivate it and they disappear. No per-plugin MCP endpoints to install, no separate OAuth flows to manage.
total MCP tools available today, expanding with every host plugin you activate
Standard protocols. Standard WordPress APIs. Every layer inspectable and open source.
Install Royal MCP for free from WordPress.org, copy your MCP URL, and add it as a connector in your AI client. Full walkthroughs below.