vSphere -Pro

This MCP server exposes VMware vCenter operations through a secure, RBAC-enabled interface. It supports VM lifecycle actions, snapshot operations, inventory discovery, and more, all wrapped with audit logging and rate limiting. To use it, configure environment variables to point at your vCenter instance and define your access tokens and role mappings. Start the server using the standard Python module invocation, then connect to the MCP endpoint (default /mcp) with an MCP client or tooling that speaks the MCP protocol. Tools are organized by capability, including VM discovery (list_vms, get_vm_details), inventory discovery (list_hosts, list_datastores, etc.), power operations (power_on_vm, power_off_vm, restart_vm), and snapshot operations. Access control is enforced via roles and tokens, and destructive actions require explicit confirmation.

Prerequisites:

• Python 3.10+
• VMware vCenter 8.0+ and valid API credentials

Install from source (recommended):

git clone https://github.com/Warezloder/vSphere-MCP-Pro
cd vSphere-MCP-Pro
pip install -e .

Run the server locally (from repository root):

export VCENTER_HOST=vcenter.example.com
export VCENTER_USER=administrator@vsphere.local
export VCENTER_PASSWORD=s3cret
export TOKENS_TO_ROLES='{"token1":"read","token2":"admin"}'
export ROLES_TO_TOOLS='{"read":["list_vms","get_vm_details"],"admin":["list_vms","get_vm_details","power_on_vm","power_off_vm","restart_vm","delete_vm"]}'
python -m vsphere_mcp_pro.server

Alternatively, run via the exact mcp_config structure (see the JSON example in this README) by exporting the necessary environment variables and using your preferred orchestration method.

Tips and considerations:

• Ensure SSL verification and CA bundles are correctly configured in production to protect against man-in-the-middle attacks.
• Use ALLOWED_VCENTER_HOSTS to prevent accidental cross-cluster operations in multi-vCenter environments.
• The server uses a session pool to minimize authentication overhead; monitor pool sizes and timeouts via VCENTER_TIMEOUT_S and related settings.
• Audit logs (JSONL) provide traceability for operations; route them to a centralized log system if needed.
• If you enable REST mode (VSPHERE_API_MODE=rest), ensure your vCenter supports the REST API and that credentials have appropriate permissions.
• Destructive operations require confirm=True (enforced by the server) to avoid accidental data loss.
• For local development, you can run with SERVER_PORT and MCP_PATH overridden via environment variables.