VMware vSphere MCP Server is an MCP server that connects AI assistants to VMware vCenter Server REST APIs, exposing enterprise virtualization management tools directly to language models. It is designed for system administrators, DevOps teams, and cloud engineers who manage VMware vSphere infrastructure and want to inspect or operate environments using natural language. The server enables users to list virtual machines, check power states, power on, power off, or restart VMs, and retrieve detailed hardware and network configurations. It also allows operators to inspect ESXi hosts, datastores, networks, and clusters, as well as take and manage VM snapshots. Additionally, the integration provides performance monitoring tools to identify VMs with high CPU or memory utilization, review vSphere event logs, and inspect active alarms. To safeguard production systems, destructive actions like virtual machine deletion or resource modification require explicit confirmation flags.
Category: Cloud & Infrastructure
Tags: cloud, infrastructure, virtualization, vmware, vsphere
Visit Vmware Vsphere Mcp Server
cp env.example .env. 4. Edit .env to configure your connection credentials: set VCENTER_HOST, VCENTER_USER, VCENTER_PASSWORD, and connection options like INSECURE=True alongside SERVER_HOST and SERVER_PORT. 5. Start the service with Docker Compose: docker compose up -d. 6. In your MCP client configuration (such as anythingllm_mcp_servers.json), register the streamable endpoint pointing to http://vsphere-mcp-server:8000/mcp.Part of MCP Servers
VMware vSphere MCP Server is a Model Context Protocol server that interfaces with VMware vCenter Server. It converts vSphere infrastructure operations into standard MCP tools, allowing AI agents to manage virtual machines, review ESXi hosts, inspect storage, and execute administrative actions.
You install the server using Docker and Docker Compose. After cloning the repository, configure your vCenter host and credentials in a local .env file, then run docker compose up -d to launch the HTTP MCP server on port 8000.
Destructive actions such as deleting virtual machines, modifying allocated compute resources, or forcing power off require an explicit confirm parameter set to true. Initial calls without confirmation return a warning prompt to prevent accidental changes.
The server exposes a streamable MCP endpoint over HTTP at port 8000. It is documented for use with AnythingLLM through its server JSON configuration file and can work with any MCP client supporting remote or streamable HTTP MCP connections.