Cursor rule Cursor
Zscaler APIs have intentional cross-service data overlap. Disabling a service does not remove overlapping tools from other services.
Zscaler Integration MCP Server is a Model Context Protocol (MCP) server designed for managing Several Zscaler Products using Large Language Models (LLMs).
This repository also configures its own agents. See what zscaler-mcp-server tells them →
Cursor rule Cursor
Zscaler APIs have intentional cross-service data overlap. Disabling a service does not remove overlapping tools from other services.
Cursor rule Cursor
Write operations are disabled by default and require explicit enablement. Delete operations use HMAC confirmation tokens.
Cursor rule Cursor
ZDX is a read-only monitoring service. The since parameter is in hours, not timestamps.
Cursor rule Cursor
ZIA requires explicit activation after any create, update, or delete operation. Forgetting this is the number one source of issues.
Cursor rule Cursor
ZMS uses GraphQL and is read-only. Every query requires ZSCALERCUSTOMERID and uses specific pagination patterns.
Cursor rule Cursor
ZPA application onboarding requires resources to be created in a specific dependency order. Skipping dependencies causes cryptic 400 errors.
Cursor rule Cursor
Zscaler MCP tool naming, discovery, and usage conventions for the Zero Trust Exchange.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: