Recommended Free Tools
The message “Couldn’t reach the MCP server” does not identify a single fault. First find the earliest request that fails: the WordPress endpoint may be reachable but refusing an unauthenticated request, or the failure may occur earlier in DNS, HTTPS, routing, or OAuth discovery—or later during consent, token exchange, or the authenticated MCP call. The correct endpoint and authentication flow depend on the WordPress integration and client.
What the error does—and does not—tell you
A client may display: “Couldn’t reach the MCP server. You can check the server URL and verify the server is running. If this persists, share this reference with support.” That message is a symptom, not a diagnosis. It does not establish that WordPress is down, that the configured URL is wrong, or that a particular authentication setting is at fault.
One open report in the WordPress/mcp-adapter issue tracker, opened April 2, 2026, describes a self-hosted site connected to Claude with WordPress MCP plugin version 0.2.5. The reporter said MCP, Create Tools, and Update Tools were enabled and a JWT token had been created. The configured URL was https://shop.mydomain.co.uk/wp-json/wp/v2/wpmcp/streamable; opening it directly returned JSON indicating “unauthorized” with HTTP 401. The issue remains open without a posted resolution in the inspected page. The reporter suspected that the client was not sending the token, but that explanation is not confirmed by a maintainer.
That example illustrates why status codes need context: a 401 response means an HTTP server answered and denied the request for lack of acceptable authentication. It is different from a DNS lookup failure or timeout, and it does not by itself prove the MCP service is unavailable. Whether a particular plugin should return 401 for an unauthenticated test depends on its documented behavior.
Identify your WordPress MCP setup first
Before changing settings, write down the integration and its version, the MCP client and its version, the exact configured URL, whether the client runs locally or remotely, the authentication method, and the full error text. WordPress has more than one MCP connection pattern, so a route that is correct for one plugin may be wrong for another.
The WordPress MCP Adapter project describes its purpose as bridging the Abilities API to the Model Context Protocol, allowing clients to discover and invoke WordPress plugin, theme, and core abilities. That description does not mean every WordPress MCP plugin uses the adapter or shares its routes.
There is no evidence-based universal rule that a “custom connector” is preferable to a WordPress-branded connector. Choose the connection method documented for the specific integration, then verify its URL, transport, and credential flow. A real setup question raised in the issue above—whether to use a custom connector with the listed endpoint or a WordPress connector—has no answer in that issue.
Debug the connection in order
-
Request the exact documented endpoint
Copy the URL from your integration’s documentation or settings, rather than adapting a route from another plugin. Request that exact URL independently and record the status code, response body, and headers. Compare the result with the integration’s documented unauthenticated or health-check behavior. A 401 may indicate that the endpoint is responding and expects credentials; it does not establish that the client successfully supplied them.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsSpecial offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy. -
Check public DNS and HTTPS reachability
If the MCP client is remote, test the hostname and HTTPS URL from a network outside the WordPress server’s local environment. A hostname that resolves only on an office network, VPN, or local machine is not necessarily reachable by an external service. A successful browser test from an administrator’s computer also does not reproduce every network path or request made by the client.
-
Check OAuth discovery only if your integration uses OAuth
Some remote connection flows begin with metadata discovery, continue through dynamic client registration and browser consent, then exchange a token before the first authenticated MCP request. The Meow Apps remote MCP connection troubleshooting guide, updated September 2026, describes that sequence for its AI Engine setup. It recommends checking both path-suffixed and host-root
.well-knowndiscovery URLs. Use the exact paths documented for your own integration; those AI Engine routes are not universal WordPress routes. -
Compare what reaches the edge with what reaches WordPress
Watch the relevant web-server, CDN or WAF, and PHP/application logs while attempting the connection. The Meow Apps troubleshooting guide also recommends comparing responses with the client User-Agent. If a request receives a 403 or 404 and never appears in PHP logs, investigate routing or filtering before changing WordPress application settings. If it reaches the application, use the integration’s logs to determine whether discovery, registration, consent, token exchange, or the authenticated MCP request failed.
-
Change one relevant setting, then repeat the same test
Keep the URL, request, and test conditions constant while changing one setting tied to the stage that failed. Record the result each time. This makes it easier to tell whether the change affected the failure, instead of attributing improvement to an unrelated simultaneous change.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.Best Value
hosting servers- easy to use
- Free app
- Compatible with all devices
- It gives the best comparison between ten different hosts
Use the first failed stage to narrow the cause
| What you observe | What it tells you | What to check next |
|---|---|---|
| Hostname does not resolve, or the request times out | The request may be failing before it reaches the WordPress endpoint. | Test public DNS and HTTPS reachability from outside the site’s local environment; then check host, network, and edge logs. |
| HTTP 401 with an unauthorized response | The endpoint answered, but the request was not accepted as authenticated. This alone does not prove that the MCP service is down. | Compare with the integration’s expected unauthenticated response, then verify where and how its client sends credentials. |
| HTTP 403 or 404, with no matching PHP log entry | The request may be blocked or misrouted before WordPress handles it. | Check web-server, CDN, WAF, routing, and request-filtering behavior. |
| OAuth discovery fails before a consent screen | The failure is earlier than user approval or the first authenticated MCP call. | Verify the integration’s documented discovery URLs and compare responses at the host or CDN edge. |
| Discovery and consent work, but the connection fails afterward | The failing step may be registration, token exchange, or the authenticated MCP request. | Inspect the relevant application and server logs for the first failing request and its response. |
When to escalate
If the failure persists, give your host, plugin developer, or client support the integration and version, client and version, exact endpoint with any secret values removed, whether the client is local or remote, authentication method, timestamp, observed status and response, and the first matching log entry. Do not post JWTs, OAuth access or refresh tokens, or other credentials. If your symptoms match the April 2026 report, note that its 401 response and JWT configuration are a single unresolved case—not proof of a general WordPress MCP bug or a confirmed token-passing defect.
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.
