VMware VKS

Name: VMware VKS
Author: zw008

by zw008version 1.8.8i★ –iRuns on your computer

Registry nameio.github.zw008/vmware-vks

Install

Overview

Description from the maker (original English)

vSphere with Tanzu (VKS): Namespace and TanzuKubernetesCluster lifecycle. Requires vSphere 8.x+.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

PyPIPython’s uv installed (for the uvx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "vmware-vks": {
      "command": "uvx",
      "args": [
        "vmware-vks"
      ]
    }
  }
}

Run this in your terminal

claude mcp add vmware-vks -- uvx vmware-vks

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "vmware-vks": {
      "command": "uvx",
      "args": [
        "vmware-vks"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "vmware-vks": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "vmware-vks"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account zw008, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 32709 servers in this category
Published to the registry more recently than 19% of the other 32709 servers in this category
Basic checks equal to or better than 100% of the other 32709 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is VMware VKS safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.8.8) reached the registry 4 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, SwarmMemo

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 2 days ago

Install

SwarmMemo

by Hugo0

Talk with agent swarms: rooms, private messages and paid tasks for AI agents

Runs in the cloudUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

VMware VKS

For a read-only check of this skill with your model and agent host, use the shared model-fit self-test in the marketplace root.

Author: Wei Zhou, VMware by Broadcom — wei-wz.zhou@broadcom.com

This is a community-driven project by a VMware engineer, not an official VMware product.

For official VMware developer tools see developer.broadcom.com.

English | 中文

MCP Skill + CLI for VMware vSphere Kubernetes Service (VKS) management — Supervisor clusters, vSphere Namespaces, and VKS Cluster lifecycle. 25 MCP tools.

Upgrading to 3.0

3.0 renames the two kubeconfig tools: get_supervisor_kubeconfig → issue_supervisor_kubeconfig, get_tkc_kubeconfig → issue_tkc_kubeconfig. They issue a credential (a Supervisor bearer token) rather than read something, and a get_ name told agents otherwise. Parameters, annotations, safety and CLI commands (vmware-vks kubeconfig supervisor / kubeconfig get) are unchanged; callers of the old names must switch (saved vmware-pilot workflows are translated by Pilot ≥ 2.0.0). Deny rules in ~/.vmware/rules.yaml naming the old names keep working with vmware-policy ≥ 1.19.0. Details in RELEASE_NOTES.md.

Upgrading to 2.0

2.0 renames the three VM Service tools: list_vm_snapshots → list_vm_service_snapshots, list_vm_groups → list_vm_service_groups, list_vm_network_interfaces → list_vm_service_network_interfaces. The reason is a name clash: in the family's 2.0, vmware-aiops and vmware-monitor call their vSphere VM snapshot tool list_vm_snapshots, while these list Kubernetes VM Service (vm-operator) objects. Trap: an agent prompt, script or saved workflow that still calls list_vm_snapshots with vmware-aiops or vmware-monitor also loaded now reaches the vSphere tool, not this one — update it. A VKS-scoped deny rule naming list_vm_snapshots now also matches the aiops/monitor tool (vmware-policy ≥ 1.18 matches both names; vmware-audit policy lists such rules). Parameters, safety gates and CLI commands are unchanged; the full table is in RELEASE_NOTES.md. If an install older than 2.0 shares that rules.yaml, give it vmware-policy ≥ 1.18.2 too: it matches each rule against both the old and the new name, so one file serves both.

Companion Skills

Part of the VMware MCP Skills family. Each skill handles a distinct domain — install only what you need.

Skill	Scope	Tools	Install
[vmware-aiops](https://github.com/vmware-skills/VMware-AIops) ⭐ entry point	VM lifecycle, deployment, guest ops, clusters	49	`uv tool install vmware-aiops`
[vmware-monitor](https://github.com/vmware-skills/VMware-Monitor)	Read-only monitoring, alarms, events, VM info	27	`uv tool install vmware-monitor`
[vmware-storage](https://github.com/vmware-skills/VMware-Storage)	Datastores, iSCSI, vSAN	11	`uv tool install vmware-storage`
[vmware-nsx](https://github.com/vmware-skills/VMware-NSX)	NSX networking: segments, gateways, NAT, IPAM	33	`uv tool install vmware-nsx-mgmt`
[vmware-nsx-security](https://github.com/vmware-skills/VMware-NSX-Security)	DFW microsegmentation, security groups, Traceflow	21	`uv tool install vmware-nsx-security`
[vmware-aria](https://github.com/vmware-skills/VMware-Aria)	Aria Ops metrics, alerts, capacity planning	28	`uv tool install vmware-aria`

Prerequisites

Python 3.10+ — required for uv tool install
vSphere 8.0+ — Workload Management (Supervisor) APIs require vSphere 8.x
Workload Management enabled — WCP must be enabled on at least one compute cluster
License — vSphere Kubernetes Service (Enterprise Plus or VMware Cloud Foundation)

Run vmware-vks check after setup to verify all requirements are met.

Quick Start

# Install

uv tool install vmware-vks

Configure

mkdir -p ~/.vmware-vks cp config.example.yaml ~/.vmware-vks/config.yaml

Edit config.yaml with your vCenter host and username

One password env var per target, named after the target in config.yaml:

target "vcenter01" (the one config.example.yaml ships) -> VMWARE_VKS_VCENTER01_PASSWORD

echo "VMWARE_VKS_VCENTER01_PASSWORD=your_password" > ~/.vmware-vks/.env chmod 600 ~/.vmware-vks/.env

Verify

vmware-vks check

Common operations

vmware-vks supervisor status domain-c1 vmware-vks namespace list vmware-vks tkc list vmware-vks tkc create my-cluster -n dev --version v1.28.4+vmware.1 --vm-class best-effort-large vmware-vks tkc create my-cluster -n dev --apply

Offline / Air-Gapped Install (from source)

This project uses the modern PEP 517 build system (hatchling), so there is no `setup.py` by design — that is expected, not a missing file. If you cloned the source and hit ERROR: File "setup.py" or "setup.cfg" not found ... editable mode currently requires a setuptools-based build, your pip is older than 21.3 and cannot do an *editable* (-e) install with a non-setuptools backend. Editable mode is a developer convenience, not needed to run the tool — do one of:

# From the source tree — a normal (non-editable) install builds a wheel:

pip install . # NOT pip install -e .

...or upgrade pip first, and editable works too:

pip install --upgrade pip && pip install -e .

For a truly air-gapped host, build the wheels on a connected machine and copy them over — the target then needs no network:

# On a connected machine, collect this package + its dependencies as wheels:

pip wheel . -w dist # → dist/*.whl (or: uv build, for just this package)

Copy dist/ to the air-gapped host, then install offline:

pip install --no-index --find-links dist vmware-vks

Common Workflows

Deploy a New TKC Cluster

Check compatibility → vmware-vks check
List available K8s versions → vmware-vks tkc versions -n dev
Create namespace (if needed) → vmware-vks namespace create dev --cluster domain-c1 --storage-policy --cpu 16000 --memory 32768 --apply (get the policy ID from vmware-vks supervisor storage-policies)
Create TKC cluster → vmware-vks tkc create dev-cluster -n dev --version v1.28.4+vmware.1 --control-plane 1 --workers 3 --vm-class best-effort-large --apply
Get kubeconfig (credential; only when you need cluster access) → vmware-vks kubeconfig get dev-cluster -n dev -o ./kubeconfig — writes an owner-only file instead of printing the token

Scale Workers for Load Testing

Check current state → vmware-vks tkc get dev-cluster -n dev
Scale up → vmware-vks tkc scale dev-cluster -n dev --workers 6
Monitor progress → vmware-vks tkc get dev-cluster -n dev (watch phase)
Scale back down after test

Namespace Resource Management

List namespaces → vmware-vks namespace list
Check usage → vmware-vks storage -n dev
Update quota → vmware-vks namespace update dev --cpu 32000 --memory 65536

Tool Reference (25 tools)

Supervisor

Tool	Description	Type
`check_vks_compatibility`	vCenter version check + WCP status	Read
`get_supervisor_upgrade_risk`	vCenter 9.1.0/9.1.1 pre-upgrade advisory scope; VUMDB schema remains unmeasured; links to the official checker	Read
`get_supervisor_status`	Supervisor cluster status and K8s API endpoint	Read
`list_supervisor_storage_policies`	vCenter storage policies (policy ID, name, description)	Read

For an upgrade from vCenter 8.0 Update 3 or 9.0.0–9.0.2 to 9.1.0/9.1.1, run supervisor upgrade-risk before scheduling. Its report cannot inspect the VUMDB schema or establish upgrade clearance. If a Supervisor/VKS environment is in scope, follow the Broadcom checker and remediation instructions or VDT, then back up vCenter and Supervisor before upgrading.

Namespace

Tool	Description	Type
`list_namespaces`	All vSphere Namespaces with status	Read
`get_namespace`	Namespace detail (quotas, storage, roles)	Read
`create_namespace`	Create Namespace; previews by default (`confirm=True` applies)	Write
`update_namespace`	Modify quotas and storage policy	Write
`delete_namespace`	Delete with TKC guard (rejects if clusters exist)	Write
`list_vm_classes`	Available VM classes for TKC sizing	Read

TKC

Tool	Description	Type
`list_tkc_clusters`	TanzuKubernetesCluster list with status	Read
`get_tkc_cluster`	Cluster detail (nodes, health, conditions)	Read
`get_tkc_available_versions`	Supported K8s versions on Supervisor	Read
`create_tkc_cluster`	Create TKC; previews the YAML plan by default (`confirm=True` applies)	Write
`scale_tkc_cluster`	Scale worker node count	Write
`upgrade_tkc_cluster`	Upgrade K8s version	Write
`delete_tkc_cluster`	Delete with workload guard	Write

Access

Tool	Description	Type
`issue_supervisor_kubeconfig`	Supervisor kubeconfig — credential (bearer token); inline or owner-only file	Write
`issue_tkc_kubeconfig`	TKC kubeconfig — credential (bearer token); inline or owner-only file	Write
`get_harbor_info`	Embedded Harbor registry info (id, cluster, version, URL, health, storage used)	Read
`list_namespace_storage_usage`	PVC list and capacity stats	Read

VCF 9.1 TKC access: In one live 9.1 report, issue_tkc_kubeconfig put a Supervisor JWT into the guest kubeconfig and the TKC API rejected it with 401. Treat the generated file as unverified for guest access; test it against the guest API before use. See issue #27. Supervisor-scoped TKC reads are unaffected in that report.

VM Service (vm-operator)

Tool	Description	Type
`list_vm_service_snapshots`	VirtualMachineSnapshot objects in a vSphere Namespace	Read
`list_vm_service_groups`	VirtualMachineGroup objects and their boot order in a Namespace	Read
`list_vm_service_network_interfaces`	Network interfaces (multi-NIC) of one VM Service VirtualMachine	Read

Permissions

Tool	Description	Type
`get_access_info`	Which account the server uses and whether it holds each tool's vSphere privileges on the root folder. Kubernetes calls are authorized by the namespace's own permissions, which it does not check	Read

Architecture

User (Natural Language)

↓ AI Agent (Claude Code / Goose / Cursor) ↓ reads SKILL.md ↓ vmware-vks CLI ─── or ─── vmware-vks MCP Server (stdio) │ ├─ Layer 1: pyVmomi (/sdk) + vSphere Automation REST (/api) │ Supervisor status, storage policies, Namespace CRUD, VM classes, Harbor │ Two session stores: the SOAP session from SmartConnect, and a separate │ REST session id from POST /api/session (vmware-api-session-id header) │ └─ Layer 2: kubernetes client → Supervisor K8s API endpoint TKC CR apply / get / delete (cluster.x-k8s.io API version auto-detected: prefers v1 when Supervisor serves it, falls back to v1beta1 for vSphere 8.0) Kubeconfig built in-memory from the POST /wcp/login bearer token (a third credential, and no temp file on disk) ↓ vCenter Server 8.x+ (Workload Management enabled) ↓ Supervisor Cluster → vSphere Namespaces → TanzuKubernetesCluster

CLI Reference

# Pre-flight diagnostics

vmware-vks check

Only the beginning is shown; read the rest in the repo

VMware VKS

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

SwarmMemo

README from the maker

VMware VKS

Upgrading to 3.0

Upgrading to 2.0

Companion Skills

Prerequisites

Quick Start

Configure

Edit config.yaml with your vCenter host and username

One password env var per target, named after the target in config.yaml:

target "vcenter01" (the one config.example.yaml ships) -> VMWARE_VKS_VCENTER01_PASSWORD

Verify

Common operations

Offline / Air-Gapped Install (from source)

...or upgrade pip first, and editable works too:

Copy dist/ to the air-gapped host, then install offline:

Common Workflows

Deploy a New TKC Cluster

Scale Workers for Load Testing

Namespace Resource Management

Tool Reference (25 tools)

Supervisor

Namespace

TKC

Access

VM Service (vm-operator)

Permissions

Architecture

CLI Reference