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.
Description from the maker (original English)
VMware AVI (NSX ALB) load balancer plus AKO Kubernetes ops — 29 MCP tools.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
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-aviPaste 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.
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.
Runs on your computer; the tool list appears in your AI app after you install it.
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
The registry name was verified with the GitHub account zw008, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
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.
The registry does not list a required key, though some servers ask you to sign in on first use.
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).
The GitHub repo last changed –, and the latest version (1.8.8) reached the registry 4 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
In the same category: GitHub, Desktop Commander, Cloudflare MCP
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’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.
MCP server for terminal commands, file operations, and process management
Cloudflare MCP servers
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.
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|
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.
# Via uv (recommended)
uv tool install vmware-avi
pip install vmware-avi
pip install vmware-avi -i https://pypi.tuna.tsinghua.edu.cn/simple
vmware-avi doctor
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 .
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)
pip install --no-index --find-links dist vmware-avi
| Category | Tools | Count |
|---|---|---|
| Virtual Service | list, status, enable/disable | 3 |
| Pool Member | pool discovery, member list, enable/disable member (drain/restore traffic) | 4 |
| SSL Certificate | list, expiry check | 2 |
| Analytics | VS metrics overview, request error logs | 2 |
| Service Engine | list, health check | 2 |
| AKO Pod Ops | status, logs, restart, version info | 4 |
| AKO Config | values.yaml view, Helm diff, Helm upgrade | 3 |
| Ingress Diagnostics | annotation validation, VS mapping, error diagnosis, fix recommendation | 4 |
| Sync Diagnostics | K8s-Controller comparison, inconsistency list, force resync | 3 |
| Multi-cluster | cluster list, cross-cluster AKO overview, AMKO status | 3 |
| Scenario | Recommended | Why |
|---|---|---|
| Local/small models (Ollama, Qwen) | CLI | ~2K tokens vs ~8K for MCP |
| Cloud models (Claude, GPT-4o) | Either | MCP gives structured JSON I/O |
| Automated pipelines | MCP | Type-safe parameters, structured output |
| AKO troubleshooting | CLI | Interactive log tailing, Helm diff output |
Rule of thumb: Use CLI for cost efficiency and small models. Use MCP for structured automation with large models.
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
mkdir -p ~/.vmware-avi
vmware-avi init # generates config.yaml and .env templates chmod 600 ~/.vmware-avi/.env
controllers:
default_controller: prod-avi
ako: kubeconfig: ~/.kube/config default_context: "" namespace: avi-system
Create ~/.vmware-avi/.env:
# AVI Controller passwords
PROD_AVI_PASSWORD=your-password-here
Password environment variable naming convention:
{CONTROLLER_NAME_UPPER}_PASSWORD
vmware-avi doctor # checks Controller connectivity + kubeconfig + avisdk
# List all virtual services
vmware-avi vs list [--controller prod-avi]
vmware-avi vs status my-webapp-vs
vmware-avi vs enable my-webapp-vs vmware-avi vs disable my-webapp-vs
# List pool members and health status
vmware-avi pool members my-pool
vmware-avi pool disable my-pool 10.1.1.5
vmware-avi pool enable my-pool 10.1.1.5
# List all certificates
vmware-avi ssl list
vmware-avi ssl expiry --days 30
# VS analytics: throughput, latency, error rates
vmware-avi analytics my-webapp-vs
vmware-avi logs my-webapp-vs --since 1h
# Name, mgmt IP, operational status, SE group — status sourced from the
vmware-avi se list
vmware-avi se health
# Check AKO pod status
vmware-avi ako status [--context my-k8s-context]
vmware-avi ako logs [--tail 100] [--since 30m]
vmware-avi ako restart
vmware-avi ako version
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
vmware-avi ako config diff
vmware-avi ako config upgrade
# Validate Ingress annotations
vmware-avi ako ingress check
vmware-avi ako ingress map
vmware-avi ako ingress diagnose
# Check K8s-Controller sync status
vmware-avi ako sync status
vmware-avi ako sync diff
vmware-avi ako sync force
# List every kube-context and whether AKO runs there
vmware-avi ako clusters
vmware-avi ako cluster-overview
vmware-avi ako amko status
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
VMWARE_AVI_CONFIG=/path/to/config.yaml vmware-avi mcp
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
vmware-avi-mcp
Behind a corporate TLS proxy? uvx may fail with
invalid peer certificate: UnknownIssuer.
Use the recommended
vmware-avi mcpform above (no network needed), or setUV_NATIVE_TLS=true.
| Category | Tools |
|---|---|
| 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