VMware vSphere storage management with 11 MCP tools: datastores, iSCSI, vSAN.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent β or use 1-click editor setup below.
π‘ Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
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.
VMware vSphere storage management: datastores, iSCSI, vSAN β 12 MCP tools, domain-focused and lightweight.
Split from vmware-aiops for lighter context and local model compatibility.
| Skill | Scope | Tools | Install |
|---|---|---|---|
| vmware-aiops β entry point | VM lifecycle, deployment, guest ops, clusters | 49 | uv tool install vmware-aiops |
| vmware-monitor | Read-only monitoring, alarms, events, VM info | 27 | uv tool install vmware-monitor |
| vmware-vks | Tanzu Namespaces, TKC cluster lifecycle | 20 | uv tool install vmware-vks |
| vmware-nsx | NSX networking: segments, gateways, NAT, IPAM | 33 | uv tool install vmware-nsx-mgmt |
| vmware-nsx-security | DFW microsegmentation, security groups, Traceflow | 21 | uv tool install vmware-nsx-security |
| vmware-aria | Aria Ops metrics, alerts, capacity planning | 28 | uv tool install vmware-aria |
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:
| Category | Tools | Type |
|---|---|---|
| Datastore | list_all_datastores, browse_datastore, scan_datastore_images, list_cached_images | Read |
| iSCSI | storage_iscsi_enable, storage_iscsi_status, storage_iscsi_add_target, storage_iscsi_remove_target, storage_rescan | Read/Write |
| vSAN | vsan_health, vsan_capacity | Read |
The patterns/ directory hosts L5 auto-remediation candidate patterns from the Enterprise Harness Engineering framework. The first PoC pattern, patterns/iscsi-target-stale-rescan.yaml, describes an iSCSI HBA rescan as a low-risk, reversible, repeatable operation. The pattern schema is documented here only β runtime enforcement is not yet wired up, so this is a reference design, not production auto-remediation.
vmware-storage iscsi enable esxi-01vmware-storage iscsi add-target esxi-01 10.0.0.100vmware-storage iscsi status esxi-01The add-target command automatically rescans storage. Use --dry-run to preview any write command first.
vmware-storage datastore listvmware-storage datastore scan-images datastore01vmware-storage datastore browse datastore01 --pattern "*.iso"vmware-storage vsan health Cluster-Prodvmware-storage vsan capacity Cluster-Prodvmware-monitor for alarms and eventsAfter uv tool install vmware-storage, start the MCP server with one command (v1.5.15+):
Add to your AI agent's MCP config:
Behind a corporate TLS proxy? uvx may fail with
invalid peer certificate: UnknownIssuer. Use the recommendedvmware-storage mcpform above (no network needed), or setUV_NATIVE_TLS=true.
vmware-aiops has 49 MCP tools β too heavy for local LLMs (7B-14B). By splitting storage into its own skill:
Python: 3.10+ (since v1.5.27 β previously 3.11+). Tested on 3.10 / 3.11 / 3.12.
| vSphere / VCF | Support | Notes |
|---|---|---|
| VCF 9.1 / vSphere 9.1 | Full | Released 2026-05-12. pyVmomi+vSAN SDK <10.0 works via SOAP. |
| VCF 9.0 / vSphere 9.0 | Full | pyVmomi 8.0.3+ with bundled vSAN SDK connects to vSphere 9. |
| 8.0 | Full | vSAN SDK built into pyVmomi 8.0.3+ |
| 7.0 | Full | All storage APIs work |
| 6.7 | Compatible | iSCSI + datastore features work; vSAN limited |
| Feature | Description |
|---|---|
| Read-heavy | 8/12 tools are read-only |
| Input validation | IP addresses and ports validated before iSCSI operations |
| Audit logging | All operations logged to ~/.vmware-storage/audit.log |
| No VM operations | Cannot create, delete, or modify VMs |
| Credential safety | Passwords only from environment variables, never config files |
| Problem | Cause & Fix |
|---|---|
| iSCSI enable fails with "already enabled" | Not an error β adapter is already active. Run iscsi status to see configured targets. |
| "Datastore not found" when browsing | Datastore names are case-sensitive. Run datastore list to get the exact name. |
vsan_health returns overall_health: null | null = not asked (see health_not_queried_reason), never a measurement; a string is always vSAN's own answer, including its own "unknown". Usual cause: connected to standalone ESXi, but the health service runs in vCenter. |
| Rescan doesn't discover new LUNs | Wait 15-30 seconds after adding targets, then rescan again. Verify target IP is reachable from ESXi. |
| "Password not found" error | Variable names follow VMWARE_<TARGET_UPPER>_PASSWORD (hyphens β underscores). Check ~/.vmware-storage/.env. |
| Connection timeout to vCenter | Use vmware-storage doctor --skip-auth to bypass auth checks on high-latency networks. |
| "Datastore browse did not finish within Ns" | The datastore is very large or busy. Narrow the search with a sub-path and a specific pattern (e.g. datastore browse ds01 --path templates --pattern "*.ova") instead of browsing the root β do not just retry the same broad browse. |
No reviews yet β be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/vmware-storage)<a href="https://allmcps.com/mcp/vmware-storage"><img src="https://allmcps.com/api/badge/vmware-storage?style=directory" alt="VMware Storage on AllMCPs" /></a>