If an AI assistant fails to connect or a tool call errors, work through the checks below. Most problems come from one of four causes: the connection is switched off, the wrong URL was used, a security layer is blocking the REST API, or an OAuth redirect failed.
“Connect to the server” fails / 403 error
Security plugin blocking the REST API
The AI connection requires your REST API to be reachable from outside your server. A quick check: open https://your-store.com/wp-json/ in a private browser window — it should return JSON, not a challenge page or error.
OAuth redirect failures
The assistant connects but a tool returns “Not authenticated”
The request reached your store but no logged-in account was attached. Reconnect the assistant using your Connection URL so it completes the login and consent step, then try again.
The app will not ask to sign in again
Click Sign everyone out under Who is connected, then add the Connection URL to the app again. Removing the connector inside the app is not enough — the app keeps its own copy of the token until you revoke it here.
WooCommerce MCP — key rejected / tools missing
Licence expiry or staging-to-live migration
If the AST PRO licence expires, the MCP endpoint closes and all connections stop working. Renew the licence and confirm it is active, then reconnect. If you have migrated from staging to a live domain, the Connection URL changes with the domain — copy the new URL from the settings screen and update the connector in your AI app.
Still stuck?
Open the Audit Log to see whether requests are arriving and what error they return. If you need more help, open a support ticket at zorem.com/support and include the error message and the tool name shown in the log.