Your AI connects to Royal MCP. Every time.

Q: How do I see which MCP plugins are active on my site?

Ask your AI client to run wp_get_mcp_coexistence. It lists the other MCP servers and hubs on the site, which plugin answers each shared sign-in address, whether robots.txt blocks AI bots and which routes reach Royal MCP's tools. Only administrators can run it.

WordPress sites rarely run one AI plugin. SEO plugins, AI writers and other MCP servers now ship their own sign-in, and several of them answer the same site-wide addresses Claude and ChatGPT read. Royal MCP signs AI clients in at its own address, answers its own sign-in documents first, and tells you exactly which plugin is in the way when something still collides.

By Jameson · Founder & Lead Developer · Royal MCP 1.5.12

Get Royal MCP

Who answers your sign-in

/wp-json/royal-mcp/v1Royal MCP
Rank Math built-in sign-innamed, fix shown
AI Engine MCP modulenamed, fix shown
Easy MCP AI sign-innamed, fix shown
Elementor MCP · Angielisted, side by side
Two MCP Adapter copiesadapter server kept off

Why connections collide

One site, several AI plugins, one set of sign-in addresses

An AI client signs in by reading a few standard addresses on your site. When more than one plugin answers them, the client follows whichever answers first.

Claude, ChatGPT and other AI clients find out how to sign in from addresses such as /.well-known/oauth-authorization-server and /.well-known/oauth-protected-resource, then send you to a sign-in page such as /authorize. Every MCP plugin needs those addresses, and so do SEO and AI plugins that now bundle their own AI sign-in. Only one plugin can answer each one.

When the wrong plugin answers, the symptoms look like a broken connection: ChatGPT shows “Unknown OAuth client.”, the sign-in page belongs to a plugin you did not mean to connect, or the client loops back to sign-in. Nothing is wrong with your host or your AI client; two plugins are answering the same door.

Royal MCP does not fight for those shared addresses. It signs AI clients in at its own address, answers its own documents before other plugins get the chance, and leaves every other plugin’s addresses alone, so each plugin keeps working.

Built in to Royal MCP (free)

Four ways Royal MCP keeps your connection its own

All of this ships in the free plugin from Royal MCP 1.5.12 and needs no setup.

01 · OWN ADDRESS

Its own sign-in address

AI clients sign in to Royal MCP at /wp-json/royal-mcp/v1, not at the site-wide addresses other plugins also answer: its sign-in documents, client registration and token exchange live there and point AI clients to Royal MCP’s own sign-in page. Connections made before the update keep working.

02 · ANSWERS FIRST

Answers its own documents first

Royal MCP answers requests for its own sign-in documents before WordPress hands the request to other plugins, so a plugin that claims every sign-in address cannot answer in Royal MCP’s place. It answers only its own exact addresses; everything else still goes to the plugin that owns it.

03 · SELF-CHECK

A sign-in self-check that names the plugin

Royal MCP walks the same path an AI client takes, from the sign-in challenge to the sign-in server, following redirects. If another plugin answers any step, the Royal MCP screens name it, show the address it answers and the fix, with a Re-check button.

04 · REPORT

A report of every MCP server on the site

Ask your AI client to run wp_get_mcp_coexistence. It lists the other MCP servers and hubs on the site, who answers each shared address (the sign-in documents, the MCP server card, llms.txt and robots.txt), whether robots.txt blocks AI bots, and which routes reach Royal MCP’s tools. Administrators only.

What Royal MCP recognises

Known collisions and the fix for each

These are the plugins we see most often next to Royal MCP. The self-check names them on your site; this table tells you what to do.

Plugin or situation	What you see	What to do
Rank Math, and other plugins that bundle the same MCP sign-in library	ChatGPT shows “Unknown OAuth client.”; Claude may still connect, to the other plugin	Royal MCP 1.5.12 or later signs in at its own address, so nothing else is needed. To turn the bundled sign-in off: add `add_filter( 'wpmedia_mcp_oauth_server_enabled', '__return_false' );` to a small must-use plugin, then re-save Settings → Permalinks.
AI Engine with its MCP module on	Can answer the site’s OAuth discovery addresses before other plugins	Royal MCP answers its own documents first. If the site does not need AI Engine’s MCP server, turn the MCP module off in AI Engine’s settings.
Easy MCP AI with OAuth sign-in on	Answers the site-root sign-in documents	Royal MCP signs in at its own address. If you do not use Easy MCP AI’s sign-in, turn OAuth off in its settings.
Elementor MCP and Angie	Elementor’s own MCP server; Angie can refuse tool calls on other MCP Adapter servers until its consent setting allows them	Both run side by side with Royal MCP. When Angie refuses a call, Royal MCP’s message names Angie’s setting; Royal MCP’s own endpoint is not affected.
Two plugins carrying different copies of the WordPress MCP Adapter	Mixed versions of the adapter loaded at once	Royal MCP keeps its MCP Adapter server off until one copy is left, and the report says which plugins carry a copy. Royal MCP’s own endpoint keeps working.
Any other plugin answering part of Royal MCP’s sign-in	AI clients land on the wrong sign-in page	The sign-in self-check names the plugin (by its name or its REST address) and the step it answers.
robots.txt blocking AI bots	AI assistants cannot read the site	The coexistence report lists which of GPTBot, ClaudeBot, Claude-User, ChatGPT-User, PerplexityBot and Google-Extended robots.txt blocks.

Check your site

See who answers your sign-in in 3 steps

No terminal and no guesswork: Royal MCP checks the same path your AI client takes.

Update Royal MCP

Royal MCP 1.5.12 or later, from WP Admin → Plugins. The own sign-in address and the self-check switch on with the update.

Open Royal MCP

If another plugin answers part of the sign-in, a notice names it with the fix. No notice means Royal MCP answers every step.

Ask for the full report

Ask your AI client to run wp_get_mcp_coexistence for every MCP server on the site and who answers each shared address.

FAQ

Common questions

No. Royal MCP only answers its own sign-in addresses, under /wp-json/royal-mcp/v1, and leaves every other address to the plugin that owns it. Your SEO plugin, AI writer or other MCP server keeps its own sign-in, and your AI clients can connect to both.

That message usually comes from another plugin’s sign-in, not from Royal MCP: the AI client reached a different plugin that does not know it. Update Royal MCP to 1.5.12 or later and connect again, and ChatGPT signs in at Royal MCP’s own address. The Royal MCP screens name the plugin that answered and show how to turn its sign-in off if you do not need it.

Usually not. Connections made before the update keep working, and new connections sign in at Royal MCP’s own address automatically. If an AI client that set itself up before the update reports a sign-in error when it next signs in, remove it in the client and add it again.

Yes. Each plugin keeps its own endpoint and sign-in, and Royal MCP never switches another plugin’s tools off. Many sites use Elementor’s or WooCommerce’s own MCP tools for what they do best and Royal MCP for the rest.

Ask your AI client to run wp_get_mcp_coexistence. It lists the other MCP servers and hubs on the site, which plugin answers each shared sign-in address, whether robots.txt blocks AI bots and which routes reach Royal MCP’s tools. Only administrators can run it.

Keep every AI plugin you rely on

Royal MCP is free from the WordPress.org plugin directory. It signs your AI clients in at its own address and works next to the SEO, AI and MCP plugins you already run.

Get Royal MCP