Appearance
Fix HTTP 405 Method Not Allowed Errors in Easy MCP AI
An HTTP 405 error means the server does not allow the request method used for that URL. The right fix depends on whether the error appears while saving settings or tools in WordPress, or while connecting an AI client.
In this article
Identify where the 405 error occurs
If the error appears after you save Easy MCP AI settings or tool choices in WordPress, check the admin-save request in the next section. If an AI client reports the error while connecting, check the MCP request and caching sections instead.
The request path and method identify which layer is involved. Do not apply every fix: a page-cache exclusion will not allow a blocked request method, and changing a client's method will not resolve a host rule blocking an admin save.
Fix a 405 while saving settings or tools
Easy MCP AI saves settings and tool choices with PATCH requests under /wp-json/easy-mcp-ai-admin/v1/. A host, web application firewall (WAF), or security rule that rejects PATCH can return HTTP 405 before WordPress processes the save.
Contact your hosting provider or security provider and share:
- The route under
/wp-json/easy-mcp-ai-admin/v1/that returned the error. - The
PATCHrequest method. - The time the failed save occurred.
- The HTTP 405 status.
Ask them to allow the required request for this route with a narrow exception. Do not ask them to disable the firewall or other security protection globally.
Fix a 405 while connecting an AI client
Use POST for the MCP endpoint
MCP protocol requests to /wp-json/easy-mcp-ai/v1/mcp use the Streamable HTTP transport and the POST method. An authenticated GET request to this endpoint returns HTTP 405 by design. Opening the endpoint URL in a browser sends a GET, so it is not a valid health check.
If you use a custom client, check that it uses Streamable HTTP, the correct endpoint, and the authentication method it supports. For the setup details, see How to Connect Other MCP Clients to WordPress. If Cloudflare returns the 405 response, follow Troubleshoot Cloudflare Blocking Easy MCP AI Connections.
Exclude MCP and OAuth paths from page caching
If a page cache handles Easy MCP AI requests, ask the cache provider to exclude these paths from page caching:
/wp-json/easy-mcp-ai//.well-known/oauth-*/.well-known/openid-configuration
If your cache provider uses different wildcard syntax, translate these patterns according to its documentation. Use these exclusions only when caching is involved: they do not resolve a host or security rule that blocks PATCH, or a client that sends GET instead of POST.
Verify the resolution
Retry the exact action that produced the error. For a settings or tool save, refresh the WordPress screen and confirm the change remains selected.
For an AI client connection, go to Easy MCP AI > Dashboard, find Diagnostics, and select Re-run. Then select Test from the internet and follow Troubleshooting Easy MCP AI Connection Issues for the full diagnostics and reachability steps. Reconnect the client using How to Connect Other MCP Clients to WordPress, then make a simple read-only tool call to confirm it can reach your site.