vsphere-mcp-server
A Python Model Context Protocol (MCP) server that provides tool-based access to VMware vSphere (vCenter/ESXi) for infrastructure management. It exposes MCP tools for authentication credential caching, VM lifecycle operations, inventory lookups (hosts/datacenters/datastores), folder organization browsing, and network/VLAN discovery using the vSphere APIs.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Strengths: credentials are claimed to be stored in macOS Keychain with a 4-hour TTL and renewed/expired handling; credential clearing tool exists. Concerns: README states SSL verification is disabled by default, which increases MITM risk unless configurable and overridden. The tool layer does not describe fine-grained scopes; authorization likely depends entirely on vSphere user permissions configured in the supplied credentials.
⚡ Reliability
Best When
You want an MCP tool layer for vSphere discovery and basic operational actions, and you can provide/handle vSphere credentials securely in an environment that can tolerate the stated TLS verification behavior.
Avoid When
You cannot change/override TLS settings to enforce certificate verification, or you require explicit OAuth-style scopes at the MCP layer.
Use Cases
- • Automating VM inventory and inspection via an MCP-connected agent
- • Running scripted power operations (power on/off) on selected VMs
- • Retrieving infrastructure metadata (hosts, datastores, datacenters) for monitoring/assessment workflows
- • Discovering networks and extracting VLAN info from network naming
- • Browsing vSphere folder structures to locate resources
Not For
- • Production-ready automated operations without human review for destructive/high-impact actions
- • Environments requiring strict TLS verification by default if SSL verification is disabled
- • High-governance setups that need fine-grained IAM scopes and explicit permission models at the API layer (it delegates to vSphere roles/permissions)
Interface
Authentication
The server appears to use vSphere session token authentication behind the scenes, but exposes username/password credential acquisition and local caching/TTL at the MCP layer rather than OAuth scopes.
Pricing
License is MIT and PyPI installation is described, but no hosted pricing is indicated (assumed self-hosted).
Agent Metadata
Known Gotchas
- ⚠ TLS verification is disabled by default per README; agents operating in strict security environments should ensure TLS verification is enabled/adjusted.
- ⚠ Network/VLAN extraction appears to rely on parsing network names; results may be inaccurate if naming conventions differ.
- ⚠ Authentication relies on credential caching with a TTL and may trigger GUI prompts; headless agent deployments may need a strategy for credential provisioning.
- ⚠ Power operations are potentially disruptive; agents should add safeguards (confirmations, inventory filtering, dry-run controls) before executing.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for vsphere-mcp-server.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-04-04.