Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

VMware AVI

by zw008version 1.8.8i★ –iRuns on your computer
Registry nameio.github.zw008/vmware-avi

Install

Overview

Description from the maker (original English)

VMware AVI (NSX ALB) load balancer plus AKO Kubernetes ops — 29 MCP tools.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Developer tools

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • The registry lists no key to fill in.

You need

  • PyPIPython’s uv installed (for the uvx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "vmware-avi": {
      "command": "uvx",
      "args": [
        "vmware-avi"
      ]
    }
  }
}

Run this in your terminal

claude mcp add vmware-avi -- uvx vmware-avi

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "vmware-avi": {
      "command": "uvx",
      "args": [
        "vmware-avi"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "vmware-avi": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "vmware-avi"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account zw008, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Developer toolsi

  • More stars than 0% of the other 1395 servers in this category
  • Published to the registry more recently than 34% of the other 1395 servers in this category
  • Basic checks equal to or better than 100% of the other 1395 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is VMware AVI safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.8.8) reached the registry 4 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: GitHub, Desktop Commander, Cloudflare MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

GitHub

by github

GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.

Computer or cloud★ 34,245MITUpdated 4 days ago
Install

Desktop Commander

by wonderwhy-er

MCP server for terminal commands, file operations, and process management

Runs on your computer★ 10,225MITUpdated 16 days ago
Install

Cloudflare MCP

by cloudflare

Cloudflare MCP servers

Runs in the cloud★ 4,446Apache-2.0Updated 14 months ago
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

VMware AVI

For a read-only check of this skill with your model and agent host, use the shared model-fit self-test in the marketplace root.

Author: Wei Zhou, VMware by Broadcom — wei-wz.zhou@broadcom.com

This is a community-driven project by a VMware engineer, not an official VMware product.

For official VMware developer tools see developer.broadcom.com.

English | 中文

AVI (NSX Advanced Load Balancer) management and AKO Kubernetes operations tool — 28 tools across 10 categories.

Dual mode: Traditional AVI Controller management + AKO K8s operations in one skill.

Companion skills handle everything else:

| Skill | Scope | Install |

|-------|-------|---------|

| [vmware-aiops](https://github.com/vmware-skills/VMware-AIops) | VM lifecycle, deployment, guest ops, cluster | uv tool install vmware-aiops |

| [vmware-monitor](https://github.com/vmware-skills/VMware-Monitor) | Read-only: inventory, health, alarms, events | uv tool install vmware-monitor |

| [vmware-storage](https://github.com/vmware-skills/VMware-Storage) | Datastores, iSCSI, vSAN management | uv tool install vmware-storage |

| [vmware-vks](https://github.com/vmware-skills/VMware-VKS) | Tanzu Namespaces, TKC cluster lifecycle | uv tool install vmware-vks |

| [vmware-nsx](https://github.com/vmware-skills/VMware-NSX) | NSX networking: segments, gateways, NAT | uv tool install vmware-nsx-mgmt |

| [vmware-nsx-security](https://github.com/vmware-skills/VMware-NSX-Security) | DFW firewall rules, security groups | uv tool install vmware-nsx-security |

| [vmware-aria](https://github.com/vmware-skills/VMware-Aria) | Aria Ops: metrics, alerts, capacity | uv tool install vmware-aria |


Upgrading to 2.0

2.0 renames all 28 MCP tools so every name starts with a verb (e.g. ako_amko_status → get_ako_amko_status, ako_clusters → list_ako_clusters, ako_config_diff → diff_ako_config). The full old → new table is in RELEASE_NOTES.md. Nothing else changes: same tools, parameters, safety gates and CLI commands. If an agent prompt, script or ~/.vmware/rules.yaml names a tool, update it — though deny rules written with the old names keep working with vmware-policy ≥ 1.18 (vmware-audit policy lists any rule the renames widened), and vmware-pilot ≥ 1.13 translates old names in saved workflows. If an install older than 2.0 shares that rules.yaml, give it vmware-policy ≥ 1.18.2 too: it matches each rule against both the old and the new name, so one file serves both.

Quick Install

# Via uv (recommended)

uv tool install vmware-avi

Or via pip

pip install vmware-avi

China mainland mirror

pip install vmware-avi -i https://pypi.tuna.tsinghua.edu.cn/simple

Verify installation

vmware-avi doctor

Offline / Air-Gapped Install (from source)

This project uses the modern PEP 517 build system (hatchling), so there is no `setup.py` by design — that is expected, not a missing file. If you cloned the source and hit ERROR: File "setup.py" or "setup.cfg" not found ... editable mode currently requires a setuptools-based build, your pip is older than 21.3 and cannot do an *editable* (-e) install with a non-setuptools backend. Editable mode is a developer convenience, not needed to run the tool — do one of:

# From the source tree — a normal (non-editable) install builds a wheel:

pip install . # NOT pip install -e .

...or upgrade pip first, and editable works too:

pip install --upgrade pip && pip install -e .

For a truly air-gapped host, build the wheels on a connected machine and copy them over — the target then needs no network:

# On a connected machine, collect this package + its dependencies as wheels:

pip wheel . -w dist # → dist/*.whl (or: uv build, for just this package)

Copy dist/ to the air-gapped host, then install offline:

pip install --no-index --find-links dist vmware-avi


Capabilities Overview

What This Skill Does
CategoryToolsCount
Virtual Servicelist, status, enable/disable3
Pool Memberpool discovery, member list, enable/disable member (drain/restore traffic)4
SSL Certificatelist, expiry check2
AnalyticsVS metrics overview, request error logs2
Service Enginelist, health check2
AKO Pod Opsstatus, logs, restart, version info4
AKO Configvalues.yaml view, Helm diff, Helm upgrade3
Ingress Diagnosticsannotation validation, VS mapping, error diagnosis, fix recommendation4
Sync DiagnosticsK8s-Controller comparison, inconsistency list, force resync3
Multi-clustercluster list, cross-cluster AKO overview, AMKO status3
CLI vs MCP: Which Mode to Use
ScenarioRecommendedWhy
Local/small models (Ollama, Qwen)CLI~2K tokens vs ~8K for MCP
Cloud models (Claude, GPT-4o)EitherMCP gives structured JSON I/O
Automated pipelinesMCPType-safe parameters, structured output
AKO troubleshootingCLIInteractive log tailing, Helm diff output

Rule of thumb: Use CLI for cost efficiency and small models. Use MCP for structured automation with large models.

Architecture
User (Natural Language)

| AI CLI Tool (Claude Code / Gemini / Codex / Cursor / Trae) | reads SKILL.md | vmware-avi CLI |--- avisdk (AVI REST API) ---> AVI Controller ---> Virtual Services / Pools / SEs |--- kubectl / kubernetes ---> K8s Cluster ---> AKO Pods / Ingress / Services


Configuration

Step 1: Create Config Directory
mkdir -p ~/.vmware-avi

vmware-avi init # generates config.yaml and .env templates chmod 600 ~/.vmware-avi/.env

Step 2: Edit config.yaml
controllers:
  • name: prod-avi host: avi-controller.example.com username: admin api_version: "22.1.4" tenant: admin port: 443 verify_ssl: true

default_controller: prod-avi

ako: kubeconfig: ~/.kube/config default_context: "" namespace: avi-system

Step 3: Set Passwords

Create ~/.vmware-avi/.env:

# AVI Controller passwords

Format: {CONTROLLER_NAME_UPPER}_PASSWORD

PROD_AVI_PASSWORD=your-password-here

Password environment variable naming convention:

{CONTROLLER_NAME_UPPER}_PASSWORD

Replace hyphens with underscores, UPPERCASE

Example: controller "prod-avi" -> PROD_AVI_PASSWORD

Example: controller "staging-alb" -> STAGING_ALB_PASSWORD

Step 4: Verify
vmware-avi doctor    # checks Controller connectivity + kubeconfig + avisdk

CLI Usage

Virtual Service Management
# List all virtual services

vmware-avi vs list [--controller prod-avi]

Check status of a specific VS

vmware-avi vs status my-webapp-vs

Enable / disable a VS (disable requires double confirmation)

vmware-avi vs enable my-webapp-vs vmware-avi vs disable my-webapp-vs

Pool Member Drain / Restore
# List pool members and health status

vmware-avi pool members my-pool

Graceful drain (disable) — double confirmation required

vmware-avi pool disable my-pool 10.1.1.5

Restore traffic (enable)

vmware-avi pool enable my-pool 10.1.1.5

SSL Certificate Expiry Check
# List all certificates

vmware-avi ssl list

Check certificates expiring within 30 days

vmware-avi ssl expiry --days 30

Analytics and Error Logs
# VS analytics: throughput, latency, error rates

vmware-avi analytics my-webapp-vs

Request error logs

vmware-avi logs my-webapp-vs --since 1h

Service Engine Health
# Name, mgmt IP, operational status, SE group — status sourced from the

serviceengine-inventory endpoint (config + runtime merged)

vmware-avi se list

Per-SE operational status + connected-VS counts

vmware-avi se health

AKO Troubleshooting
# Check AKO pod status

vmware-avi ako status [--context my-k8s-context]

View AKO logs

vmware-avi ako logs [--tail 100] [--since 30m]

Restart AKO pod (double confirmation)

vmware-avi ako restart

Show AKO version

vmware-avi ako version

AKO Helm Config Management

The AKO Helm release is discovered automatically (official installs use helm install --generate-name, so the release is not named ako). Upgrades pull the official Broadcom OCI chart oci://projects.packages.broadcom.com/ako/helm-charts/ako with --reuse-values.

# View current AKO Helm values (release auto-discovered)

vmware-avi ako config show

Show pending changes (diff against the official OCI chart)

vmware-avi ako config diff

Helm upgrade (double confirmation + --dry-run default)

vmware-avi ako config upgrade

Ingress Diagnostics
# Validate Ingress annotations

vmware-avi ako ingress check

Show Ingress-to-VS mapping

vmware-avi ako ingress map

Diagnose why an Ingress has no VS

vmware-avi ako ingress diagnose

Sync Diagnostics
# Check K8s-Controller sync status

vmware-avi ako sync status

Show inconsistencies between K8s and Controller

vmware-avi ako sync diff

Force AKO resync (double confirmation)

vmware-avi ako sync force

Multi-cluster AKO
# List every kube-context and whether AKO runs there

vmware-avi ako clusters

Cross-cluster AKO status overview

vmware-avi ako cluster-overview

AMKO GSLB status

vmware-avi ako amko status


MCP Server

The MCP server exposes all 28 tools via the Model Context Protocol. Works with any MCP-compatible client.

After `uv tool install vmware-avi`, start the MCP server with one command (v1.5.15+):

# Recommended — single command, no network re-resolve

vmware-avi mcp

With custom config path

VMWARE_AVI_CONFIG=/path/to/config.yaml vmware-avi mcp

Claude Desktop Config

Add to claude_desktop_config.json:

{

"mcpServers": { "vmware-avi": { "command": "vmware-avi", "args": ["mcp"], "env": { "VMWARE_AVI_CONFIG": "~/.vmware-avi/config.yaml" } } } }

Alternative: uvx (no install) or legacy entry point

# Run without installing (requires PyPI access each launch)

uvx --from vmware-avi vmware-avi mcp

Legacy entry point (still works, kept for backward compatibility)

vmware-avi-mcp

Behind a corporate TLS proxy? uvx may fail with invalid peer certificate: UnknownIssuer.

Use the recommended vmware-avi mcp form above (no network needed), or set UV_NATIVE_TLS=true.

MCP Tools (28)
CategoryTools
Virtual Service (3)list_virtual_services, get_virtual_service_status, set_virtual_service_enabled
Pool Member (4)list_lb_pools, list_lb_pool_members, enable_lb_pool_member, disable_lb_pool_member
SSL Certificate (2)list_ssl_certs, check_ssl_cert_expiry
Analytics (2)get_virtual_service_analytics, get_virtual_service_error_logs
Service Engine (2)list_service_engines, get_service_engine_health
AKO Pod (4)get_ako_status, get_ako_logs, restart_ako, get_ako_version

| AKO Config (3) | get_ako_config, diff_ako_config, `upgr

Only the beginning is shown; read the rest in the repo

Ask PopNx