Zscaler Zero Trust Exchange

Name: Zscaler Zero Trust Exchange
Author: zscaler

by zscalerversion 0.15.4i★ –iRuns on your computer

Registry nameio.github.zscaler/zscaler-mcp-server

Install

Overview

Description from the maker (original English)

Manage Zscaler Zero Trust Exchange via 400+ tools — ZPA, ZIA, ZDX, ZCC, ZTW, ZMS, EASM, and more.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other
You need to fill in: ZSCALER_CLIENT_ID, ZSCALER_CLIENT_SECRET, ZSCALER_CUSTOMER_ID, ZSCALER_VANITY_DOMAIN

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: ZSCALER_CLIENT_ID, ZSCALER_CLIENT_SECRET, ZSCALER_CUSTOMER_ID, ZSCALER_VANITY_DOMAIN

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

PyPIPython’s uv installed (for the uvx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

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

Run this in your terminal

claude mcp add zscaler --env ZSCALER_CLIENT_ID=your-value --env ZSCALER_CLIENT_SECRET=your-value --env ZSCALER_CUSTOMER_ID=your-value --env ZSCALER_VANITY_DOMAIN=your-value -- uvx zscaler-mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "zscaler": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "zscaler-mcp"
      ],
      "env": {
        "ZSCALER_CLIENT_ID": "your-value",
        "ZSCALER_CLIENT_SECRET": "your-value",
        "ZSCALER_CUSTOMER_ID": "your-value",
        "ZSCALER_VANITY_DOMAIN": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

ZSCALER_CLIENT_ID secret required env
Zscaler OneAPI Client ID from ZIdentity console.
ZSCALER_CLIENT_SECRET secret required env
Zscaler OneAPI Client Secret from ZIdentity console.
ZSCALER_CUSTOMER_ID required env
Zscaler Customer ID from ZIdentity console.
ZSCALER_VANITY_DOMAIN required env
Zscaler vanity domain (e.g. mycompany.zscloud.net).

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account zscaler, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 32545 servers in this category
Published to the registry more recently than 26% of the other 32545 servers in this category
Basic checks equal to or better than 100% of the other 32545 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Zscaler Zero Trust Exchange safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: ZSCALER_CLIENT_ID, ZSCALER_CLIENT_SECRET, ZSCALER_CUSTOMER_ID, ZSCALER_VANITY_DOMAIN

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.15.4) reached the registry 3 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv), Docker on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Python MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday

Install

Python MCP

by Files-com

Local-only Python MCP server for the Files.com API.

Runs on your computerUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

zscaler-mcp-server is a Model Context Protocol (MCP) server that connects AI agents with the Zscaler Zero Trust Exchange platform. By default, the server operates in read-only mode for security, requiring explicit opt-in to enable write operations.

Support Disclaimer

-> Disclaimer: Please refer to our General Support Statement before proceeding with the use of this provider. You can also refer to our troubleshooting guide for guidance on typical problems.

[!IMPORTANT]

🚧 Public Preview: This project is currently in public preview and under active development. Features and functionality may change before the stable 1.0 release. While we encourage exploration and testing, please avoid production deployments. We welcome your feedback through GitHub Issues to help shape the final release.

📄 Table of contents

📺 Overview
🔒 Security & Permissions
🔐 MCP Client Authentication
Supported Tools
Installation & Setup
Prerequisites
Environment Configuration
Installation
Usage
Command Line
Service Configuration
Additional Command Line Options
Zscaler API Credentials & Authentication
OneAPI Authentication
Authentication Troubleshooting
MCP Server Configuration
As a Library
Container Usage
Using Pre-built Image (Recommended)
Building Locally (Development)
Editor/Assistant Integration
Using uvx (recommended)
With Service Selection
Using Individual Environment Variables
Docker Version
Additional Deployment Options
Remote MCP Deployment (EC2, VM, etc.)
Azure Container Apps / Virtual Machine / AKS (Preview)
Google Cloud (Cloud Run / GKE / VM / ADK Agent)
Kubernetes (Helm Chart)
Amazon Bedrock AgentCore
Using the MCP Server with Agents
Claude Desktop
Cursor
Visual Studio Code + GitHub Copilot
Platform Integrations
Troubleshooting
License

📺 Overview

The Zscaler Integrations MCP Server brings context to your agents. Try prompts like:

"List my ZPA Application segments"
"List my ZPA Segment Groups"
"List my ZIA Rule Labels"

[!WARNING]

🔒 READ-ONLY BY DEFAULT: For security, this MCP server operates in read-only mode by default. Only list_* and get_* operations are available. To enable tools that can CREATE, UPDATE, or DELETE Zscaler resources, you must explicitly enable write mode using the --enable-write-tools flag or by setting ZSCALER_MCP_WRITE_ENABLED=true. See the Security & Permissions section for details.

[!TIP]

Writing effective prompts: This server exposes 402 tools across multiple Zscaler services. Most MCP clients (Claude Desktop, Cursor, etc.) use deferred tool loading and will search for relevant tools based on your prompt. For best results, be specific about the service and action in your prompts:

- Good: *"List my ZPA application segments"* — targets the right service and tool directly

- Good: *"Show ZIA firewall rules"* — clear service (zia) and action (list)

- Less effective: *"Show me my devices"* — ambiguous; multiple services expose device-related tools

When a service is disabled, its tools are fully removed from the server. However, the AI agent may still attempt to find related tools in other services. If you get unexpected results, refine your prompt with the specific service name (e.g. zpa, zia, zdx, zcc, zcell, zms).

🔒 Security & Permissions

The Zscaler MCP Server implements a security-first design with granular permission controls and safe defaults:

Read-Only Mode (Default - Always Available)

By default, the server operates in read-only mode, exposing only tools that list or retrieve information:

✅ ALWAYS AVAILABLE - Read-only tools are registered by the server
✅ Safe to use with AI agents autonomously
✅ No risk of accidental resource modification or deletion
✅ All list_* and get_* operations are available (110+ read-only tools)
❌ All create_*, update_*, and delete_* operations are disabled by default
💡 Note: You may need to enable read-only tools in your AI agent's UI settings

# Read-only mode (default - safe)

zscaler-mcp

When the server starts in read-only mode, you'll see:

🔒 Server running in READ-ONLY mode (safe default)

Only list and get operations are available To enable write operations, use --enable-write-tools AND --write-tools flags

💡 Read-only tools are ALWAYS registered by the server regardless of any flags. You never need to enable them server-side. Note: Your AI agent UI (like Claude Desktop) may require you to enable individual tools before use.

Write Mode (Explicit Opt-In - Allowlist REQUIRED)

To enable tools that can create, modify, or delete Zscaler resources, you must provide BOTH flags:

✅ --enable-write-tools - Global unlock for write operations
✅ --write-tools "pattern" - MANDATORY explicit allowlist

🔐 SECURITY: Allowlist is MANDATORY - If you set --enable-write-tools without --write-tools, 0 write tools will be registered. This ensures you consciously choose which write operations to enable.

# ❌ WRONG: This will NOT enable any write tools (allowlist missing)

zscaler-mcp --enable-write-tools

✅ CORRECT: Explicit allowlist required

zscaler-mcp --enable-write-tools --write-tools "zpa_create_*,zpa_delete_*"

When you try to enable write mode without an allowlist:

⚠️  WRITE TOOLS MODE ENABLED

⚠️ NO allowlist provided - 0 write tools will be registered ⚠️ Read-only tools will still be available ⚠️ To enable write operations, add: --write-tools 'pattern'

Write Tools Allowlist (MANDATORY)

The allowlist provides two-tier security:

✅ First Gate: --enable-write-tools must be set (global unlock)
✅ Second Gate: Explicit allowlist determines which write tools are registered (MANDATORY)

Allowlist Examples:

# Enable ONLY specific write tools with wildcards

zscaler-mcp --enable-write-tools --write-tools "zpa_create_*,zpa_delete_*"

Enable specific tools without wildcards

zscaler-mcp --enable-write-tools --write-tools "zpa_create_application_segment,zia_create_rule_label"

Enable all ZPA write operations (but no ZIA/ZDX/ZTW)

zscaler-mcp --enable-write-tools --write-tools "zpa_*"

Or via environment variable:

export ZSCALER_MCP_WRITE_ENABLED=true

export ZSCALER_MCP_WRITE_TOOLS="zpa_create_*,zpa_delete_*" zscaler-mcp

Wildcard patterns supported:

zpa_create_* - Allow all ZPA creation tools
zpa_delete_* - Allow all ZPA deletion tools
zpa_* - Allow all ZPA write tools
*_application_segment - Allow all operations on application segments
zpa_create_application_segment - Exact match (no wildcard)

When using a valid allowlist, you'll see:

⚠️  WRITE TOOLS MODE ENABLED

⚠️ Explicit allowlist provided - only listed write tools will be registered ⚠️ Allowed patterns: zpa_create_*, zpa_delete_* ⚠️ Server can CREATE, MODIFY, and DELETE Zscaler resources 🔒 Security: 85 write tools blocked by allowlist, 8 allowed

Tool Design Philosophy

Each operation is a separate, single-purpose tool with explicit naming that makes its intent clear:

✅ Good (Verb-Based - Current Design)

zpa_list_application_segments    ← Read-only, safe to allow-list

zpa_get_application_segment ← Read-only, safe to allow-list zpa_create_application_segment ← Write operation, requires --enable-write-tools zpa_update_application_segment ← Write operation, requires --enable-write-tools zpa_delete_application_segment ← Destructive, requires --enable-write-tools

This design allows AI assistants (Claude, Cursor, GitHub Copilot) to:

Allow-list read-only tools for autonomous exploration
Require explicit user confirmation for write operations
Clearly understand the intent of each tool from its name

Responses: the API record, verbatim

A read tool returns the Zscaler API record unchanged. The server does not trim, rename, or re-declare a resource's attributes — that attribute set belongs to the API, so a field Zscaler adds in future reaches you with no server upgrade.

To keep responses small, you control what comes back rather than the server guessing. Two levers:

`--toolsets` — load only the slice of tools you need, so the tool catalog stays small (see Toolsets).
`query` — every list tool accepts an optional JMESPath expression applied to the results, so the agent projects exactly what it wants:

  zcc_list_devices(query="[*].{user: user, policy: policyName}")   # just those two fields

zcc_list_devices(query="[?registrationState=='Quarantined']") # just quarantined devices zcc_list_devices(query="length(@)") # just the count

Field names are exactly what the Zscaler API returns. Omit query to get the full records.

Security Layers

The server implements multiple layers of security (defense-in-depth). The first nine apply on every transport, including stdio — they govern which tools are exposed and how dangerous calls are confirmed. The remaining HTTP-only layers (TLS, host-header validation, source-IP ACL, MCP client authentication) are described in the Network-Level Controls section further down.

**Read-Only T

Only the beginning is shown; read the rest in the repo

Zscaler Zero Trust Exchange

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

Python MCP

README from the maker

Support Disclaimer

📄 Table of contents

📺 Overview

🔒 Security & Permissions

Read-Only Mode (Default - Always Available)

Write Mode (Explicit Opt-In - Allowlist REQUIRED)

✅ CORRECT: Explicit allowlist required

Write Tools Allowlist (MANDATORY)

Enable specific tools without wildcards

Enable all ZPA write operations (but no ZIA/ZDX/ZTW)

Tool Design Philosophy

✅ Good (Verb-Based - Current Design)

Responses: the API record, verbatim

Security Layers