VMware AVI

Install

Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/vmware-skills-vmware-avi

About

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list, install config and code. Checked Oct 25, 2026.

Tools

22 read · 2 write · 4 delete

Secrets

None asked for

Install scripts

None found

Runs as

Python package

Tools (28)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

• check_ako_ingressread-only

  [READ] Validate every Ingress in one namespace: IngressClass and TLS secret references that would stop AKO creating a Virtual Service. Returns name, IngressClass, issues and OK/ISSUES per Ingress. Run list_ako_ingresses first for namespace names; use diagnose_ako_ingress instead for one named Ingress. Covers one namespace only, and TLS checks are skipped when its secrets cannot be listed. Args: namespace: K8s namespace to check. context: K8s context name (optional).

• check_ssl_cert_expiryread-only

  [READ] Check which SSL certificates expire within N days (default 30). Returns name, expiry date and days remaining, soonest first. Use this instead of list_ssl_certs when you only want certificates near expiry. Expired certs are included, with negative days remaining. Certificates whose expiry could not be read are counted and named separately — they are unknown, not "not expiring". Args: days: Report certs expiring within this many days (default 30).

• diagnose_ako_ingressread-only

  [READ] Diagnose why one Ingress has no corresponding AVI Virtual Service. Validates IngressClass ('avi'/'avi-lb'), TLS secrets and backend Services. Returns annotations, a numbered issue list and kubectl fixes. "Not found"/"missing" is reported only for a 404; any other error reading the Ingress, a TLS secret or a backend Service says it could not be read (with the HTTP status). Use list_ako_ingresses first to find Ingresses lacking a VS. Checks configuration only; when it is clean, try get_ako_logs and get_ako_sync_status. Args: name: Exact Ingress resource name. namespace: Namespac…

• diff_ako_configread-only

  [READ] Pending Helm value changes that have not been applied yet. Returns helm's diff output; empty means nothing would change. Credential values in it read `<redacted>` — that is this skill blanking them, not the configured value. Use this before upgrade_ako_config — it runs the same command, so the preview is real. Note: with chart_version empty the registry's moving latest is resolved, so two runs can differ with no local change; read get_ako_version and pass it to both. Args: chart_version: Pin the chart, e.g. "1.11.1". Empty = registry latest.

• diff_ako_syncread-only

  [READ] List Ingresses with no matching Virtual Service or pool on the Controller. Returns Type, namespace/name and Status per suspect Ingress. Use when get_ako_sync_status reports a mismatch; force_ako_sync reconciles. Shard-mode Ingresses are matched heuristically against AKO pool names, so confirm a 'Missing' result with list_lb_pools before acting. Args: context: K8s context name (optional).

• disable_lb_pool_membercan change or delete data

  [WRITE] Disable a pool member with graceful drain — existing connections complete, no new traffic. Without confirm=True this only previews: it returns blast_radius (pool name and uuid, the member's IP/port/state, and how many members are enabled before and after) and changes nothing. Show that to the user and get their explicit decision. Do not set confirm=True on your own because the user asked earlier: they have not seen what it changes yet. An already disabled member returns action "noop". Refused with confirm=True: the pool's only enabled member (the pool would serve nothing — enable ano…

• enable_lb_pool_member

  [WRITE] Enable a pool member so it receives traffic again. Returns a one-line confirmation. Use list_lb_pool_members first to verify the server IP. The server must already belong to the pool — this adds nothing. Args: pool: Exact pool name as shown by list_lb_pools — matched literally, not fuzzily, and an unknown name is refused rather than ignored. Pools are often named differently from the Virtual Services that use them, so do not infer it from a VS name. server: Server IP address.

• force_ako_synccan change or delete data

  [WRITE] Force AKO to resync all K8s resources with the AVI Controller. The resync restarts the AKO pod so it rebuilds every Virtual Service, pool and VS-VIP from the cluster's current resources. Without confirm=True this only previews: it returns blast_radius (context, namespace, the pod's name, uid and phase, and the Ingresses it re-programs) and changes nothing. Show that to the user and get their explicit decision. Do not set confirm=True on your own because the user asked earlier: they have not seen what it changes yet. Refused with confirm=True: a pod already terminating, and a pod or I…

• get_ako_amko_statusread-only

  [READ] AMKO (AVI Multi-Cluster Kubernetes Operator) GSLB status. Returns raw kubectl output: the AMKO pods in avi-system, then the GSLBConfig YAML if one exists. 'AMKO not deployed' means kubectl answered and found no AMKO pods; if kubectl cannot read the cluster the call fails with its reason. A GSLBConfig that cannot be read is reported, not skipped. Use this only for multi-cluster GSLB questions — for single-cluster AKO health use get_ako_status instead. Always reads the current kubectl context; see list_ako_clusters.

• get_ako_configread-only

  [READ] The AKO Helm release's values — controller IP, cloud name, network settings, feature flags. Returns YAML as helm reports it. Use this first to read the live config; use diff_ako_config instead to see what an upgrade would change. Only values supplied at install time appear; chart defaults do not.

• get_ako_logsread-only

  [READ] AKO pod logs — Ingress creation failures, sync errors, Controller connectivity. Returns raw log text, not a table. Use when get_ako_status shows the pod unhealthy or diff_ako_sync reports a missing Ingress. Only the running container's logs are returned. Args: tail: Number of log lines (default 100). since: Narrows the window, e.g. '30m', '1h'. context: K8s context (optional, uses current).

• get_ako_statusread-only

  [READ] Check AKO (AVI Kubernetes Operator) pod status in Kubernetes. Returns pod name, phase, ready flag, restart count and namespace. First step for Ingress or LoadBalancer issues in Tanzu/K8s; follow with get_ako_logs when it is not Running. Looks in one context's AKO namespace only — run list_ako_clusters if not found. Args: context: K8s context name (optional, uses current context).

• get_ako_sync_statusread-only

  [READ] Compare the number of K8s Ingresses with the number of AVI Virtual Services. Returns both counts and a match/mismatch verdict. Use this first as a cheap check, then diff_ako_sync for which objects differ. A count comparison only — in AKO shard mode many Ingresses share one VS, so a mismatch does not by itself mean trouble. Args: context: K8s context name (optional).

• get_ako_versionread-only

  [READ] AKO version running in a cluster, read from the pod's image tag. Returns the pod name and an Image/Version pair per container. Use it to check compatibility with the Controller, and before diff_ako_config or upgrade_ako_config so both target the installed chart. The tag is the only source, so 'latest' reports 'latest', not a number. Args: context: K8s context name (optional).

• get_service_engine_healthread-only

  [READ] Health of every Service Engine — operational status and VS counts. Returns name, operational state and the number of VSes placed on each SE. Use when VS health degrades to check if the issue is at the SE level; list_service_engines gives the management IP and SE Group, get_virtual_service_status the affected VS. An SE hosting no VS reports 0, not an error.

Compare and alternatives

Featured in

• Best MCP servers for Kubernetes

Signals

Stars

2

Forks

1

Open issues

0

Weekly downloads

283

Last commit

Oct 24, 2026 (4 days ago)

Last release

Oct 16, 2026 (12 days ago)

Last package publish

Oct 16, 2026 (12 days ago)

From GitHub (fetched Oct 24, 2026) and the package registry.

Details

Registry name

io.github.vmware-skills/vmware-avi

Version

2.4.0

Auth

No auth

Packages

pypi vmware-avi

License

MIT

Repository

github.com/vmware-skills/VMware-AVI

First seen

Oct 24, 2026

Last checked

Oct 24, 2026

Source

Official MCP Registrygithub-graphql