Log inSubmit server
Zscaler Zero Trust Exchange logo

Zscaler Zero Trust Exchange

Connect AI agents to Zscaler services with read-only access by default and optional allowlisted write tools.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Zscaler Zero Trust Exchange

Pick your client, then add it in one click or paste the config.

STDIOPython
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "zscaler-zero-trust-exchange": {
      "command": "uvx",
      "args": [
        "zscaler-mcp"
      ],
      "env": {
        "ZSCALER_MCP_WRITE_ENABLED": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 254 tools correctly (15d ago).

Overview

The Zscaler Zero Trust Exchange MCP server connects AI agents to the Zscaler Zero Trust Exchange platform through MCP tools. It exposes tools across services including ZPA, ZIA, ZDX, and ZCC, with read-only list and get operations enabled by default. Write operations require both an explicit enablement flag and a tool allowlist. Reach for it when an agent needs to inspect or selectively manage Zscaler resources using natural-language requests.

Use cases

  • List ZPA application segments
  • Inspect ZIA rule labels
  • Review ZDX or ZCC resources
  • Enable selected Zscaler write operations
  • Limit exposed tools by service

Key features

  • 402 tools across Zscaler services
  • Read-only mode by default
  • Allowlisted create, update, and delete tools
  • ZPA, ZIA, ZDX, and ZCC coverage
  • Service-level tool selection
  • MCP client integrations

Tools254

What Zscaler Zero Trust Exchange lets your agent do. Expand a tool for its parameters.

Verified live~58.4k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

15/15 checks healthy over the last 61d

What it can do

From the 254 tools this server returned when we ran it; 254 declare their own safety hints.

Handles credentials · 8Makes network requests · 21Read-only tools · 254
Network at startup2 connections
Files written at startup20

Observed 2026-10-24 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 4d ago via OSV.dev · zscaler-mcp (PyPI)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars55Stargazers on the source repository.
Last commit12d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed254Callable tools this server registers over MCP.

How Zscaler Zero Trust Exchange works

What Zscaler Zero Trust Exchange MCP server does

The Zscaler Zero Trust Exchange MCP server gives MCP-compatible AI agents access to Zscaler platform data and operations. The repository documents 402 tools spanning multiple Zscaler services, including ZPA, ZIA, ZDX, ZCC, Zscaler Client Connector, EASM, and other services referenced by the project.

Typical requests include listing ZPA application segments, viewing ZPA segment groups, and retrieving ZIA rule labels. Prompts should identify both the service and the requested action because several Zscaler services may contain similarly named resources.

By default, the server exposes read-only operations. Agents can use list and get tools without enabling resource changes. Create, update, and delete operations are not available unless write access is deliberately configured.

How it works

The Zscaler Zero Trust Exchange MCP server runs as an MCP service and presents Zscaler operations as agent tools. An MCP client can discover the available tools and select one based on a prompt.

Read-only tools remain registered regardless of the write-related options. Service selection can reduce the set of exposed tools; disabled services have their tools removed from the server. The agent may still search other enabled services for related capabilities, so prompts should name the intended service.

Setup and configuration

The server can be started in its default read-only mode. To permit modifications, configure both the --enable-write-tools command-line option and the --write-tools allowlist. Setting only the global write option registers no write tools. The allowlist accepts exact tool names and wildcard patterns, such as a service-wide pattern or selected create and delete operations.

The same global write setting can be provided through ZSCALER_MCP_WRITE_ENABLED=true. Authentication and deployment documentation covers Zscaler API credentials, MCP client configuration, containers, remote deployments, Kubernetes, and cloud environments; the appropriate setup depends on where the server runs and which Zscaler APIs are being used.

Tools and capabilities

The documented tool groups support:

  • Reading Zscaler resources through list_* and get_* operations.
  • Creating, updating, or deleting resources when explicitly allowlisted.
  • Working with ZPA application segments and segment groups.
  • Inspecting ZIA rule labels and other service resources.
  • Selecting or disabling service groups to control which tools are exposed.

The Zscaler Zero Trust Exchange MCP server is therefore suitable for read-heavy investigation by default, with narrowly scoped automation available for teams that need changes through an agent.

Limitations and notes

The project is in public preview and under active development. Its features may change before the stable 1.0 release, and the README advises against production deployments during this phase.

Write access has two independent safeguards: the global write switch and a mandatory allowlist. Enabling the switch without naming tools does not enable modifications. An MCP client may also require individual read-only tools to be enabled in its own interface. Consult the project’s support and troubleshooting guidance before relying on the server.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Zscaler Zero Trust Exchange

Zscaler Zero Trust Exchange is an MCP server that connects AI agents to the Zscaler Zero Trust Exchange platform. Its main tools cover services such as ZPA, ZIA, ZDX, and ZCC, with list and get operations available by default and create, update, or delete tools enabled only through an explicit allowlist.

Install and configure the server using the repository’s MCP setup instructions. The project documents package, container, remote deployment, cloud, Kubernetes, and editor or assistant options, but the exact installation path depends on the environment where you plan to run it.

Enable write operations with both `--enable-write-tools` and `--write-tools`. The allowlist is mandatory, so enabling only the global flag registers no write tools. You can also set `ZSCALER_MCP_WRITE_ENABLED=true` for the global write setting, then provide the required tool allowlist.

Because Cursor may use deferred tool loading, write prompts with a specific service and action, such as listing ZPA application segments or showing ZIA firewall rules.

Related MCP servers

All in Security All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewZscaler Zero Trust Exchange AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/zscaler-zero-trust-exchange?style=directory)](https://allmcps.com/mcp/zscaler-zero-trust-exchange)
HTML Embed
<a href="https://allmcps.com/mcp/zscaler-zero-trust-exchange"><img src="https://allmcps.com/api/badge/zscaler-zero-trust-exchange?style=directory" alt="Zscaler Zero Trust Exchange on AllMCPs" /></a>