Self-hosted deployments
On our hosted service there's nothing to run, and you can connect straight away. This page is for Enterprise customers who run zlicx on their own infrastructure.
Where it fits
Run the MCP service on its own, separate from the API and these docs. Its traffic, logs and scaling needs are different from theirs, and keeping it separate lets you restart it without touching anything else.
AI client → MCP service → zlicx REST API
/mcp /api/v1Settings
| Variable | Purpose | Default |
|---|---|---|
| ZLICX_API_BASE_URL | Your API address, including /api/v1 | None |
| PORT | Port the service listens on | 8787 |
| MCP_ENDPOINT_PATH | Path of the MCP endpoint | /mcp |
| MCP_CORS_ORIGINS | Browser origins allowed to call it, separated by commas | None |
Keys
Don't give the service a shared API key. Each client sends its own key, and the service passes it on, so your organisation's permissions still decide what each client can do.
Health checks
Point your load balancer at GET /health. After each deployment, connect a client and run a read-only request, since a healthy service can still have the wrong API address.
Before going live
- Serve it over HTTPS only.
- Give it its own hostname and logs.
- Keep API keys out of your request logs.
- Set a rate limit at your load balancer.