Symantec ZTNA AIops

io.github.AIops-toolsPublished by GitHub account AIops-toolsv0.1.0Updated Nov 6, 2026

Governed Symantec ZTNA operations — 40 MCP tools, read-only with audit.

VerifiedSTDIODesktop onlyCloud & InfrastructureSecurity & Monitoring

Overview

AI-generated overview

Read-only MCP server and CLI exposing 40 governed tools for inspecting Symantec ZTNA tenants, connectors, policies and audit logs.

What you can do
  • Inspect tenant and connector health, including sampled health probes and connector metrics
  • Review applications, access policies, shared objects and collections
  • Look up DNS, identities and cloud integrations
  • Search audit logs with paging cursors and truncation reporting
  • Run the same operations from a CLI that mirrors every MCP tool
When to use it
Use it when an assistant needs to answer questions about a Symantec Zero Trust Network Access deployment — tenant health, connector status, policy configuration or audit history — without making changes. It suits administrators who want read-only, auditable inspection from a chat client.
Requirements
Runs locally as a Python package (symantec-ztna-aiops) via uv or the symantec-ztna-aiops-mcp entry point. Needs a ZTNA tenant API HTTPS origin in SYMANTEC_ZTNA_URL plus SYMANTEC_ZTNA_CLIENT_ID and SYMANTEC_ZTNA_CLIENT_SECRET from a ZTNA API client. Optional: SYMANTEC_ZTNA_CA_BUNDLE, SYMANTEC_ZTNA_TIMEOUT, SYMANTEC_ZTNA_AIOPS_HOME. Network access to the tenant API is required.
Before you install
Requires a ZTNA API client ID and secret (SYMANTEC_ZTNA_CLIENT_ID, SYMANTEC_ZTNA_CLIENT_SECRET); use a least-privilege client. Read results, including tenant configuration and audit logs, are sent to the assistant and its model provider. The project is community-maintained and unaffiliated with Broadcom or Symantec, and is described as an unverified preview; no state-changing API is exposed. Search windows are capped at 30 days and connector metrics at seven days.

Installation

In SourceWeft

  1. Open Symantec ZTNA AIops in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

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.

Source: README.md at commit 848f6aa

Tools

0
SourceWeft started this package once in an isolated sandbox, without credentials, to list its tools. That failed: the server did not start.

Version history

1
  1. v0.1.0LatestNov 6, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts