Symantec ZTNA AIops
Provides governed read-only tools for Symantec Zero Trust Network Access (ZTNA), covering tenant and connector health, applications, access policies, shared objects, collections, DNS, identities, cloud integrations, and audit logs.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
Symantec ZTNA AIops
An independent MCP server, CLI and skill for Symantec Zero Trust Network Access. This preview exposes 40 governed read tools for tenant and connector health, applications, access policies, shared objects, collections, DNS, identities, cloud integrations and audit logs. It is separate from SEP, SES Cloud and on-premises EDR.
Community-maintained project. Not affiliated with or endorsed by Broadcom or Symantec; product names are their owners’ trademarks.
Setup
Set SYMANTEC_ZTNA_URL to the tenant API HTTPS origin, such as https://api.example.luminatesec.com, and provide SYMANTEC_ZTNA_CLIENT_ID and SYMANTEC_ZTNA_CLIENT_SECRET from a ZTNA API client. The URL must be an origin without a path. Optional settings are SYMANTEC_ZTNA_CA_BUNDLE, SYMANTEC_ZTNA_TIMEOUT and SYMANTEC_ZTNA_AIOPS_HOME for local governance storage. Use an API client with the least privileges needed for the reads you intend to call.
Run uv run symantec-ztna-aiops --help. The MCP entry point is symantec-ztna-aiops-mcp. CLI commands mirror all MCP tools; see the operations catalog for the full list and official API sources.
Paged endpoints return truncated, nextPage and totalReported from the documented server page metadata. Audit searches fetch one extra log to measure truncation and return the next SearchAfterValues cursor. Search windows are capped at 30 days; connector metrics at seven days. health-sample is explicitly a sample and reports partial probe failures. No state-changing API is exposed in this unverified preview.
See verification for official API evidence and the remaining live-tenant checks. Missing a common ZTNA task? Open an issue or PR with the product version and a sanitized response shape.
This server cannot be deployed
Maintenance
Related MCP Connectors
Read-only MCP access to a documented IT fleet: state, changes, posture. 15 tools.
Read-only AI coding tools for change verification, release readiness, capacity, and guidance.
Cloud cost, inventory and governance on AWS/Azure/GCP. Read-only by default, optional scoped writes
Read-only checks for DIDs, credentials, MCP servers, A2A cards and agent delegation.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables read-only access to LeanIX Multi-Tenant Management (MTM) API data through 29 tools. Supports querying accounts, workspaces, users, permissions, contracts, instances, events, technical users, domains, identity providers, custom features, and labels with filtering and pagination.13 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables read-only access to operations and telemetry data across 12 domains through 45 agent tools, including asset inventory, metrics, outages, incidents, and platform settings, with support for AWS SigV4-signed live access and a fixture-based mock mode that runs without a backend.MIT
- AlicenseAqualityBmaintenanceProvides read-only visibility into CyberQP privileged access management data, including customer and account metadata, tenant event logs, and Just-In-Time account status and policies, for AI assistants.10Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to read managed Microsoft 365 client tenants, baselines, alignment scores, policies, Secure Score, Entra users/groups/roles, and audit activity, and on explicit request run assessments and queue reports. Access is read-only apart from those two run tools, which never modify tenant policies.Apache 2.0