Skip to main content
The Dashboard links here when the Wordfence plugin is active on the Dashboard site. Wordfence’s firewall runs before WordPress handles a request, so it can block an app’s request before the Dashboard sees it.

Start with the checks

In MainWP > AI > MainWP MCP > Connect directly, click Run the self-test, then Check from the internet. Troubleshooting explains each line. A Wordfence block page usually shows up in the check from the internet as “Something in front of WordPress blocks the well-known address: an error page, a server error or a challenge page.” or as “The MCP address didn’t answer with a sign-in request (HTTP 401).”

Find the blocked request

Open Wordfence’s Live Traffic view and look for requests to these paths around the time the app tried to connect:
With plain permalinks, the /wp-json/ paths use ?rest_route=/mainwp-remote/v1/… instead, and the sign-in page uses ?mainwp_oauth=authorize. Live Traffic shows whether the firewall blocked the request and which rule did it.

What to change

  • A firewall rule blocked the request. Allowlist that specific request in Wordfence instead of turning the firewall off or putting it into learning mode for the whole site.
  • Rate limiting throttled the app. An app can send many requests in a short time while it works. If Wordfence rate limiting blocked it, raise the limit or adjust the rule’s action for these paths.
  • A blocked IP or country. Hosted apps such as Claude and ChatGPT connect from their providers’ servers. A country or IP block can stop them even though your own browser gets through.
Don’t turn off Wordfence to make the connection work. MainWP still enforces its own sign-in, permission, and approval checks. Limit the exception to the request actually blocked. If the connection still fails, the local MCP server only needs HTTPS access from your computer and works as a fallback.