“Couldn’t reach the MCP server” is a generic connection error, not proof that your WordPress plugin is broken. The failure may happen during endpoint discovery, OAuth authorization, or an authenticated MCP request—and it may come from the plugin, WordPress, your host, a CDN, or a security layer. Find the failing step and inspect the request and response before changing settings.
First, identify where the connection stops
Note the exact URL you entered, the plugin and version, whether you are using Claude on the web or desktop, and the last step that succeeded. In particular, determine whether the error appears before an authorization window, during approval or token exchange, or after Claude shows the connector as connected.
As an Amazon Associate I earn from qualifying purchases.
- Before authorization: Claude may be unable to discover the endpoint or retrieve OAuth metadata.
- During or after approval: the browser may reach the consent page while a separate server-to-server token request is blocked or fails.
- After connection: an authenticated MCP request may have a transport, credential, or request-routing problem.
These stages use different requests and can fail independently. A working consent screen, for example, does not prove that token exchange or later MCP calls can reach your site.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Confirm the endpoint and the request that fails
Copy the transport URL from the current instructions for your specific plugin. Do not assume the plugin’s namespace or base path is the transport endpoint: an AI Engine support reply specifically cautions that entering the namespace root rather than its /http endpoint can cause a connection failure. Plugin instructions and paths can vary by product and version.
Use an HTTP client or the plugin’s diagnostics, if available, to reproduce the failing request. Record the URL, HTTP method, status, response headers, and response body. If you are checking whether the request reached WordPress or PHP, compare the result with a known WordPress response and check the corresponding access logs. Redact access tokens and other credentials before sharing logs.
Interpret those details together, rather than treating a status code as a diagnosis:
- A 404 or HTML page at a metadata URL can point to a wrong route, rewrite issue, or interception by a host or edge layer.
- A 401 on an authenticated request can indicate missing or invalid credentials, including an Authorization header that did not reach the application.
- A 403 can indicate a policy or security rule blocking the request.
- A 405 from a browser GET does not by itself show that a Streamable HTTP endpoint is broken if the transport expects POST. Test the method specified by the plugin and inspect that response.
These are clues, not fixed mappings: the URL, method, headers, body, and logs matter as much as the status.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
If Claude fails before showing authorization
Check the exact discovery and OAuth metadata URLs Claude requests. A registration endpoint can respond successfully while a separate metadata URL—possibly one with a path suffix—returns 404. Likewise, a working bare /.well-known/ URL does not establish that every path-suffixed discovery route works.
Rank #3
WordPress.org support threads describe both plugin-side discovery defects and requests to /.well-known/ that may be intercepted before reaching PHP. One Agent Abilities for MCP support report says version 1.7.1 fixed a reported path-suffixed protected-resource discovery route; that is a version-specific fix, not a general remedy for every plugin. Check your own plugin’s release notes and logs before changing server rules.
If authorization opens but the connection still fails
Browser authorization and backend requests can take different network paths. A browser may load the consent page while a CDN, host firewall, web application firewall (WAF), security plugin, or proxy blocks the later registration, token, or MCP request.
At the time of a failed attempt, check WordPress access logs, host and security-plugin logs, CDN security events, and the OAuth endpoint response. Look for the precise requested path and whether the request reached the application. Pay particular attention to edge bot rules and server or proxy rules affecting discovery, registration, token, or MCP paths. Do not infer that the browser’s successful page load means those backend requests succeeded.
If Claude connects but MCP calls fail
Check that the request uses the transport method the endpoint expects and that the Authorization header reaches the WordPress application. Also check whether a cache or security layer alters or blocks POST responses. Use the plugin’s diagnostics when available, and compare the failing request with the plugin’s current transport instructions.
Royal MCP support discussions describe version-specific Authorization-header handling and advise checking logs; Easy MCP AI support discussions distinguish a browser GET returning 405 from a transport tested with POST. Treat those reports as clues for matching setups, not as proof that the same defect exists on your site.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Apply the narrowest fix supported by the evidence
- Verify the URL and method. Use the current plugin instructions and confirm you entered the transport endpoint, not just a base or namespace path.
- Locate the failed stage. Establish whether discovery, authorization/token exchange, or authenticated tool requests fail, using the exact URL and timestamp.
- Check the plugin version and release notes. Some support cases describe fixes for discovery routing or Authorization-header handling. Update only when a release addresses the behavior you observed.
- Inspect the layer producing the response. Use access, host, CDN, WAF, and security-plugin logs to determine whether the request reached WordPress and what response it received.
- Change configuration narrowly. If logs identify a blocked route or altered request, adjust the relevant rule rather than broadly disabling security controls. Remove and re-add the Claude connector only if the plugin or provider’s instructions call for it.
What support reports can—and cannot—establish
WordPress.org support discussions provide concrete examples involving AI Engine, Royal MCP, Agent Abilities for MCP, and Easy MCP AI. They describe plugin-specific discovery and compatibility issues as well as possible host, CDN, and security-layer interference. They are individual support cases, not independent prevalence studies, so they do not establish that one cause is statistically “usual” or justify a percentage.
For a useful support request, include the plugin name and version, Claude client, exact endpoint path, last successful step, request method, status and response details, and relevant log entries with secrets removed. That evidence is more useful than the generic error alone.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
