Zscaler Zero Trust Exchange
MCP server by Zscaler
Manage Zscaler Zero Trust Exchange services such as ZPA, ZIA, ZDX and ZCC through more than 400 tools, read-only by default.
Install Zscaler Zero Trust Exchange
Runs on your machine. Your client starts it with this command:
Needs uv (Python) on your computer. The setup steps below show where the command goes in each client.
ZSCALER_CLIENT_IDsecret Zscaler OneAPI Client ID from ZIdentity console.ZSCALER_CLIENT_SECRETsecret Zscaler OneAPI Client Secret from ZIdentity console.ZSCALER_CUSTOMER_IDZscaler Customer ID from ZIdentity console.ZSCALER_VANITY_DOMAINZscaler vanity domain (e.g. mycompany.zscloud.net).
Share this server
Opens this page, with the install command and setup steps.
mcp.tc/i/zscaler-zero-trust-exchangeAbout
Connects an AI assistant to the Zscaler Zero Trust Exchange platform. It exposes about 400 tools across services including ZPA, ZIA, ZDX, ZCC, ZTW, ZMS and EASM, so you can list and inspect resources such as application segments, segment groups and firewall rule labels.
The server runs locally over stdio, started with uvx from the zscaler-mcp PyPI package, or as a Docker image. It needs a Zscaler OneAPI client ID, client secret, customer ID and vanity domain. It starts in read-only mode; create, update and delete tools need an explicit write flag plus an allowlist. The project is labelled public preview.
What you can do
- List and inspect ZPA application segments and segment groups
- Review ZIA configuration such as rule labels and firewall rules
- Query multiple Zscaler services from one server
- Run in read-only mode by default
- Enable selected write tools through an explicit allowlist
- Select which Zscaler services to load
Tools
Zscaler Zero Trust Exchange lists its tools only to clients with a key, so we can’t show them here.
Example prompts
List my ZPA application segments
Show ZIA firewall rules
List my ZPA segment groups
List my ZIA rule labels
Set up
Every client starts Zscaler Zero Trust Exchange on your machine with the same command. Pick yours; the page remembers your choice.
Claude Code
- Run this in a terminal, in your project folder:
claude mcp add --transport stdio zscaler-zero-trust-exchange --env "ZSCALER_CLIENT_ID=<YOUR_ZSCALER_CLIENT_ID>" --env "ZSCALER_CLIENT_SECRET=<YOUR_ZSCALER_CLIENT_SECRET>" --env "ZSCALER_CUSTOMER_ID=<YOUR_ZSCALER_CUSTOMER_ID>" --env "ZSCALER_VANITY_DOMAIN=<YOUR_ZSCALER_VANITY_DOMAIN>" -- uvx zscaler-mcp- Start Claude Code and type
/mcp. zscaler-zero-trust-exchange should show as connected.
Add --scope user to make it available in every project. Replace the placeholders with your own values.
Claude Desktop
- Open Settings → Developer → Edit Config. It opens
claude_desktop_config.json. Add:
{
"mcpServers": {
"zscaler-zero-trust-exchange": {
"command": "uvx",
"args": [
"zscaler-mcp"
],
"env": {
"ZSCALER_CLIENT_ID": "<YOUR_ZSCALER_CLIENT_ID>",
"ZSCALER_CLIENT_SECRET": "<YOUR_ZSCALER_CLIENT_SECRET>",
"ZSCALER_CUSTOMER_ID": "<YOUR_ZSCALER_CUSTOMER_ID>",
"ZSCALER_VANITY_DOMAIN": "<YOUR_ZSCALER_VANITY_DOMAIN>"
}
}
}
}- Save the file and restart Claude Desktop. Replace the placeholders with your own values.
Needs uv (Python) on your computer. The file lives in ~/Library/Application Support/Claude/ on macOS and %APPDATA%\Claude\ on Windows.
Cursor
Add to Cursor (opens in a new tab)
Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):
{
"mcpServers": {
"zscaler-zero-trust-exchange": {
"command": "uvx",
"args": [
"zscaler-mcp"
],
"env": {
"ZSCALER_CLIENT_ID": "<YOUR_ZSCALER_CLIENT_ID>",
"ZSCALER_CLIENT_SECRET": "<YOUR_ZSCALER_CLIENT_SECRET>",
"ZSCALER_CUSTOMER_ID": "<YOUR_ZSCALER_CUSTOMER_ID>",
"ZSCALER_VANITY_DOMAIN": "<YOUR_ZSCALER_VANITY_DOMAIN>"
}
}
}
}Needs uv (Python) on your computer. Replace the placeholders with your own values.
VS Code
Add it to .vscode/mcp.json. VS Code asks for the secret the first time and stores it securely:
{
"servers": {
"zscaler-zero-trust-exchange": {
"type": "stdio",
"command": "uvx",
"args": [
"zscaler-mcp"
],
"env": {
"ZSCALER_CLIENT_ID": "${input:zscaler-client-id}",
"ZSCALER_CLIENT_SECRET": "${input:zscaler-client-secret}",
"ZSCALER_CUSTOMER_ID": "<YOUR_ZSCALER_CUSTOMER_ID>",
"ZSCALER_VANITY_DOMAIN": "<YOUR_ZSCALER_VANITY_DOMAIN>"
}
}
},
"inputs": [
{
"type": "promptString",
"id": "zscaler-client-id",
"description": "ZSCALER_CLIENT_ID",
"password": true
},
{
"type": "promptString",
"id": "zscaler-client-secret",
"description": "ZSCALER_CLIENT_SECRET",
"password": true
}
]
}Needs uv (Python) on your computer.
Devin Desktop
- Add it to
~/.config/devin/mcp_config.json(macOS and Linux) or%APPDATA%\devin\mcp_config.json(Windows):
{
"mcpServers": {
"zscaler-zero-trust-exchange": {
"command": "uvx",
"args": [
"zscaler-mcp"
],
"env": {
"ZSCALER_CLIENT_ID": "<YOUR_ZSCALER_CLIENT_ID>",
"ZSCALER_CLIENT_SECRET": "<YOUR_ZSCALER_CLIENT_SECRET>",
"ZSCALER_CUSTOMER_ID": "<YOUR_ZSCALER_CUSTOMER_ID>",
"ZSCALER_VANITY_DOMAIN": "<YOUR_ZSCALER_VANITY_DOMAIN>"
}
}
}
}- Refresh the MCP server list in Cascade. Replace the placeholders with your own values.
Devin Desktop is the new name for Windsurf.
Codex
codex mcp add zscaler-zero-trust-exchange --env "ZSCALER_CLIENT_ID=<YOUR_ZSCALER_CLIENT_ID>" --env "ZSCALER_CLIENT_SECRET=<YOUR_ZSCALER_CLIENT_SECRET>" --env "ZSCALER_CUSTOMER_ID=<YOUR_ZSCALER_CUSTOMER_ID>" --env "ZSCALER_VANITY_DOMAIN=<YOUR_ZSCALER_VANITY_DOMAIN>" -- uvx zscaler-mcpOr edit ~/.codex/config.toml directly:
[mcp_servers.zscaler-zero-trust-exchange]
command = "uvx"
args = ["zscaler-mcp"]
env = { ZSCALER_CLIENT_ID = "<YOUR_ZSCALER_CLIENT_ID>", ZSCALER_CLIENT_SECRET = "<YOUR_ZSCALER_CLIENT_SECRET>", ZSCALER_CUSTOMER_ID = "<YOUR_ZSCALER_CUSTOMER_ID>", ZSCALER_VANITY_DOMAIN = "<YOUR_ZSCALER_VANITY_DOMAIN>" }Needs uv (Python) on your computer. Replace the placeholders with your own values.
Gemini CLI
gemini mcp add -e "ZSCALER_CLIENT_ID=<YOUR_ZSCALER_CLIENT_ID>" -e "ZSCALER_CLIENT_SECRET=<YOUR_ZSCALER_CLIENT_SECRET>" -e "ZSCALER_CUSTOMER_ID=<YOUR_ZSCALER_CUSTOMER_ID>" -e "ZSCALER_VANITY_DOMAIN=<YOUR_ZSCALER_VANITY_DOMAIN>" zscaler-zero-trust-exchange uvx zscaler-mcpThis adds it to the current project. Add -s user to use it everywhere.
Any client
Most clients that start local servers accept this shape:
{
"mcpServers": {
"zscaler-zero-trust-exchange": {
"command": "uvx",
"args": [
"zscaler-mcp"
],
"env": {
"ZSCALER_CLIENT_ID": "<YOUR_ZSCALER_CLIENT_ID>",
"ZSCALER_CLIENT_SECRET": "<YOUR_ZSCALER_CLIENT_SECRET>",
"ZSCALER_CUSTOMER_ID": "<YOUR_ZSCALER_CUSTOMER_ID>",
"ZSCALER_VANITY_DOMAIN": "<YOUR_ZSCALER_VANITY_DOMAIN>"
}
}
}
}Zed puts servers under context_servers in its settings, with the same command, args and env fields.
Needs uv (Python) on your computer. Replace the placeholders with your own values.
Embed
Show Zscaler Zero Trust Exchange in a README or on your site. Each embed links to this page, uses the server’s own install command, and sets no cookies. How embeds work
The card, the iframe and the JSON are in English. Add ?lang=it, fr, de or es to their address for another language.
README badge
[](https://mcp.tc/i/zscaler-zero-trust-exchange)<a href="https://mcp.tc/i/zscaler-zero-trust-exchange"><img src="https://mcp.tc/i/zscaler-zero-trust-exchange/badge.svg" alt="Zscaler Zero Trust Exchange on mcp.tc" height="20"></a>It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.
Website card
<script src="https://mcp.tc/w/zscaler-zero-trust-exchange.js" async></script>The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no cookies.
iframe
<iframe src="https://mcp.tc/embed/zscaler-zero-trust-exchange" title="Zscaler Zero Trust Exchange on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.
JSON
The listing as data for your own pages and tools: name, tagline, install command, tools and the “Add to” links. Any site can read it (CORS is open).
https://mcp.tc/i/zscaler-zero-trust-exchange.jsonAI prompt
Paste this into an AI coding assistant, such as Claude Code or Cursor, and it adds the Zscaler Zero Trust Exchange card to your site.
Add the mcp.tc card for Zscaler Zero Trust Exchange, an MCP server, to my website. It is one static script: no build step, no package to install, no cookies.
Put this tag where the card should appear. The card renders right before it:
```html
<script src="https://mcp.tc/w/zscaler-zero-trust-exchange.js" async></script>
```
To show the card somewhere else, put this placeholder there and load the same script once, for example before `</body>`. Keep the link inside: visitors without JavaScript see it.
```html
<div data-mcptc="zscaler-zero-trust-exchange"><a href="https://mcp.tc/i/zscaler-zero-trust-exchange">Zscaler Zero Trust Exchange on mcp.tc</a></div>
```
Options:
- `data-theme="light"` or `"dark"` on the tag or the placeholder fixes the colors. Without it, the card follows the visitor’s light or dark mode.
- `data-size="compact"` gives a smaller card without the tagline.
- The CSS variable `--mcptc-max-width` on the placeholder or a parent sets the width (default `520px`).
- `?lang=` on the script URL sets the card’s language: `en`, `it`, `fr`, `de` or `es`.
If the site has a Content Security Policy, allow `script-src https://mcp.tc` and `img-src data:` (the icon is inline).
For a README or other Markdown docs, use the badge instead:
```markdown
[](https://mcp.tc/i/zscaler-zero-trust-exchange)
```
Reference: https://mcp.tc/embedChange history
This server runs on your computer, so we follow its PyPI package: each new version shows up here, with edits by its owner.
FAQ
Can I paste mcp.tc/i/zscaler-zero-trust-exchange into my MCP client?
No. Zscaler Zero Trust Exchange runs on your own computer, started by your client, so it has no web address to connect to. The quick link is the page to share; the install command is uvx zscaler-mcp.
Does Zscaler Zero Trust Exchange need an API key?
Yes. It reads ZSCALER_CLIENT_ID, ZSCALER_CLIENT_SECRET, ZSCALER_CUSTOMER_ID and ZSCALER_VANITY_DOMAIN from its environment, and ZSCALER_CLIENT_ID and ZSCALER_CLIENT_SECRET are secrets. Put the values in your client’s config on your own machine, never in a shared file.
Is Zscaler Zero Trust Exchange a remote or a local server?
Local. Your client starts it as a process on your computer with uvx zscaler-mcp, which needs uv (Python).
What can Zscaler Zero Trust Exchange do?
You can list and inspect ZPA application segments and segment groups, review ZIA configuration such as rule labels and firewall rules and query multiple Zscaler services from one server.
Which clients can use it?
Any client that starts local servers: Claude Code, Claude Desktop, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. claude.ai and ChatGPT only connect to remote servers.
Does mcp.tc track changes to Zscaler Zero Trust Exchange?
Partly. It runs on your computer, so we follow its PyPI package: its History tab shows each new version and edits by its owner. Follow the listing to get an email when it changes.
Who wrote this page?
mcp.tc’s robot read Zscaler Zero Trust Exchange’s public metadata (its package and repository pages), and an AI model drafted the text from it. A person reviews anything the checks can’t confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.
mcp.tc isn’t affiliated with Zscaler. This page was built from Zscaler Zero Trust Exchange’s public metadata, last checked on 4 Oct 2026, and an AI model wrote the description, so it can be wrong. Names and marks belong to their owners. Something off? Report this listing.