Read-Only vSphere MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HOST | No | Listening address for HTTP/SSE (unused by stdio) | 127.0.0.1 |
| MCP_PORT | No | Listening port for HTTP/SSE (unused by stdio) | 8000 |
| VSPHERE_HOST | Yes | HTTPS address of vCenter, e.g., https://vcenter.company.com | |
| MCP_TRANSPORT | No | Transport mode: stdio, streamable-http, or sse | stdio |
| VSPHERE_PASSWORD | Yes | Password for the vCenter account | |
| VSPHERE_USERNAME | Yes | vCenter SSO or directory username | |
| VSPHERE_CA_BUNDLE | No | Absolute path to a PEM CA bundle if using internal CA | |
| VSPHERE_VERIFY_SSL | No | Whether to verify SSL certificate (true or false) | true |
| VSPHERE_TIMEOUT_SECONDS | No | Maximum time for one vCenter HTTP request | 30 |
| VSPHERE_VI_JSON_RELEASE | No | API release for deep property tools (auto-detected) | |
| VSPHERE_PROPERTY_ALLOWLIST | No | Advanced replacement for managed-object property allowlist |
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_list_vmsB | List visible virtual machines using the vSphere Automation REST API. |
| vsphere_get_vmA | Get read-only details for one virtual machine by vSphere VM id, for example vm-42. |
| vsphere_list_hostsA | List visible ESXi hosts using the vSphere Automation REST API. |
| vsphere_list_clustersA | List visible vCenter clusters using the vSphere Automation REST API. |
| vsphere_list_datastoresA | List visible datastores using the vSphere Automation REST API. |
| vsphere_list_datacentersA | List visible datacenters using the vSphere Automation REST API. |
| vsphere_list_networksA | List visible networks using the vSphere Automation REST API. |
| vsphere_get_vm_summaryC | Get a VirtualMachine summary property through VI/JSON by VM id, for example vm-42. |
| vsphere_query_propertiesA | Read one allowlisted VI/JSON managed-object property. Inputs are mo_type, mo_id, property_path, and optional release. |
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 9 tools
Tools are mostly distinct with clear purposes. The slight overlap between vsphere_get_vm and vsphere_get_vm_summary could cause confusion, but descriptions differentiate them (full VM details vs. summary property). All other tools target unique resource types.
All tools start with 'vsphere_' and follow a verb_noun pattern. Verbs are consistently 'list' for enumeration and 'get' for single resources, except 'query_properties' which uses 'query' instead of 'get', introducing minor inconsistency.
9 tools cover the core read-only operations for vSphere (listing main resources and retrieving VM details). The count is well-scoped for the server's purpose, not excessive or sparse.
The set covers listing for most resources and VM detail retrieval, but lacks ways to get detailed properties for clusters, datastores, or hosts beyond listing. The generic 'query_properties' tool may partially fill gaps but is limited to allowlisted properties and requires specific input.