zscaler-mcp-server
OfficialRelated Servers
Alternatives to zscaler-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to securely access and act on CRM, order, support, and automation systems through the Model Context Protocol, with authentication, authorization, audit logging, and guardrails.MIT
- AlicenseNot gradedqualityCmaintenanceConnects AI agents to TiddlyWiki through the Model Context Protocol, enabling listing, searching, filtering, creating, updating, and deleting tiddlers. Defaults to read-only mode with optional write permissions.9MIT
- AlicenseNot gradedqualityBmaintenanceConnects AI agents with the CrowdStrike Falcon platform to programmatically access detections, threat intelligence, host management, and other security capabilities for intelligent security analysis and automation.1MIT
- AlicenseAqualityAmaintenanceEnables AI-powered ticket analysis and comprehensive Zendesk API integration via the Model Context Protocol, supporting both API token (CLI) and OAuth 2.1 (web) authentication modes.55312 npm5MIT
- AlicenseAqualityCmaintenanceConnects LLM agents to Apache Atlas for searching, tracing lineage, and managing metadata. Read-only by default, with optional write mode for creating entities and classifications.16MIT
- AlicenseNot gradedqualityAmaintenanceEnables secure enterprise AI agents to access internal tools like GitHub, Gmail, Calendar, file systems, databases, and knowledge bases through the Model Context Protocol, with built-in security, audit, and observability.MIT
TDQS
Scored across 254 tools
The set is mostly organized by product and resource, so standard list/get pairs are clear, but exact duplicate operations exist via `*_lite` variants (e.g., zia_list_devices vs zia_list_devices_lite, ztw_list_ip_groups vs ztw_list_ip_groups_lite) and some tools combine list-or-fetch-by-ID behavior, blurring the usual list/get boundary. The descriptions are unusually thorough and often disambiguate overlap, but at 254 tools an agent still has several plausible wrong choices.
The dominant `{product}_{verb}_{noun}` pattern is readable and consistent across ZIA, ZPA, ZDX, ZMS, ZCELL, and ZTW. However, a separate `get_zia_*` and `get_zpa_*` family reverses the prefix order, and a few tools like zdx_get_web_probes, zia_url_lookup, and zia_geo_search deviate from the list/get semantics. The conventions are mixed but still navigable.
254 tools is far beyond what an agent can practically keep in context, even for a multi-product vendor like Zscaler. The surface is heavily inflated by read-only list/get pairs, lite endpoint duplicates, and near-identical resource catalogs across products.
As a read-only visibility and analytics surface, the coverage is remarkably broad across ZIA, ZPA, ZDX, ZMS, ZCELL, ZTW, ZEASM, and ZINS. But the complete absence of create/update/delete operations means any configuration or remediation workflow dead-ends immediately, which is a notable gap for a server named after a management platform.