# bright8192/esxi-mcp-server [Health: Active]

**Category:** ☁️ Cloud Platforms  
**Repository:** https://github.com/bright8192/esxi-mcp-server  
**GitHub Stars:** 64  
**Views:** 4  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/bright8192-esxi-mcp-server

## Description
A VMware ESXi/vCenter management server based on MCP (Model Control Protocol), providing simple REST API interfaces for virtual machine management.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `uvx` (confidence: high):

```json
"mcpServers": {
  "esxi-mcp-server": {
    "command": "uvx",
    "args": ["pyvmomi"],
    "env": {
      "VCENTER_HOST": "",
      "VCENTER_USER": "",
      "VCENTER_PASSWORD": "",
      "VCENTER_DATACENTER": "",
      "VCENTER_CLUSTER": "",
      "VCENTER_DATASTORE": "",
      "VCENTER_NETWORK": "",
      "MCP_API_KEY": ""
    }
  }
}
```

**Requires environment variables:** `VCENTER_HOST`, `VCENTER_USER`, `VCENTER_PASSWORD`, `VCENTER_DATACENTER`, `VCENTER_CLUSTER`, `VCENTER_DATASTORE`, `VCENTER_NETWORK`, `MCP_API_KEY` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What bright8192/esxi-mcp-server MCP server does

The bright8192/esxi-mcp-server MCP server exposes VMware ESXi and vCenter operations through MCP-oriented interfaces. It is intended for environments where an agent or client needs to manage virtual machines without interacting directly with the VMware administration UI.

Supported lifecycle actions include creating a VM, cloning an existing VM, deleting a VM, powering a VM on or off, and listing available VMs. Creation accepts values such as the VM name, CPU count, memory, datastore, and network. Cloning uses a source VM or template name and a new VM name.

The server also provides VM performance data through a `vmstats://{vm_name}` resource interface. The documented statistics cover CPU, memory, storage, and network traffic usage.

## How it works

The bright8192/esxi-mcp-server MCP server uses Python and the VMware `pyVmomi` library to connect to an ESXi host or vCenter Server. Requests are exposed through REST-style endpoints with JSON-RPC support. SSE provides the documented real-time communication channel, including the `/sse/messages` endpoint shown for authenticated requests.

VMware connection settings identify the host, username, and password. Optional placement settings select a datacenter, cluster, datastore, and network. If these optional values are not supplied, the configuration describes automatic selection behavior: the first datacenter or cluster, the largest available datastore, and the default `VM Network`.

## Setup and configuration

Install Python 3.7 or newer and the listed dependencies: `pyvmomi`, `pyyaml`, `uvicorn`, and `mcp-core`. The documented startup command runs `server.py` with a YAML configuration file, for example `python server.py -c config.yaml`.

Configuration can be provided through YAML, JSON, or environment variables. The main connection values are `vcenter_host`, `vcenter_user`, and `vcenter_password`. Other settings control VMware object selection, certificate verification, API access, logging destination, and log verbosity. Environment variable names include `VCENTER_HOST`, `VCENTER_USER`, `VCENTER_PASSWORD`, `VCENTER_DATACENTER`, `VCENTER_CLUSTER`, `VCENTER_DATASTORE`, `VCENTER_NETWORK`, and `MCP_API_KEY`.

## Tools and capabilities

The bright8192/esxi-mcp-server MCP server documents these operational areas:

- Create, clone, delete, list, and power virtual machines.
- Monitor CPU, memory, storage, and network usage for a named VM.
- Connect to either standalone ESXi or vCenter Server.
- Exchange requests through SSE, REST-style APIs, and JSON-RPC.
- Protect privileged operations with an API key sent as a bearer token.
- Configure TLS verification behavior and application logging.

## Limitations and notes

The README identifies the project as an initial v0.0.1 release with basic VM management and monitoring functionality. It does not document a package-manager distribution, hosted endpoint, or named compatibility with Claude Desktop, Cursor, Windsurf, or Cline.

The VMware username and password are required connection settings. API key authentication is documented for privileged operations, although the configuration table marks the API key field as optional. Production guidance recommends valid SSL certificates and restricted API access. Setting `insecure: true` skips certificate verification and is presented for testing; it should be treated carefully in production.

No detailed behavior is provided for VM hardware customization beyond the creation fields shown, nor for advanced VMware operations outside the listed lifecycle and monitoring functions.

_Full upstream README: https://allmcps.com/mcp/bright8192-esxi-mcp-server/readme_