Troubleshooting

Most connection problems come down to the key, its permissions, or the server address.

The client can't connect

Check that the address includes the /mcp path, and that your client supports remote servers over HTTP. Then restart the client, since many only read their settings at startup.

401: the key is rejected

The request has no valid key. Check that your client is sending the x-api-key header, that the placeholder has been replaced, and that the key hasn't been revoked. Console login cookies don't work here.

403: not enough permissions

The key is valid, but it can't use that tool or resource. Create a key with the permission it needs under Settings → API keys, then update your client. See API keys.

404 from a tool

The MCP server responded, but the API behind it doesn't have that route. On a self-hosted deployment, check that ZLICX_API_BASE_URL points to the right host, and that your API version is up to date.

The assistant chooses the wrong tool

Have your client ask before using anything that costs money or removes data, and give the key only the permissions it needs. See risk levels.

Still stuck?

Contact us with the client you're using, the tool you called and the error you saw. Please don't include your API key.