Configuration
Configuration
Section titled “Configuration”The Xplorr MCP server is configured via environment variables.
Environment variables
Section titled “Environment variables”| Variable | Required | Default | Description |
|---|---|---|---|
XPLORR_API_TOKEN | Yes* | — | Your xplorr_ prefixed API token from the portal |
XPLORR_API_URL | No | https://api.xplorr.io | Override if self-hosting the Xplorr backend |
PORT | No | 3005 | Port for the MCP HTTP server |
*Required in single-tenant (self-hosted) mode. In multi-tenant mode, the token is passed per-request via Authorization: Bearer xplorr_....
Getting an API token
Section titled “Getting an API token”- Log in to xplorr.io
- Go to Settings → API Tokens
- Click Create Token
- Copy the token (it starts with
xplorr_)
Example .env file
Section titled “Example .env file”# RequiredXPLORR_API_TOKEN=xplorr_your_token_here
# Optional — override for on-prem deployments# XPLORR_API_URL=https://api.your-company.com
# Optional — change the listen port# PORT=3005Pointing at a self-hosted backend
Section titled “Pointing at a self-hosted backend”If you run the Xplorr platform on your own infrastructure, set XPLORR_API_URL to your backend’s URL:
XPLORR_API_TOKEN=xplorr_your_token_hereXPLORR_API_URL=https://api.your-company.comHealth check endpoint
Section titled “Health check endpoint”The server exposes a health endpoint at GET /health:
curl http://localhost:3005/health{ "status": "ok", "service": "xplorr-mcp", "tools": 21, "mode": "single-tenant"}