IS_WPE or WPE_APIKEY constant that WP Engine defines.
On WP Engine, the web server and its page cache are managed for you. Most fixes on this page are requests to WP Engine support rather than settings you change yourself.
Start with the checks
In MainWP > AI > MainWP MCP > Connect directly, click Run the self-test, then Check from the internet. Note everyfail and warn line. Troubleshooting explains each one.
What to look at
The well-known addresses. If the self-test reports “Requests for the well-known addresses don’t reach WordPress, so no app can find how to sign in.”, ask WP Engine support to pass these two paths to WordPress’sindex.php, keeping the original address:
Authorization request header to PHP for your site.
Caching. The Dashboard marks every remote AI response as not cacheable. If the check from the internet reports “The MCP address didn’t answer with a sign-in request (HTTP 401).” while the self-test passes, ask support to exclude these paths from the page cache:
?rest_route=/mainwp-remote/v1/mcp instead. Mention that form if your site uses it.
What to send to support
- your Dashboard’s address
- the failing lines from the self-test and the check from the internet, word for word
- the rule the self-test shows, if any
- the time you ran the checks, so support can find the requests in the server logs
rest_route points into /mainwp-remote/ and requests with a mainwp_oauth parameter in any relevant challenge or cache exception. Keep the exception specific to these endpoints.