Skip to main content
Find a fix by symptom.

Check the state first

Run expl server status. Exit code 0 from expl server tools list does not mean that the connection works (see Inspect commands). To see what is sent and received, add --verbose; it prints to standard error. Tokens are never printed, but review the output before you paste it anywhere.

When you contact support

Send these to support@exploratory.io: the output of expl --version, the command you ran, the exit code and the message. Hide any token or API key.

When you cannot connect from a company network

Ask your IT administrator to allow communication with exploratory.io. For an on-premises server, ask them to allow the URL of your own server.

The command is not found

For how to check when two copies are installed, see Installation.

Sign-in

To switch to a saved login while EXPL_SERVER_TOKEN is set, run unset EXPL_SERVER_TOKEN first, because it is used before a saved login. For how to create, pass and revoke an API key, see API keys.

Connection

Limits

The server that returns these errors is the same one that MCP Server uses. For the other errors it returns (NOT_FOUND, PERSONALIZED_CONTENT, CONTENT_UPDATING, UNSUPPORTED_OPERATION, RESULT_TOO_LARGE) and the limit on the number of requests per minute (120), see Limits and errors of MCP Server.

Data that cannot be queried

For how to write the JSON arguments, see Query data.