vsphere-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| vsphere_clear_credentialsB | Clear stored vSphere credentials for a domain. Args: hostname: vSphere hostname (e.g., vcenter.domain.local) |
| list_vmsA | List all virtual machines with basic information. Args: hostname: vSphere hostname (e.g., vcenter.domain.local) |
| get_vm_detailsA | Get detailed information about a specific virtual machine. Args: hostname: vSphere hostname (e.g., vcenter.domain.local) vm_id: Virtual machine ID or name |
| power_on_vmA | Power on a virtual machine. Args: hostname: vSphere hostname (e.g., vcenter.domain.local) vm_id: Virtual machine ID |
| power_off_vmC | Power off a virtual machine. Args: hostname: vSphere hostname (e.g., vcenter.domain.local) vm_id: Virtual machine ID |
| list_hostsA | List all ESXi hosts. Args: hostname: vSphere hostname (e.g., vcenter.domain.local) |
| get_host_detailsB | Get detailed information about an ESXi host. Args: hostname: vSphere hostname (e.g., vcenter.domain.local) host_id: ESXi host ID |
| list_datacentersB | List all datacenters. Args: hostname: vSphere hostname (e.g., vcenter.domain.local) |
| get_datacenter_detailsB | Get detailed information about a datacenter. Args: hostname: vSphere hostname (e.g., vcenter.domain.local) datacenter_id: Datacenter ID |
| list_datastoresB | List all datastores with capacity information. Args: hostname: vSphere hostname (e.g., vcenter.domain.local) |
| get_datastore_detailsC | Get detailed information about a datastore. Args: hostname: vSphere hostname (e.g., vcenter.domain.local) datastore_id: Datastore ID |
| list_foldersA | List folders by type. Args: hostname: vSphere hostname (e.g., vcenter.domain.local) folder_type: Folder type (VIRTUAL_MACHINE, HOST, DATACENTER, DATASTORE, NETWORK) |
| get_folder_detailsA | Get detailed information about a folder. Args: hostname: vSphere hostname (e.g., vcenter.domain.local) folder_id: Folder ID |
| list_networksA | List all networks with VLAN information. Args: hostname: vSphere hostname (e.g., vcenter.domain.local) |
| get_network_detailsB | Get detailed information about a network. Args: hostname: vSphere hostname (e.g., vcenter.domain.local) network_id: Network ID |
| get_vlan_infoA | Get information about a VLAN by name or VLAN ID. Args: hostname: vSphere hostname (e.g., vcenter.domain.local) vlan_query: VLAN name (e.g., v1306-MEL03-Secure-Management) or VLAN ID (e.g., 1306) |
| list_vlansB | Extract and list VLAN information from network names. Args: hostname: vSphere hostname (e.g., vcenter.domain.local) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 17 tools
Each tool targets a specific entity type and action (list vs get details vs power). There is no overlap; every tool has a clear, distinct purpose.
Most tools follow a consistent 'list_<entity>' and 'get_<entity>_details' pattern. Minor deviations: 'get_vlan_info' instead of 'get_vlan_details', and 'vsphere_clear_credentials' uses a different verb prefix.
17 tools is well-scoped for a vSphere management server, covering the main entities and basic actions without being overwhelming or too sparse.
The set covers listing and getting details for core entities, plus power control for VMs. However, it lacks create/update/delete operations and more advanced VM actions (clone, snapshot, etc.), leaving notable gaps for full lifecycle management.