Zscaler Zero Trust Exchange

Zscaler Zero Trust Exchange runs locally from a Python package published to PyPI: zscaler-mcp version 0.15.4. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install — the usual command is uvx zscaler-mcp. It reads these environment variables: ZSCALER_CLIENT_ID (required, secret), ZSCALER_CLIENT_SECRET (required, secret), ZSCALER_CUSTOMER_ID (required) and ZSCALER_VANITY_DOMAIN (required); set them in the client's configuration for this server.

Zscaler Zero Trust Exchange runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: docker.io/zscaler/zscaler-mcp-server:latest. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Docker or another OCI container runtime; started with docker run — the usual command is docker run -i --rm docker.io/zscaler/zscaler-mcp-server:latest. Required arguments: -e, -e, -e and -e.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "zscaler-mcp-server": {
      "command": "uvx",
      "args": [
        "zscaler-mcp"
      ],
      "env": {
        "ZSCALER_CLIENT_ID": "<secret>",
        "ZSCALER_CLIENT_SECRET": "<secret>",
        "ZSCALER_CUSTOMER_ID": "<value>",
        "ZSCALER_VANITY_DOMAIN": "<value>"
      }
    }
  }
}

Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect