Other · Local MCP server
Zscaler Zero Trust Exchange
Manage Zscaler Zero Trust Exchange via 400+ tools - ZPA, ZIA, ZDX, ZCC, ZTW, ZMS, EASM, and more.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.zscaler/zscaler-mcp-server- Version
- 0.15.4
- Status
- Active
- Category
- other
- Transport
- stdio (local process)
- Package
- PyPI, OCI image (Docker)
- Published
- 2026-08-19
- Updated
- 2026-08-19
- Publisher
- zscaler (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/zscaler) · how
- Website
- github.com/zscaler/zscaler-mcp-server
- Repository
- github.com/zscaler/zscaler-mcp-server
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| PyPIruntime: uvx | zscaler-mcp | 0.15.4 | stdio |
| OCI image (Docker)runtime: docker | docker.io/zscaler/zscaler-mcp-server:latest | - | stdio |
How to connect 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
More other servers
| Server | Runs |
|---|---|
| ZoogentAI agent orchestrator with Architect AI. Multi-team, web dashboard, 35+ MCP tools. | Local · stdio |
| Zoom Team ChatZoom Chat server for channels, messages, contacts, files, and chat collaboration. | Remote · HTTPLive check: sign-in required |
| Zoom WhiteboardZoom Whiteboard server for creating boards and diagrams and locating existing boards. | Remote · HTTPLive check: sign-in required |
| ZP NexusSuas IAs nos computadores e projetos da empresa, com permissões, aprovações e auditoria. | Remote · HTTPLive check: sign-in required |
| ZTL JudgeZero-trust logic judge: your AI writes a claim as a ZFL table, the ZTL core judges it. | Remote · HTTPLive check: ✓ handshake |
| ZuckerBot - Meta Ads MCP Server60+ Meta Ads tools for AI agents: audits, campaign management, audiences and CAPI tracking. | Remote & Local · HTTP, stdioLive check: sign-in required |
| Zuerst zuhause - Swiss new-build projectsSwiss building applications: new residential projects, months before they are advertised. | Remote · HTTPLive check: ✓ handshake |
| ZUGFeRD ValidatorValidiert E-Rechnungen (ZUGFeRD/Factur-X, XRechnung) gegen EN 16931 mit Korrekturvorschlägen. | Remote & Local · HTTP, stdioLive check: ✓ handshake |