# zw008/VMware-Harden [Health: Active]

**Category:** 🔒 Security  
**Repository:** https://github.com/zw008/VMware-Harden  
**GitHub Stars:** 4  
**Views:** 4  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/zw008-vmware-harden

## Description
VMware vSphere compliance and hardening — read-only baseline scanning plus drift detection across CIS, vSphere SCG, China DJCP 2.0, and PCI-DSS frameworks. 6 read-only tools with LLM-powered remediation suggestions (apply-side gated through vmware-pilot approval workflow).

## Claude Desktop Quick Installation
No generated config for this server: it installs through its own setup steps.

The project's own setup steps (from https://github.com/zw008/VMware-Harden), copied verbatim. Run them in order; they are not an mcpServers config.

1. Install:

```sh
uv tool install "vmware-harden[collectors]"
```

2. Install:

```sh
pip install --no-index --find-links dist vmware-harden
```

## Documentation

## What zw008/VMware-Harden MCP server does

zw008/VMware-Harden MCP server evaluates VMware infrastructure against security, compliance, and vulnerability baselines. It connects to vSphere and NSX data collected through the related VMware skill family, then compares those observations with rules covering host, virtual machine, datastore, distributed firewall, and vCenter-related checks.

The package includes baselines for CIS ESXi, VMware vSphere Security Configuration Guides, China DJCP 2.0 Level 3, PCI-DSS 4.0, EU NIS2, BSI IT-Grundschutz, and a vSphere 9 STIG-aligned subset. An offline VMSA advisory catalog checks ESXi and vCenter builds against known VMware security advisories. The catalog can identify affected or fixed builds, but a clean result only covers advisories present when that catalog was assembled.

## How it works

All eight MCP tools are read-only against managed vSphere and NSX infrastructure. A scan writes observations to the local twin database at `~/.vmware-harden/twin.duckdb`; it does not modify VMware resources. Agents can use the returned findings, coverage information, and drift data to distinguish failed checks from checks that could not be evaluated.

Coverage is important when interpreting results. A rule may remain unevaluated if no collector supplies the attribute it requires. A rule can also be unknown for an individual host when the host is unreachable, the scanning account lacks permission, or the setting is unavailable. Consequently, zero violations does not by itself establish compliance.

Remediation advice is generated separately and can use Anthropic's API when `ANTHROPIC_API_KEY` is available. Without that key, the command falls back to a mock advisor. The server does not apply these recommendations; write operations are deferred to vmware-pilot, where approval and audit controls are available.

## Setup and configuration

Install the collectors extra when scans need to read inventory:

```bash
uv tool install "vmware-harden[collectors]"
```

For reporting against an existing twin database, the base package is sufficient:

```bash
uv tool install vmware-harden
```

The command-line interface can list baselines, scan a named vCenter target, produce reports, inspect drift, generate advice, and start a local web dashboard. A typical scan selects a target and baseline, such as `cis-vmware-esxi-8.0-subset` or `dengbao-2.0-level3-vmware`. Source installations use the PEP 517 build system; offline deployments can build wheels on a connected machine and install them with `pip --no-index`.

## Limitations and notes

The server is community-maintained and is not affiliated with, endorsed by, or sponsored by VMware or Broadcom. Its findings depend on the data available from the collectors and the privileges and reachability of the scanning account. Baseline coverage therefore varies by rule and node.

The VMSA catalog is offline and has a defined catalog date. Advisories published afterward are outside its results, and unknown build or product mappings are not treated as passes. The vSphere 9 STIG-aligned baseline is experimental and has been collector-verified on ESXi 8.0.3 rather than run against 9.x environments.

_Full upstream README: https://allmcps.com/mcp/zw008-vmware-harden/readme_