# How Royal MCP works

> How Royal MCP connects AI Agents to WordPress. Three-layer architecture, request lifecycle, direct data path, auto-registered tools. Setup in 5 minutes or less.

- Canonical: <https://royalplugins.com/royal-mcp/how-it-works/>
- Last updated: 2026-10-21
- HTML version: <https://royalplugins.com/royal-mcp/how-it-works/>

---

- [Overview](https://royalplugins.com/royal-mcp/)
- [Features](https://royalplugins.com/royal-mcp/features/connect/)

  [Ways to connect](https://royalplugins.com/royal-mcp/features/connect/)
  [Works with other MCP plugins NEW](https://royalplugins.com/royal-mcp/features/works-with-other-mcp-plugins/)
  [Agent Ready NEW](https://royalplugins.com/royal-mcp/features/agent-ready/)
  [Safety and Recovery NEW](https://royalplugins.com/support/royal-mcp/safety-and-recovery/)
- [Getting Started](https://royalplugins.com/royal-mcp/how-it-works/)

  [How It Works](https://royalplugins.com/royal-mcp/how-it-works/)
  [WordPress MCP Guide NEW](https://royalplugins.com/royal-mcp/wordpress-mcp/)
  [Connect Claude](https://royalplugins.com/royal-mcp/connect-claude/)
  [Connect ChatGPT](https://royalplugins.com/royal-mcp/connect-chatgpt/)
  [Editing Elementor with Claude](https://royalplugins.com/blog/editing-elementor-with-claude-four-workflows/)
- [Troubleshooting](https://royalplugins.com/support/royal-mcp/troubleshooting-start-here/)

  [Start Here — Quick Checklist](https://royalplugins.com/support/royal-mcp/troubleshooting-start-here/)
  [Diagnose with curl](https://royalplugins.com/support/royal-mcp/diagnose-mcp-with-curl/)
  [Common Patterns](https://royalplugins.com/support/royal-mcp/#troubleshooting)
- [Developers](https://royalplugins.com/support/royal-mcp/add-your-plugin-tools/)

  [Add your plugin’s tools](https://royalplugins.com/support/royal-mcp/add-your-plugin-tools/)
  [Shape replies with filters](https://royalplugins.com/support/royal-mcp/exposing-customer-email-via-filter/)
  [WP-CLI commands](https://royalplugins.com/support/royal-mcp/wp-cli-commands/)
  [Changelog](https://royalplugins.com/royal-mcp/changelog/)
  [GitHub repository](https://github.com/royalplugins/royal-mcp)
- [Support](https://wordpress.org/support/plugin/royal-mcp/)
- [All Docs](https://royalplugins.com/support/royal-mcp/)

Overview
Features — Ways to connect
— Works with other MCP plugins (NEW)
— Agent Ready (NEW)
— Safety and Recovery (NEW)
Getting Started — How It Works
— WordPress MCP Guide (NEW)
— Connect Claude
— Connect ChatGPT
— Editing Elementor with Claude
Troubleshooting — Start Here
— Diagnose with curl
— Common Patterns
Developers — Add your plugin’s tools
— Shape replies with filters
— WP-CLI commands
— Changelog
— GitHub repository
Support (wp.org Forum)
All Docs

Royal MCP · How It Works

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.

Three-layer architecture

Direct data path

5-minute setup

By Jameson · Founder & Lead Developer · Updated September 2026

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.

Setup

## Set up Royal MCP in 3 steps

5 minutes or less.

No developer required. Install from WordPress.org, copy your MCP URL, add as a connector in Claude or ChatGPT. Done.

[Connect Claude walkthrough](https://royalplugins.com/royal-mcp/connect-claude/)
[Connect ChatGPT walkthrough](https://royalplugins.com/royal-mcp/connect-chatgpt/)

Architecture

## Three layers, one protocol

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.

### WordPress

Your site · content · store data

Actions

Results

R

### Royal MCP

The translator layer

Tool calls

Responses

### AI Agent

Claude · ChatGPT · Cursor

**What each layer owns.** WordPress owns your data and business logic. Royal MCP owns authentication, capability checks, rate limiting, tool dispatch, and translating between the MCP protocol and WordPress function calls. Your AI Agent owns the reasoning: which tool to call and how to interpret the response.

Request Lifecycle

## What happens when you ask AI to do something

One prompt, five steps under the hood. Everything happens in milliseconds. You only see the final answer.

1

“Bump all t-shirt prices 10%”

#### You prompt Claude

Type the request in plain English. Claude parses your intent.

2

{ tool:

"wc\_bulk\_price\_update",

args: {…}

}

#### Claude picks a tool

Chooses the right MCP tool from 250+, packages the arguments as JSON-RPC.

3

#### Royal MCP validates

OAuth check, WordPress capability check, rate-limit check. All in your PHP layer.

4

#### WordPress executes

The tool runs against your database using WordPress's native APIs, generating an undo token.

5

**Updated 47 products.**
Undo available 72h.

#### Result back to Claude

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.

Data Path

## Where your data lives

Royal MCP is direct-connect. Your WordPress site and your AI Agent talk to each other. Nothing sits in the middle.

### Direct (Royal MCP)

Your WordPress

Your AI client

- ✓ One hop, one vendor in the path (you)
- ✓ Your OAuth credentials never leave your site
- ✓ No third-party data-processor to add to your DPA
- ✓ Works with any WordPress host, no cloud tunnels needed

### Relay-based (typical alternatives)

Your WordPress

Vendor relay

Your AI client

- × Two hops, two vendors in the path
- × Credentials + payloads pass through the relay
- × Relay operator becomes a data processor on your DPA
- × Local / firewalled sites often need tunnel workarounds

### Local dev server (developer-focused)

Your machine

Tunnel

Your WordPress

AI client

- × Requires Node.js, npm, or Docker on your machine
- × Local-only unless you run cloudflared or ngrok tunnel
- × Manual updates (GitHub clone, not wp.org auto-update)
- × API-key auth typical, no in-browser OAuth flow

Compatibility

## One endpoint, not one-per-plugin

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.

### One Royal MCP endpoint

WooCommerce
Elementor
Divi
Yoast
ACF
WPForms
+ 8 more

↓

/wp-json/royal-mcp/v1/mcp

↓

Your AI Agent

- ✓ One OAuth flow to authorize
- ✓ One WAF allowlist rule to whitelist
- ✓ One CDN cache-bypass entry
- ✓ One setup that grows with your plugin stack

### Plugin-native MCPs (one per plugin)

WooCommerce
Elementor
Divi
Yoast
ACF
WPForms

↓

/wc-mcp/v1

/elementor-mcp/v1

/divi-mcp/v1

/yoast-mcp/v1

/acf-mcp/v1

/wpf-mcp/v1

↓

Your AI Agent (6× setup)

- × Separate OAuth flow per endpoint
- × Separate WAF allowlist rule per endpoint URL
- × Separate CDN cache-bypass entry per endpoint
- × Setup cost grows linearly with plugin count

**Royal MCP won't block plugin-native MCPs when they ship.** Elementor is building an internal MCP module behind their experimental `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.

Tools Auto-Register

## Your tool count grows with your stack

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.

250+

total MCP tools available today, expanding with every host plugin you activate

WordPress core

+85

WooCommerce

+32

Elementor

+11

Divi 4 & 5

+9

ACF

+19

Yoast SEO

+6

WPForms

+4

UpdraftPlus

+4

And more

+30

Under The Hood

## The technical stack

Standard protocols. Standard WordPress APIs. Every layer inspectable and open source.

AI Client Layer

Claude Desktop · ChatGPT · Cursor · any MCP-capable client

layer 1

↓

MCP Protocol

JSON-RPC over HTTPS · OAuth 2.1 with DCR + PKCE

layer 2

↓

R

Royal MCP

Auth · capability checks · rate limits · audit log · 72h undo tokens

layer 3

↓

WordPress Core

WordPress 6.9 Abilities API · REST API · hook system · roles & caps

layer 4

↓

Your Database

posts · users · options · WooCommerce · page-builder tables

layer 5

## Ready to connect it?

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.

[Connect Claude](https://royalplugins.com/royal-mcp/connect-claude/)
[Connect ChatGPT](https://royalplugins.com/royal-mcp/connect-chatgpt/)

Related

## Keep learning

[### Royal MCP overview

The full Royal MCP product page: features, integrations, 250+ MCP tools breakdown, and pricing.

Open page](https://royalplugins.com/royal-mcp/)
[### Agent Readiness

How Royal MCP publishes the discovery documents Cloudflare, Vercel, and Chrome Lighthouse use to detect MCP-enabled sites.

Learn more](https://royalplugins.com/royal-mcp/features/agent-ready/)
[### Support hub

Every Royal MCP support article: connection troubleshooting, hosting-specific fixes, OAuth deep-dives, WAF gotchas.

Browse docs](https://royalplugins.com/support/royal-mcp/)