Enterprise DNA
M MCP Servers Developer low

zw008/VMware-VKS

by Various

MCP Skill + CLI for vSphere with Tanzu (VKS) — Supervisor, Namespace, and TanzuKubernetesCluster lifecycle management. Requires vSphere 8.x+.

Z

MCP

zw008/VMware-VKS

Added 11 June 2026

#agent-skills #ai-skill #claude-code #codex #gemini-cli #kubernetes #mcp #supervisor

Overview

This tool provides an MCP skill and CLI for managing vSphere with Tanzu (VKS) environments, including Supervisor, Namespace, and TanzuKubernetesCluster lifecycle operations. It requires vSphere 8.x+ and is written in Python.

Best for

Best for
Developers and operators managing vSphere with Tanzu environments who want MCP-based automation for cluster lifecycle tasks.

Use cases

  • Automate TanzuKubernetesCluster creation and deletion
  • Manage vSphere Supervisor and Namespace resources
  • Integrate vSphere with Tanzu lifecycle tasks into MCP workflows

Notes

This tool provides an MCP skill and CLI for managing vSphere with Tanzu (VKS) environments, including Supervisor, Namespace, and TanzuKubernetesCluster lifecycle operations. It requires vSphere 8.x+ and is written in Python.

1 stars on GitHub. Last updated 2026-06-10. Licensed MIT.

Use cases

  • Automate TanzuKubernetesCluster creation and deletion
  • Manage vSphere Supervisor and Namespace resources
  • Integrate vSphere with Tanzu lifecycle tasks into MCP workflows

Pros

  • Fills a niche for vSphere with Tanzu automation via MCP
  • Lightweight Python CLI with focused functionality
  • Directly addresses lifecycle management for VKS clusters

Cons

  • Very early stage (1 star, minimal community adoption)
  • Requires vSphere 8.x+, limiting compatibility
  • Narrow scope may not suit general Kubernetes management

Indexed from awesome-mcp-servers-punkpeye and enriched against its public facts.

Pros

  • Fills a niche for vSphere with Tanzu automation via MCP
  • Lightweight Python CLI with focused functionality
  • Directly addresses lifecycle management for VKS clusters

Cons

  • Very early stage (1 star, minimal community adoption)
  • Requires vSphere 8.x+, limiting compatibility
  • Narrow scope may not suit general Kubernetes management