Docs Advanced Shipment Tracking Troubleshooting the AI Assistant

Troubleshooting the AI Assistant

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 connection 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 connection enabled? Go to AI Assistant > AST MCP and make sure Enable the AST PRO connection is ON. It saves as soon as you switch it.
  • Are you using the right URL? It must be your store’s link — /wp-json/zorem-mcp/v1/mcp — not any other MCP endpoint. Use the Copy button to avoid typos.
  • Is a security plugin blocking the REST API? Click Test my link — it names the plugin and the setting when it can. See the next section.

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 or block callers by user agent, which stops 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, Block user-agents or a bad-bot list, and allow the path /wp-json/zorem-mcp/.
  • If you use a firewall (for example Cloudflare or a host-level WAF), make sure it isn’t blocking requests to /wp-json/ or filtering callers by name.
  • After changing the setting, run Test my link again — it should report that callers from outside are getting through.

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 your link so it completes the login/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 link to the app again. Removing the connector inside the app is not enough, because the app keeps its own copy of the connection.

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.