vcenter-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VCENTER_PASSWORD | No | Default vCenter password (fallback if credentials not found in OS keyring). | |
| VCENTER_USERNAME | No | Default vCenter username (fallback if credentials not found in OS keyring). | |
| VCENTER_MCP_INVENTORY | Yes | Path to the inventory.yaml file that lists vCenter instances. |
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 |
|---|---|
| get_appliance_versionC | Get appliance version information. |
| get_appliance_timeC | Get current appliance time settings. |
| list_vcentersA | List configured vCenter instances from inventory.yaml. |
| get_vcenter_inventoryC | Return configured inventory entries and guidance for using vCenter tools. |
| list_clustersB | List vCenter clusters, optionally filtered by cluster IDs or datacenter IDs. |
| get_clusterC | Get details for a specific cluster. |
| get_cluster_resource_utilization_wsC | Get cluster CPU, memory, storage, and IOPS utilization via the vSphere Web Services API. |
| get_cluster_cpu_memory_utilization_period_wsC | Get time-bound cluster CPU and memory utilization via Web Services (default 5 days). |
| get_cluster_cpu_memory_daily_rollup_wsB | Get daily rollups for cluster CPU/memory utilization via Web Services (default 5 days). |
| get_cluster_cpu_memory_utilization_window_wsC | Get cluster CPU/memory utilization for windows like '24 hours' or '4 days', optionally as per-day averages. |
| list_datacentersC | List datacenters visible in vCenter. |
| get_datacenterC | Get datacenter details. |
| list_datastoresB | List datastores with optional filters. |
| get_datastoreC | Get datastore details. |
| list_foldersC | List folders with optional filters. |
| list_hostsC | List ESXi hosts with optional filters via the vSphere Web Services API. |
| get_hostC | Get details for a specific physical ESXi host via the vSphere Web Services API. |
| list_networksC | List networks and distributed port groups. |
| list_resource_poolsC | List resource pools with optional filters. |
| get_resource_poolC | Get resource pool details. |
| list_vmsC | List VMs with optional inventory filters. |
| get_vmB | Get VM summary details. |
| get_vm_guest_identityC | Get guest identity details for a VM. |
| list_vm_guest_local_filesystemsC | List guest local filesystems for a VM. |
| list_vm_guest_network_interfacesB | List guest network interfaces for a VM. |
| get_vm_hardwareC | Get VM hardware summary. |
| get_vm_bootC | Get VM boot configuration. |
| get_vm_cpuC | Get VM CPU configuration. |
| get_vm_memoryC | Get VM memory configuration. |
| list_vm_disksC | List virtual disks for a VM. |
| get_vm_diskC | Get a virtual disk by disk identifier. |
| list_vm_nicsC | List VM virtual NICs. |
| get_vm_nicC | Get a single VM virtual NIC. |
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 33 tools
Most tools target distinct resources with clear prefixes (get_ vs list_), though the cluster CPU/memory tools have overlapping scopes (rollups, periods, windows) that could cause confusion despite different time dimensions.
All tools follow a consistent verb_noun pattern (get_<resource>, list_<resources>), using snake_case throughout. Suffixes like _ws are used uniformly for web services endpoints, maintaining predictability.
33 tools is slightly above the typical range for a focused server, but the vSphere domain has many resource types, making the count justifiable. Each tool appears necessary for comprehensive inventory coverage.
The tool set is entirely read-only (get/list), lacking any create, update, or delete operations. For an inventory or monitoring server this may be complete, but for full vCenter management, significant lifecycle operations are missing.