zw008/VMware-AIops

> **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 | 中文
AI-powered VMware vCenter/ESXi VM lifecycle and deployment tool — 61 tools.
> **Companion skills** handle everything else:
>
> | Skill | Scope | Install |
> |-------|-------|---------|
> | **vmware-monitor** | Read-only: inventory, health, alarms, events, metrics | uv tool install vmware-monitor |
> | **vmware-storage** | Datastores, iSCSI, vSAN management | uv tool install vmware-storage |
> | **vmware-vks** | Tanzu Namespaces, TKC cluster lifecycle | uv tool install vmware-vks |
>
> **Need read-only monitoring only?** Use VMware-Monitor — zero destructive code in the codebase.
Upgrading to 2.0
2.0 renames 38 of its MCP tools so every name starts with a verb (e.g. cluster_add_host → add_cluster_host, cluster_configure → configure_cluster, cluster_create → create_cluster). 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 (but not the action words in saved plan
files — cluster_add_host, storage_rescan and the like are plan actions, not tool names, and keep their spelling) — 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 Investigation Reports (read-only)
Triage → investigate → act, all in one conversation. Five opinionated read-only reports **aggregate and correlate server-side** and hand back a high-signal result (never raw inventory), so you can decide *where to look* before changing anything. Each renders a **self-contained offline HTML snapshot** with --html (no external assets; drill-down detail collapses in native , zero JavaScript). All delegate to the vmware-monitor library using AIops's own vCenter connection.
| Question | Command | What it correlates |
|----------|---------|--------------------|
| **"What needs attention now?"** across all vCenters | vmware-aiops attention | Every vCenter merged into one globally-ranked issue list; unreachable targets degrade gracefully |
| **"Is anything on fire?"** across all clusters | vmware-aiops summary | Every cluster's hosts + VM power + live CPU/mem + alarms → ranked top-N issues + per-cluster status |
| **"What's happening around this VM?"** | vmware-aiops investigate vm | VM state + host + cluster + backing datastores + snapshots + alarms + performance + a merged event timeline |
| **"What's happening around this host?"** | vmware-aiops investigate host | Host state + cluster + the VMs it runs + mounted datastores + alarms + performance + correlated timeline |
| **"What's happening around this datastore?"** | vmware-aiops investigate datastore | Capacity/free + mounting hosts + VMs it backs + alarms + correlated timeline |
Via MCP these are the tools get_cluster_health_summary, get_cross_vcenter_attention, investigate_vm, investigate_host, investigate_datastore. (Requires vmware-monitor installed.)
Quick Install (Recommended)
Works with Claude Code, Cursor, Codex, Gemini CLI, Trae, and 30+ AI agents:
PyPI Install (No GitHub Access Required)
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:
For a **truly air-gapped host**, build the wheels on a connected machine and copy
them over — the target then needs no network:
---
Why this over other VMware MCP servers
Most open-source VMware MCP servers (e.g. bright8192/esxi-mcp-server,
giuliolibrando/vmware-vsphere-mcp-server) are **single-vCenter VM wrappers**:
list/power/snapshot a VM, basic monitoring, a confirm=True flag. They explicitly
do not cover networking, storage, Kubernetes, ops analytics, load balancing, or