Vcenter MCP Server

Vcenter MCP MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Lookups accept either a display name or a moref ID (e.g. vm-42) — the moref path skips the inventory scan and is faster on large environments.

What you get

• List VMs on a vCenter datacenter (grouped by host) or on a standalone ESXi host
• Create a VM (network-boot first; thin or thick provisioning; nested-virt option for ESXi targets)
• Power VMs on and off
• Delete VMs (powers off first if running, then destroys from disk)

What the assistant can call

Once Vcenter MCP is connected, these are the calls the assistant has available:

• list_vms — List VMs on a target using a single PropertyCollector RPC (no per-VM round trips)
• create_vm — The create_vm tool exposed by this server
• power_on_vm — The power_on_vm tool exposed by this server
• power_off_vm — Hard power off a VM by display name or moref ID (e.g. vm-42)
• delete_vm — Permanently delete a VM (powers off first if running, then destroys from disk)

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Configuration and credentials

• Python 3.10 or newer - A vCenter Server or standalone ESXi host you can reach over the network - A vSphere account with the privileges needed for whatever you plan to do (read-only is enough for list_vms; create / delete need the corresponding VM and resource-pool privileges)

Choosing this one

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Vcenter MCP's toolset — list_vms, create_vm, power_on_vm and 2 more — is a fair guide to whether it matches your workflow. It is maintained by michaelrice; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the vcenter mcp mcp server does with a few real requests.