ESXi MCP
Related Servers
Alternatives to ESXi MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables managing VMs, running guest operations, transferring files, and controlling headless consoles via vmrun, REST, and VNC/RFB through 93 tools.MIT
- AlicenseAqualityBmaintenanceEnables AI-assisted management of vCenter Server and standalone ESXi hosts, including lifecycle, deployment, guest operations, cluster management, datastore browsing, alarms, and investigations through natural language.60MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants such as Claude, Gemini, and GPT to connect directly to VMware ESXi and vCenter hosts over stdio JSON-RPC. Provides full virtual machine lifecycle management (create, clone, delete, power on/off) plus real-time CPU, memory, storage, and network performance monitoring, with API key authentication and SSL/TLS support.MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to manage VMware vSphere infrastructure through 55 typed tools built on the govc CLI. It supports comprehensive operations including VM lifecycle management, snapshot control, datastore navigation, and networking configuration.5-
- AlicenseCqualityBmaintenanceEnables agents to control local VMware Player/Workstation and ESXi/vCenter virtual machines, including power lifecycle, snapshots, cloning, file transfer, guest command/process execution, console screenshots, and keyboard/mouse input.59MIT
- AlicenseNot gradedqualityDmaintenanceEnables comprehensive management of Proxmox Virtual Environment through 35 tools for VMs, containers, storage, backups, snapshots, and cluster operations via the Proxmox VE API.22 npm22MIT
TDQS
Scored across 63 tools
Most tools are named for a distinct domain (firewall, license, time, snapshots), but there is real overlap between the generic catch-alls (esxi_api_get, esxi_api_invoke, esxi_resource_get) and the specialized *_manage tools, plus four or more file-transfer paths (datastore_transfer, api_transfer, transfer_start/stage_upload, guest_files upload_url/download_url). Descriptions provide guidance ('managers/inventory → schema/get → dry_run'), which helps, but an agent can still reasonably misselect between the generic and domain-specific layers.
All names share the esxi_ prefix and snake_case, but the verb/noun ordering is inconsistent: verb_noun (esxi_list_vms, esxi_create_snapshot), noun_verb (esxi_transfer_start, esxi_stage_upload), noun-only (esxi_inventory, esxi_capabilities, esxi_managers), and bare verbs (esxi_shell, esxi_esxcli). Readable overall, but the mixed conventions reduce predictability.
63 tools is far above the practical range for reliable tool selection, and several clusters (transfer, API access, plans) could be consolidated. The breadth of ESXi management justifies many tools, but the count still creates a heavy selection surface with substantial redundancy.
The surface covers VM lifecycle (create/configure/power/delete/register/hardware), snapshots, datastores, networks, storage, services, firewall, accounts, permissions, license, time, PCI, certificates, patching, guest processes/files, OVF import/export, and raw esxcli/shell access. Only niche operations like VM clone/migrate are explicitly excluded, so coverage is effectively complete for standalone ESXi management.