WP Rocket MCP

The WP Rocket MCP connector is available since WP Rocket 3.23.

MCP hub

Please refer to our MCP hub to get more information on:


Basic requirements

The following are the requirements to use the MCP connector:

  1. You must have a valid WP Rocket license.
  2. You need to install and activate the standalone MCP Adapter plugin (WP Rocket doesn’t bundle the MCP Adapter).

Troubleshooting connection issues

In some cases, when trying to connect WP Rocket MCP to Claude with OAuth, you might encounter some connection issues.

Unable to reach MCP Server


Couldn't reach [connector name]. You can check the server URL and verify the server is running. If this persists, share this reference with support: "ofid_f370e25f0ba839f6”

This error can happen if your hosting service has a Firewall or a Recaptcha system blocking Claude IPs. To fix this, contact your host to unblock Claude IP addresses (Anthropic IP addresses) or disable the Recaptcha system.


Site Health : MCP Oauth discovery documents

Sometimes in the Site Health tool you may see this message:

This message is a recommendation improvement when a .well-known hosting conflict is detected.

WordPress Site Health checks if external AI tools (e.g., Claude, Cursor) can automatically find your site’s connection URLs via /.well-known/oauth-....

Why do I see a “Recommended improvement” notice?

Some web hosts (OVH, cPanel, Plesk, managed hosts) intercept /.well-known/ requests for automated SSL renewals and return a 404 Not Found instead of passing the request to WordPress.

Does this affect WP Rocket or MCP?

No. This is an optional auto-discovery feature.

  • WP Rocket caching and features work normally.
  • MCP connections and authentication continue to work through direct WordPress API endpoints (/wp-json/...).

Do I need to fix it?

No action is required. If you want automatic discovery enabled, contact your host to allow non-SSL /.well-known/ requests to route through WordPress.

Last updated:

Was this article helpful?