Zscaler MCP Server

Zscaler's own MCP server for the Zscaler Zero Trust Exchange. It connects your agent to Zscaler's services through OneAPI, so you can review policies, troubleshoot connectivity, audit security settings and investigate incidents in plain words. It's read-only unless you choose otherwise. What you can do with it - ZIA (Internet Access): review firewall, URL filtering, SSL inspection and sandbox rules, locations and URL categories, and check which category a URL falls in - ZPA (Private Access): review application segments, segment groups, server groups, app connectors and access policies, and onboard new applications - ZDX (Digital Experience): check application scores, ongoing alerts and device deep traces to troubleshoot someone's experience - ZCC (Client Connector): list enrolled devices and forwarding profiles - EASM: review findings and lookalike domains on your external attack surface - Z-Insights: look at web traffic, cyber incidents and shadow IT analytics - Also ZIdentity, Workload Segmentation (ZTW), Microsegmentation (ZMS) and Zscaler Cellular How it connects It runs on your machine with uvx zscaler-mcp (Python 3.11 or later, with uv installed), or from Zscaler's Docker image. It signs in to Zscaler with OneAPI credentials from an API client you create in the ZIdentity console: a client ID, a client secret (or a private key), your customer ID and your vanity domain. It only offers tools for the Zscaler products those credentials are entitled to. Zscaler also ships it as a Claude Code plugin with guided skills (onboarding a ZPA application, auditing SSL inspection, investigating ZDX alerts, troubleshooting a user's connectivity and more), as a Claude Desktop extension, and as a Gemini CLI extension. The plugin and the Gemini extension read your credentials from a .env file in their folder. Good to know - Read-only by default: only list and get tools are available. To let it create, change or delete anything, start it with --enable-write-tools and an explicit allowlist of write tools, such as --write-tools "zpa_create_*". - Deletes always need a confirmation first, and that check can't be turned off. - ZIA changes take effect once the staged configuration is activated. - You can load only the toolsets you need (--toolsets) to keep your agent's context small. - Zscaler calls it a public preview and asks you to avoid production deployments for now.

• “List my ZPA application segments.”

  1. zpa_list_application_segments
  Copy

• “Show my ZIA firewall rules.”

  1. zia_list_cloud_firewall_rules
  Copy

• “What category is twilio.com in?”

  1. zia_url_lookup
  Copy

• “Show ongoing ZDX alerts and the devices they affect.”

  1. zdx_list_alerts