If an AI assistant fails to connect or a tool call errors, work through the checks below. Most connection problems come from one of three causes: the assistant is switched off, the wrong URL was used, or a security layer is blocking your REST API.
“Connect to the server” fails / 403 error
- Is the assistant enabled? Go to AI Settings, make sure Enable AI Assistant is ON, and click Save Changes. The toggle does nothing until saved.
- Are you using the right URL? It must be your store’s Returns connection URL —
/wp-json/zorem-returns/mcp/v1/mcp— not any other MCP endpoint. Use the Copy button to avoid typos. - Is a security plugin blocking the REST API? See the next section — this is the most common cause of a 403 when everything else looks correct.
A security plugin is blocking the REST API
The AI connection relies on your site’s REST API being reachable by outside clients. Some security plugins (and some firewalls) restrict the WordPress REST API to logged-in users only, which blocks the connection before the plugin ever runs. A quick way to confirm: open https://your-store.com/wp-json/ in a private browser window — it should return data, not an error.
- In your security plugin, look for a setting like Restrict REST API or Require authentication for REST API and disable it, or allow anonymous access.
- If you use a firewall (for example Cloudflare or a host-level WAF), make sure it isn’t blocking requests to
/wp-json/. - After changing the setting,
https://your-store.com/wp-json/should load, and the connection will complete.
The assistant connects but a tool returns “Not authenticated”
This means the request reached your store but no logged-in account was attached. Reconnect the assistant using the Connection URL so it completes the login/consent step, then try again.
The connector shows “failed” in desktop / advanced sessions
If a local or advanced session reports a tools-list error, make sure the plugin is updated to the latest version — older versions could send a tool definition that stricter clients reject. Updating resolves it.
Still stuck?
Open the Audit Log to see whether requests are arriving and what error they return. If you need more help, reach out through Get Support and include the error message and the tool name shown in the log.