VMware-MCP
Related Servers
Alternatives to VMware-MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceMCP server for VMware vSphere infrastructure management, enabling VM operations, monitoring, and network discovery.171MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for VMware vSphere/vCenter operations, enabling natural language control of VMs, hosts, and infrastructure.Apache 2.0
- AlicenseAqualityAmaintenanceMCP server for managing VMware vCenter (vSphere 7/8) with 39 tools covering VMs, clusters, and ESXi hosts. Supports direct and jump host deployment modes.20MIT
- AlicenseNot gradedqualityBmaintenanceMCP server that provides AI agents with comprehensive access to VMware vSphere operations, including VM management, monitoring, and vSAN read-only monitoring, through a secure Docker environment.Apache 2.0
- FlicenseNot gradedqualityCmaintenanceA comprehensive MCP server for VMware vSphere management, enabling AI agents to perform VM operations, monitoring, snapshots, and reporting through a secure, Dockerized environment.21-
- AlicenseNot gradedqualityFmaintenanceA VMware ESXi/vCenter management server based on MCP (Machine Control Protocol), providing simple REST API interfaces for virtual machine management.64MIT
TDQS
Scored across 27 tools
Most tools target distinct resources and actions, but vsphere_list_running_tasks overlaps with vsphere_list_tasks when filtered by state, creating some ambiguity. Overall, boundaries are clear and well-documented.
All tools follow a consistent vsphere_<verb>_<noun> pattern using lowercase snake_case. Verbs like list, get, create, delete, and change are used predictably across the set.
With 27 tools, the count exceeds the 25-tool threshold for 'too many' and feels heavy. While each tool addresses a specific vSphere concern, the inclusion of overlapping task-listing tools adds unnecessary bulk.
The tool set covers the core vSphere lifecycle: inventory queries, VM management (clone, reconfigure, migrate, delete, power), snapshots, tasks, events, alarms, and performance. Minor gaps like having no direct datastore/cluster creation are acceptable and don't block common workflows.