vmware-vks
The vmware-vks MCP server provides 25 tools for managing VMware vSphere Kubernetes Service (VKS) environments.
Check vCenter VKS compatibility, Supervisor upgrade risk, Supervisor status, and WCP-enabled clusters.
List Supervisor storage policies and VM classes for namespace and cluster sizing.
List, inspect, create, update, and delete vSphere Namespaces, with previews and guards for destructive actions.
List, inspect, create, scale, upgrade, and delete TanzuKubernetesCluster (TKC) clusters; list available Kubernetes versions.
Issue Supervisor and TKC kubeconfig credentials as bearer tokens, optionally writing owner-only files.
Inspect embedded Harbor registry status and list PVC/storage usage in namespaces.
Read VM Service snapshots, VM groups with boot order, and VM network interfaces.
Check which vCenter account the server uses and whether it has required privileges.
Use safety features such as read-only operations, blast-radius previews, confirm requirements, workload/TKC deletion guards, audit logging, and optional HTTPS/exposed-tool restrictions.
Retrieves information about the embedded Harbor container registry integrated within the VMware vSphere environment.
Interacts with the Supervisor Kubernetes API to manage Tanzu Kubernetes Clusters (TKC), including creating, scaling, upgrading, and retrieving kubeconfigs for workload clusters.
Provides management tools for VMware vSphere with Tanzu (VKS), enabling control over Supervisor clusters, vSphere Namespaces, and TanzuKubernetesCluster lifecycle operations.
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.
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.
Related MCP server: vmware-nsx
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 ⭐ entry point | VM lifecycle, deployment, guest ops, clusters | 49 |
|
Read-only monitoring, alarms, events, VM info | 27 |
| |
Datastores, iSCSI, vSAN | 11 |
| |
NSX networking: segments, gateways, NAT, IPAM | 33 |
| |
DFW microsegmentation, security groups, Traceflow | 21 |
| |
Aria Ops metrics, alerts, capacity planning | 28 |
|
Prerequisites
Python 3.10+ — required for
uv tool installvSphere 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 --applyOffline / 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-vksCommon Workflows
Deploy a New TKC Cluster
Check compatibility →
vmware-vks checkList available K8s versions →
vmware-vks tkc versions -n devCreate namespace (if needed) →
vmware-vks namespace create dev --cluster domain-c1 --storage-policy <policy-id> --cpu 16000 --memory 32768 --apply(get the policy ID fromvmware-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 --applyGet 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 devScale up →
vmware-vks tkc scale dev-cluster -n dev --workers 6Monitor progress →
vmware-vks tkc get dev-cluster -n dev(watch phase)Scale back down after test
Namespace Resource Management
List namespaces →
vmware-vks namespace listCheck usage →
vmware-vks storage -n devUpdate quota →
vmware-vks namespace update dev --cpu 32000 --memory 65536
Tool Reference (25 tools)
Supervisor
Tool | Description | Type |
| vCenter version check + WCP status | Read |
| vCenter 9.1.0/9.1.1 pre-upgrade advisory scope; VUMDB schema remains unmeasured; links to the official checker | Read |
| Supervisor cluster status and K8s API endpoint | Read |
| 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 |
| All vSphere Namespaces with status | Read |
| Namespace detail (quotas, storage, roles) | Read |
| Create Namespace; previews by default ( | Write |
| Modify quotas and storage policy | Write |
| Delete with TKC guard (rejects if clusters exist) | Write |
| Available VM classes for TKC sizing | Read |
TKC
Tool | Description | Type |
| TanzuKubernetesCluster list with status | Read |
| Cluster detail: every worker pool, known total replicas, health, conditions | Read |
| Supported K8s versions on Supervisor | Read |
| Create TKC; previews the YAML plan by default ( | Write |
| Scale worker node count | Write |
| Upgrade K8s version | Write |
| Delete with workload guard | Write |
get_tkc_cluster.worker_pools lists every declared worker pool. worker_replica_total
is the sum only when every pool has a known fixed replica count; it is null
for an autoscaled or unreadable pool. The older worker_replicas field remains
the first pool only for compatibility and must not be interpreted as the
cluster total.
Access
Tool | Description | Type |
| Supervisor kubeconfig — credential (bearer token); inline or owner-only file | Write |
| TKC kubeconfig — credential (bearer token); inline or owner-only file | Write |
| Embedded Harbor registry info (id, cluster, version, URL, health, storage used) | Read |
| 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 |
| VirtualMachineSnapshot objects in a vSphere Namespace | Read |
| VirtualMachineGroup objects and their boot order in a Namespace | Read |
| Network interfaces (multi-NIC) of one VM Service VirtualMachine | Read |
Permissions
Tool | Description | Type |
| 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 → TanzuKubernetesClusterCLI Reference
# Pre-flight diagnostics
vmware-vks check
# Supervisor
vmware-vks supervisor status <cluster-id>
vmware-vks supervisor upgrade-risk --to 9.1.1
vmware-vks supervisor storage-policies
# Namespace
vmware-vks namespace list
vmware-vks namespace get <name>
vmware-vks namespace create <name> --cluster <id> --storage-policy <policy>
vmware-vks namespace create <name> --cluster <id> --storage-policy <policy> --apply
vmware-vks namespace update <name> [--cpu <mhz>] [--memory <mib>]
vmware-vks namespace delete <name>
vmware-vks namespace vm-classes
# VKS Cluster
vmware-vks tkc list [-n <namespace>]
vmware-vks tkc get <name> -n <namespace>
vmware-vks tkc versions -n <namespace>
vmware-vks tkc create <name> -n <namespace> [--version <v>] [--vm-class <c>]
vmware-vks tkc create <name> -n <namespace> --apply
vmware-vks tkc scale <name> -n <namespace> --workers <n>
vmware-vks tkc upgrade <name> -n <namespace> --version <v>
vmware-vks tkc delete <name> -n <namespace>
# Kubeconfig
vmware-vks kubeconfig supervisor -n <namespace> [-o <path>]
vmware-vks kubeconfig get <cluster-name> -n <namespace> [-o <path>]
# Harbor & Storage
vmware-vks harbor
vmware-vks storage -n <namespace>MCP Server
After uv tool install vmware-vks, start the MCP server with one command (v1.5.15+):
# Recommended — single command, no network re-resolve
vmware-vks mcp
# With a custom config path
VMWARE_VKS_CONFIG=/path/to/config.yaml vmware-vks mcpAgent Configuration
Add to your AI agent's MCP config:
{
"mcpServers": {
"vmware-vks": {
"command": "vmware-vks",
"args": ["mcp"],
"env": {
"VMWARE_VKS_CONFIG": "~/.vmware-vks/config.yaml"
}
}
}
}# Run without installing (requires PyPI access each launch)
uvx --from vmware-vks vmware-vks mcp
# Legacy entry point (still works, kept for backward compatibility)
vmware-vks-mcpBehind a corporate TLS proxy? uvx may fail with
invalid peer certificate: UnknownIssuer. Use the recommendedvmware-vks mcpform above (no network needed), or setUV_NATIVE_TLS=true.
Safety
Feature | Description |
Read-heavy | 16/25 tools are read-only |
Preview by default |
|
TKC guard |
|
Workload guard |
|
Credential safety | Passwords only from environment variables ( |
In-memory kubeconfig | For the skill's own API calls the Supervisor/TKC kubeconfig (with the Supervisor bearer token) is built as an in-memory dict and loaded via |
Kubeconfig is credential access |
|
Audit logging | All write operations logged to |
stdio transport | No network listener; MCP runs over stdio only |
Troubleshooting
"VKS not compatible" error
Workload Management must be enabled in vCenter. Check: vCenter UI -> Workload Management. Requires vSphere 8.x+ with Enterprise Plus or VCF license.
Every command fails with "session is not authenticated"
The password is right. Either the session expired (run the command again; a new session is opened) or the account has no vSphere role, so vCenter shows no session for it and every call fails. VKS does not refuse such a login when it connects, because an account holding only Supervisor namespace permissions can look the same and still work; the error appears on the first call that needs a role. Assign the account a role (Read-Only or higher) on the vCenter root folder under Administration > Access Control > Global Permissions; Namespace and TKC work also needs Workload Management privileges.
Every REST tool returns 401
The namespace, storage-policy and Supervisor-status tools authenticate against
the vSphere Automation REST API with a session id from POST /api/session —
not the pyVmomi SOAP session key, which that API never issued and always
rejects. A 401 is refreshed automatically once; if it persists, check whether a
proxy between you and vCenter strips the vmware-api-session-id header. An
account short of Workload Management permissions gets a 403, not a 401.
Namespace creation fails with "storage policy not found"
List policies first: vmware-vks supervisor storage-policies, then pass the Policy ID column value (not the display name) as --storage-policy.
TKC cluster stuck in "Creating" phase
Check Supervisor events in vCenter. Common causes: insufficient resources on ESXi hosts, network issues with NSX-T, or storage policy not available on target datastore.
Kubeconfig retrieval fails
Supervisor API endpoint must be reachable from the machine running vmware-vks. Check firewall rules for port 6443.
Scale operation has no effect
Verify the cluster is in "Running" phase before scaling. Clusters in "Creating" or "Updating" phase reject scale operations.
Delete namespace rejected unexpectedly
The namespace delete guard prevents deletion when TKC clusters exist inside. Delete all TKC clusters in the namespace first, then retry.
Version Compatibility
vSphere / VCF | Support | Notes |
9.0 / 9.1 | ⚠ Partial external 9.1 report | A 9.1 lab confirmed Supervisor |
8.0+ | Full | Workload Management APIs available |
7.x | Not supported | WCP API surface is different; use vSphere 8.x |
VKS 3.8 introduces vendor-managed chained upgrades and more granular node
placement (official announcement).
This skill's upgrade_tkc_cluster still submits one requested Kubernetes version;
it does not verify or orchestrate the 3.8 upgrade chain or placement policy.
The new worker-pool summary is a read of the existing Cluster topology, not a
VCF 9.1/VKS 3.8 compatibility claim. Live 9.1/3.8 validation is pending.
Official Broadcom References
SDKs: https://developer.broadcom.com/sdks — VCF Python SDK (unified SDK in VCF 9+)
REST APIs: https://developer.broadcom.com/xapis — vSphere Automation API (Workload Management endpoints)
CLI Tools: https://developer.broadcom.com/tools — kubectl-vsphere, PowerCLI 9.1
Related Projects
Skill | Scope | Tools | Install |
vmware-aiops ⭐ entry point | VM lifecycle, deployment, guest ops, clusters | 49 |
|
Read-only monitoring, alarms, events, VM info | 27 |
| |
Datastores, iSCSI, vSAN | 11 |
| |
NSX networking: segments, gateways, NAT, IPAM | 33 |
| |
DFW microsegmentation, security groups, Traceflow | 21 |
| |
Aria Ops metrics, alerts, capacity planning | 28 |
|
Remote access (HTTPS) and limiting tools
By default vmware-vks mcp speaks stdio to one local client and offers every tool. Two options change that
(vmware-policy ≥ 1.21.0).
Serve over HTTPS so clients on other machines can connect. Every caller needs a bearer token:
vmware-audit token create alice # prints the token once; give it to alice
vmware-audit token list # names only
vmware-audit token revoke alice # refused from its next request, no restart
vmware-vks mcp --transport https --host 0.0.0.0 --port 8443 \
--cert /etc/vmware-mcp/server.pem --key /etc/vmware-mcp/server-key.pem \
--public-name mcp.example.comConnect a client (Claude Code shown; any MCP client that supports streamable HTTP and custom headers works):
claude mcp add --transport http vmware-vks https://mcp.example.com:8443/mcp \
--header "Authorization: Bearer $VMWARE_MCP_TOKEN"{
"mcpServers": {
"vmware-vks": {
"type": "http",
"url": "https://mcp.example.com:8443/mcp",
"headers": { "Authorization": "Bearer ${VMWARE_MCP_TOKEN}" }
}
}
}The server will not start without a token, refuses Host/Origin values outside
--public-name, and checks before it binds that unauthenticated requests get 401. Use a certificate your clients trust for those names.Behind a TLS-terminating reverse proxy on the same machine use
--transport http --host 127.0.0.1 --public-name mcp.example.comand pass theAuthorizationheader through.Behind a load balancer or gateway on another machine, keep
--transport https(a self-signed certificate is fine), list in--public-namethe host name the balancer sends asHost, and have it forwardAuthorization. Its health probe can useGET /healthz, which needs no token and returns only{"status": "ok"}(vmware-policy ≥ 1.23.0).Send
traceparentorX-Request-IDwith each request to have it stored on the audit row;vmware-audit log --correlation-id IDthen finds the calls behind one platform request.Tools that read or write files on this server (here:
issue_*_kubeconfig(output_path)) never touch its configuration, tokens, audit log or TLS key, and over the network they are off unlessVMWARE_MCP_FILE_ROOTnames a directory for them (vmware-policy ≥ 1.23.1).The audit log records each caller as
token:<name>. Calls run side by side, also on the same target: the server keeps up toVMWARE_MCP_POOL_SIZE(default 2) sessions per target, each one a login on that target, and a call waits at most 300 s for a free session (vmware-policy ≥ 1.22.0).Everyone who can reach the endpoint acts with this server's account. Tokens identify callers; they grant nothing on the platform. Run one endpoint per privilege level.
vmware-vks access-infoshows which account that is and what it may do.Several people or roles on one endpoint: run
vmware-audit roles enableonce, then give each token a role (vmware-audit token create NAME --role reader, or a role inroles.yamlnaming tools and targets; vmware-policy ≥ 1.24.0). A role limits what the token may call on this endpoint; it cannot grant more than the account has. See vmware-policy's README, "Roles for network callers".
Offer only read tools, plus the writes you choose:
vmware-vks mcp --expose read --allow-write create_namespace
# or: VMWARE_VKS_MCP_EXPOSE=read VMWARE_VKS_MCP_ALLOW_WRITE=create_namespace vmware-vks mcpTools not offered do not appear in the client's tool list. A bad value or an unknown write tool stops the server (exit 2). This limits what clients are offered; it is not authorization, so the account itself should be least-privilege.
Details: skills/vmware-vks/references/setup-guide.md ("Serving MCP over HTTPS", "Limiting which tools are offered").
License
Available Tools
25 toolscheck_vks_compatibilityARead-onlyIdempotent
[READ] Check whether this vCenter supports VKS (requires vSphere 8.x+).
Returns compatible (bool), vcenter_version, wcp_enabled_clusters and wcp_clusters ({cluster, status}). Start here: those cluster MoRefs are the cluster_id for get_supervisor_status and create_namespace. Only reports vCenter-level support — a listed cluster may still be CONFIGURING.
| Name | Required | Description | Default |
|---|---|---|---|
| target | No | vCenter in config.yaml; omit for the default. |
create_namespaceA
[WRITE] Create a vSphere Namespace on a Supervisor Cluster.
Without confirm=True this only previews: it returns blast_radius (the spec that would be applied, and whether the name is already taken) and creates nothing. Show it to the user and get their decision. Do not set confirm=True on your own because the user asked earlier — they have not seen the preview yet. confirm=True returns {action: "created", namespace, status, cluster, blast_radius}; it is refused when the name is taken (use update_namespace) or the existing names could not be read. Confirm with get_namespace afterwards.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Namespace name (lowercase, no spaces). | |
| target | No | vCenter in config.yaml; omit for the default. | |
| confirm | No | False (default) returns the blast radius and changes nothing. True applies it. | |
| cpu_limit | No | MHz. Omit for no limit. | |
| cluster_id | Yes | Supervisor MoRef (from check_vks_compatibility). | |
| description | No | Free-text label. Omit for none. | |
| storage_policy | Yes | Policy ID (from list_supervisor_storage_policies). | |
| memory_limit_mib | No | MiB. Omit for no limit. |
create_tkc_clusterA
[WRITE] Create a TanzuKubernetesCluster in a vSphere Namespace.
Without confirm=True this only previews: it returns blast_radius (node counts, VM class, the YAML manifest, and whether the name is taken) and creates nothing. Show it to the user and get their decision. Do not set confirm=True on your own because the user asked earlier — they have not seen the preview yet. confirm=True returns {action: "created", name, namespace, status: "creating", yaml, blast_radius} and provisions in the background — poll get_tkc_cluster until phase is running. Refused when the name is taken or the namespace's clusters could not be read. Call get_tkc_available_versions for k8s_version and list_vm_classes first.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Cluster name. | |
| target | No | vCenter in config.yaml; omit for the default. | |
| confirm | No | False (default) returns the blast radius and changes nothing. True applies it. | |
| vm_class | Yes | Node sizing, e.g. 'best-effort-large'. | |
| namespace | Yes | Must already exist (see list_namespaces). | |
| k8s_version | Yes | e.g. 'v1.28.4+vmware.1'. | |
| worker_count | No | Worker nodes (>= 1). | |
| storage_class | No | Storage class. | vsphere-storage |
| control_plane_count | No | 1 or 3. |
delete_namespaceADestructive
[WRITE] Delete a vSphere Namespace and everything inside it (irreversible).
Without confirm=True this only previews: it returns blast_radius (the namespace, and the TKC clusters, VMs and PVCs inside it, with counts and names) and deletes nothing. Show that to the user and get their explicit decision. Do not set confirm=True on your own because the user said "delete" earlier: they have not seen what it destroys yet.
confirm=True returns {action: "deleted", namespace, status, blast_radius}. Refused while TKC clusters exist inside (run delete_tkc_cluster on each), and whenever the clusters, VMs or PVCs inside could not be read. Prefer update_namespace to only change quotas.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Namespace name to delete (discover via list_namespaces). | |
| target | No | vCenter in config.yaml; omit for the default. | |
| confirm | No | False (default) returns the blast radius and changes nothing. True applies it. |
delete_tkc_clusterADestructive
[WRITE] Delete a TKC cluster and all of its nodes (irreversible).
Without confirm=True this only previews: it returns blast_radius (control plane and worker node counts per pool, and the running Deployments, StatefulSets and DaemonSets) and deletes nothing. Show that to the user and get their explicit decision. Do not set confirm=True on your own because the user said "delete" earlier: they have not seen what it destroys yet.
confirm=True returns {action: "deleted", name, namespace, status: "deleting", blast_radius}. Refused while workloads run (drain them, or pass force=True, which skips the workload check entirely) and whenever the node counts or workloads could not be read. Use scale_tkc_cluster instead for fewer nodes. Empty a namespace of TKC clusters before delete_namespace accepts it.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Cluster name (via list_tkc_clusters). | |
| force | No | Skip the running-workload check (dangerous). | |
| target | No | vCenter in config.yaml; omit for the default. | |
| confirm | No | False (default) returns the blast radius and changes nothing. True applies it. | |
| namespace | Yes | Namespace holding it. |
get_access_infoARead-onlyIdempotent
[READ] Which account this server uses, and whether it holds each tool's vSphere privileges.
Use this when a tool fails with a permission error, or before a write, to check what the configured account may do. Asks vCenter about the current session (needs only System.View, so any account can ask about itself). Returns target, account, the privilege states, and for one tool its requires/verdict/meaning; without tool, every tool grouped by verdict. Gotchas: privileges are checked on the root folder only, and a verdict of not_granted_at_root is NOT "no access" — it may be granted on a specific cluster. undetermined means vCenter did not answer; never read it as granted. Kubernetes calls (TKC, VM Service, kubeconfigs) are authorized by the namespace's view/edit/owner permission, which this cannot check, so those tools report undetermined. Namespace writes need Namespaces.Configure.
| Name | Required | Description | Default |
|---|---|---|---|
| tool | No | One tool name on this server, e.g. "create_namespace". Omit to summarize every tool. | |
| target | No | vCenter in config.yaml; omit for the default. |
get_harbor_infoARead-onlyIdempotent
[READ] Get status of the embedded Harbor container registry on the Supervisor.
Returns {registries: [{id, cluster (Supervisor MoRef), version, url, status, storage_used_mb}]}; status and storage come from a detail call and are null if it fails. If Harbor is not enabled it returns {error, hint} rather than raising. Use it to check registry health or find the push URL — it does not list repositories or images. Run check_vks_compatibility first if the Supervisor may be down.
| Name | Required | Description | Default |
|---|---|---|---|
| target | No | vCenter in config.yaml; omit for the default. |
get_namespaceARead-onlyIdempotent
[READ] Get detailed configuration for a single vSphere Namespace.
Returns one raw vCenter namespace object, not the list envelope: config_status, description, storage_specs, quotas. Use list_namespaces first for the name; follow with list_namespace_storage_usage for PVC usage or list_tkc_clusters for the clusters inside. Point-in-time only — a CONFIGURING namespace may not have quotas applied.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Namespace name, e.g. 'dev' (discover via list_namespaces). | |
| target | No | vCenter in config.yaml; omit for the default. |
get_supervisor_statusARead-onlyIdempotent
[READ] Get the health of one Supervisor Cluster (vSphere with Tanzu control plane).
Returns cluster_id, config_status (RUNNING = healthy, else CONFIGURING / ERROR / REMOVING), kubernetes_status (READY / WARNING / ERROR), api_server_cluster_endpoint, kubernetes_version (null plus kubernetes_version_hint if unavailable), and network_provider. Run check_vks_compatibility first for cluster IDs; use this to confirm a Supervisor is healthy before create_namespace or create_tkc_cluster.
| Name | Required | Description | Default |
|---|---|---|---|
| target | No | vCenter in config.yaml; omit for the default. | |
| cluster_id | Yes | Compute cluster MoRef, e.g. 'domain-c1' (wcp_clusters field of check_vks_compatibility). |
get_supervisor_upgrade_riskARead-onlyIdempotent
[READ] Check the vCenter 9.1.0/9.1.1 Supervisor pre-upgrade advisory scope.
Reads the source vCenter version/build and Supervisor cluster inventory. Returns advisory_applicability, supervisor_presence and next_step. The vLCM/VUM database schema is unmeasured: this tool never grants upgrade clearance. Use the official checker in Broadcom KB 455737 or VDT before upgrading an affected environment. No database script is run here.
| Name | Required | Description | Default |
|---|---|---|---|
| target | No | vCenter target from config.yaml; omit for the default. | |
| target_version | No | Planned vCenter version, 9.1.0 or 9.1.1. | 9.1.1 |
get_tkc_available_versionsARead-onlyIdempotent
[READ] List Kubernetes versions (TanzuKubernetesReleases) available on the Supervisor.
Returns {versions: [{name, version, e.g. 'v1.28.4+vmware.1'}]}, newest first. If the TanzuKubernetesRelease API is unavailable it returns an empty versions list with error and hint rather than raising. Call this before create_tkc_cluster or upgrade_tkc_cluster to pick a valid k8s_version.
| Name | Required | Description | Default |
|---|---|---|---|
| target | No | vCenter in config.yaml; omit for the default. | |
| namespace | Yes | vSphere Namespace used to reach the Supervisor K8s API. |
get_tkc_clusterARead-onlyIdempotent
[READ] Get detailed status for a single TKC cluster.
Returns one object, not the list envelope: name, namespace, phase, k8s_version, control_plane_replicas, worker_replicas, conditions, infrastructure_ready, control_plane_ready. Run list_tkc_clusters first — a TKC name is only unique within one namespace. Poll this after create_tkc_cluster, scale_tkc_cluster or upgrade_tkc_cluster to watch an async change land.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Cluster name (via list_tkc_clusters). | |
| target | No | vCenter in config.yaml; omit for the default. | |
| namespace | Yes | Namespace holding it. |
issue_supervisor_kubeconfigAIdempotent
[WRITE] Credential access: issue a kubeconfig for the Supervisor K8s API.
Call only when the user explicitly asks for this kubeconfig; never as a side step. Returns {namespace, kubeconfig} as a YAML string, or {namespace, written_to} when output_path is given. The kubeconfig embeds a Supervisor bearer token (JWT from /wcp/login) that acts as the configured vCenter account until the JWT expires (typically hours; not tied to this process) — always pass output_path so the token never enters agent context, and report only the path. The file is created owner-only (0600). For TKC workloads, see issue_tkc_kubeconfig and its vSphere 9.1 limitation before issuing a guest-cluster credential.
| Name | Required | Description | Default |
|---|---|---|---|
| target | No | vCenter in config.yaml; omit for the default. | |
| namespace | Yes | vSphere Namespace to set as the kubeconfig context. | |
| output_path | No | File to write, e.g. '~/.kube/supervisor.yaml'. Omit to return the kubeconfig inline. Creates parent directories and truncates the file. |
issue_tkc_kubeconfigAIdempotent
[WRITE] Credential access: issue a kubeconfig for one TKC cluster.
Call only when the user explicitly asks for this kubeconfig; never as a side step. Returns {cluster, kubeconfig}, or {cluster, written_to} when output_path is given. The kubeconfig embeds a Supervisor bearer token (JWT from /wcp/login) that acts as the configured vCenter account until the JWT expires (typically hours; not tied to this process) — always pass output_path so the token never enters agent context, and report only the path. Nothing in the managed cluster changes, but output_path creates parent directories and truncates the named file (owner-only, 0600), so output_path='~/.kube/config' replaces the user's own kubeconfig. Run list_tkc_clusters first for name and namespace; use issue_supervisor_kubeconfig instead for Supervisor-level access. On one reported VCF 9.1 deployment, the guest cluster API rejects this Supervisor JWT with 401. A generated file does not prove guest access; verify it against the guest API before relying on it (issue #27).
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | TKC cluster name. | |
| target | No | vCenter in config.yaml; omit for the default. | |
| namespace | Yes | Namespace holding it. | |
| output_path | No | File to write, e.g. '~/.kube/my.yaml'. Omit to return the kubeconfig inline. |
list_namespacesARead-onlyIdempotent
[READ] List all vSphere Namespaces on the target vCenter with their status.
Returns the list envelope: items of {namespace, config_status (RUNNING = healthy, CONFIGURING, REMOVING, ERROR), description} plus returned/total/truncated — one call returns them all, so truncated is always false. Start here, then call get_namespace for detail, list_tkc_clusters for what runs inside, or update_namespace / delete_namespace to change one.
| Name | Required | Description | Default |
|---|---|---|---|
| target | No | vCenter in config.yaml; omit for the default. |
list_namespace_storage_usageARead-onlyIdempotent
[READ] List PersistentVolumeClaims and storage usage inside one vSphere Namespace.
Via the Supervisor K8s API. Returns the family list envelope: {namespace, items: [{name, namespace, status (Bound / Pending / Lost), capacity ('10Gi'), storage_class}], returned, limit, total, truncated, hint}. Every PVC comes back in one call, so truncated is always False. Run list_namespaces first for the namespace; use list_supervisor_storage_policies instead for policy-level rather than PVC-level information. 'pvcs' and 'pvc_count' are deprecated pre-1.8.0 aliases of 'items' and 'returned', removed in 2.0 — read 'items'.
| Name | Required | Description | Default |
|---|---|---|---|
| target | No | vCenter in config.yaml; omit for the default. | |
| namespace | Yes | Namespace to inspect. |
list_supervisor_storage_policiesARead-onlyIdempotent
[READ] List vCenter storage policies assignable to Supervisor Namespaces.
Returns the list envelope: items of {policy (ID), name, description} plus returned/total/truncated — one call returns them all, so truncated is always false. Call this before create_namespace or update_namespace and pass the 'policy' ID as their storage_policy. For PVC-level usage use list_namespace_storage_usage instead.
| Name | Required | Description | Default |
|---|---|---|---|
| target | No | vCenter in config.yaml; omit for the default. |
list_tkc_clustersARead-onlyIdempotent
[READ] List TanzuKubernetesCluster (TKC) clusters, optionally in one namespace.
Returns the family list envelope: {items: [{name, namespace, phase, k8s_version}], returned, limit, total, truncated, hint}. The Supervisor list is walked to completion, so truncated is always False. Start here, then call get_tkc_cluster for full detail or issue_tkc_kubeconfig for access. 'clusters' is a deprecated pre-1.8.0 alias of 'items', removed in 2.0 — read 'items'.
| Name | Required | Description | Default |
|---|---|---|---|
| target | No | vCenter in config.yaml; omit for the default. | |
| namespace | No | vSphere Namespace to filter by. Omit to list every one. |
list_vm_classesARead-onlyIdempotent
[READ] List VM classes available for sizing TKC cluster nodes.
Returns the list envelope: items of {id (e.g. 'best-effort-large'), cpu_count, memory_mb, gpu_count (vGPU + DirectPath I/O; 0 if none)} plus returned/total/truncated — one call returns them all, so truncated is always false. Call this before create_tkc_cluster and pass the chosen 'id' as its vm_class; 'guaranteed-' classes reserve resources, 'best-effort-' do not.
| Name | Required | Description | Default |
|---|---|---|---|
| target | No | vCenter in config.yaml; omit for the default. |
list_vm_service_groupsARead-onlyIdempotent
[READ] List VirtualMachineGroup objects and their bootOrder in a Namespace.
VM Service groups (vmoperator.vmware.com CRD, v1alpha4+) via the Supervisor
K8s API — the served CRD version is discovered at runtime. Returns the
family list envelope: items of {name, namespace, boot_order, member_count}
plus returned/total/truncated (walked to completion) and served_version.
boot_order mirrors spec.bootOrder: an ordered list of {members:
[{kind, name}], power_on_delay?}. Older Supervisors without v1alpha4 return
a teaching error naming the required version.
| Name | Required | Description | Default |
|---|---|---|---|
| target | No | vCenter in config.yaml; omit for the default. | |
| namespace | Yes | vSphere Namespace to list VM groups in (via list_namespaces). |
list_vm_service_network_interfacesARead-onlyIdempotent
[READ] List the network interfaces (multi-NIC) of one VirtualMachine.
Reads spec.network.interfaces[] off a single VM Service VirtualMachine (vmoperator.vmware.com) via the Supervisor K8s API; the served CRD version is discovered at runtime. Returns the family list envelope: items of {name, network_name, network_kind, network_api_version} plus returned/total/truncated and vm_name/served_version. A VM with no network block returns an empty list, not an error. Run list_namespaces for the namespace; the VM name comes from your own VM inventory in that namespace.
| Name | Required | Description | Default |
|---|---|---|---|
| target | No | vCenter in config.yaml; omit for the default. | |
| vm_name | Yes | Name of the VirtualMachine to read interfaces from. | |
| namespace | Yes | vSphere Namespace the VM lives in (via list_namespaces). |
list_vm_service_snapshotsARead-onlyIdempotent
[READ] List VirtualMachineSnapshot objects in a vSphere Namespace.
VM Service snapshots (vmoperator.vmware.com CRD, new at v1alpha5) via the Supervisor K8s API — the served CRD version is discovered at runtime, not hardcoded. Returns the family list envelope: items of {name, namespace, vm_name, created, ready} plus returned/total/truncated (walked to completion, so truncated is always false) and served_version. If the Supervisor is older than v1alpha5 the error names the required version. Run list_namespaces first for the namespace; use list_vm_service_network_interfaces for a VM's NICs.
| Name | Required | Description | Default |
|---|---|---|---|
| target | No | vCenter in config.yaml; omit for the default. | |
| namespace | Yes | vSphere Namespace to list snapshots in (via list_namespaces). |
scale_tkc_clusterA
[WRITE] Scale the worker node count of an existing TanzuKubernetesCluster (TKC).
Asynchronous: returns {name, namespace, pool, worker_count, status: "scaling"} immediately — poll get_tkc_cluster to watch nodes appear or drain. Scales workers only; use upgrade_tkc_cluster instead for the K8s version. Not destructive, but lowering worker_count drains removed nodes.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Cluster name (via list_tkc_clusters). | |
| target | No | vCenter in config.yaml; omit for the default. | |
| namespace | Yes | Namespace holding it. | |
| pool_name | No | Node pool (machineDeployment). Omit for the first; other pools are always preserved. | |
| worker_count | Yes | Desired total, integer >= 1 (below 1 is rejected). |
update_namespaceA
[WRITE] Update resource quotas or storage policy of an existing vSphere Namespace.
Only the fields you pass are patched; omitting all of them returns status "no_changes" without an API call, otherwise {namespace, status: "updated"}. Applies immediately — no dry run, no undo. Use this rather than create_namespace when the namespace exists; valid storage_policy values come from list_supervisor_storage_policies.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Existing namespace name (discover via list_namespaces). | |
| target | No | vCenter in config.yaml; omit for the default. | |
| cpu_limit | No | New CPU limit in MHz. Omit to keep current. | |
| storage_policy | No | New storage policy ID. Omit to keep current. | |
| memory_limit_mib | No | New memory limit in MiB. Omit to keep current. |
upgrade_tkc_clusterA
[WRITE] Upgrade a TKC cluster to a new Kubernetes version.
Returns {name, namespace, new_version, status: "upgrading"}. Asynchronous and irreversible — Kubernetes cannot be downgraded, so poll get_tkc_cluster until phase is running. There is no dry run. Use this only for the K8s version; prefer scale_tkc_cluster for node counts.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Cluster name (via list_tkc_clusters). | |
| target | No | vCenter in config.yaml; omit for the default. | |
| namespace | Yes | Namespace holding it. | |
| k8s_version | Yes | Target version from get_tkc_available_versions. |
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
v3.5.0- Added
get_supervisor_upgrade_risk
4 tool updates
v3.4.2- Changed
create_namespace1 field changed- removed
Input schema / properties / dry_runRemoved value: -{ - "anyOf": [ - { - "type": "boolean" - }, - { - "type": "null" - } - ], - "default": null, - "description": "Deprecated alias for confirm; removed in the next minor release. dry_run=False acts, dry_run=True previews.", - "title": "Dry Run" -}
- Changed
create_tkc_cluster1 field changed- removed
Input schema / properties / dry_runRemoved value: -{ - "anyOf": [ - { - "type": "boolean" - }, - { - "type": "null" - } - ], - "default": null, - "description": "Deprecated alias for confirm; removed in the next minor release. dry_run=False acts, dry_run=True previews.", - "title": "Dry Run" -}
- Changed
delete_namespace2 fields changed- removed
Input schema / properties / confirmedRemoved value: -{ - "anyOf": [ - { - "type": "boolean" - }, - { - "type": "null" - } - ], - "default": null, - "description": "Deprecated alias for confirm; removed in the next minor release. Acts only together with dry_run=False; confirmed=False previews.", - "title": "Confirmed" -} - removed
Input schema / properties / dry_runRemoved value: -{ - "anyOf": [ - { - "type": "boolean" - }, - { - "type": "null" - } - ], - "default": null, - "description": "Deprecated alias for confirm; removed in the next minor release. dry_run=True previews.", - "title": "Dry Run" -}
- Changed
delete_tkc_cluster2 fields changed- removed
Input schema / properties / confirmedRemoved value: -{ - "anyOf": [ - { - "type": "boolean" - }, - { - "type": "null" - } - ], - "default": null, - "description": "Deprecated alias for confirm; removed in the next minor release. Acts only together with dry_run=False; confirmed=False previews.", - "title": "Confirmed" -} - removed
Input schema / properties / dry_runRemoved value: -{ - "anyOf": [ - { - "type": "boolean" - }, - { - "type": "null" - } - ], - "default": null, - "description": "Deprecated alias for confirm; removed in the next minor release. dry_run=True previews.", - "title": "Dry Run" -}
1 tool update
v3.3.0- Added
get_access_info
4 tool updates
v3.2.0- Removed
get_supervisor_kubeconfig - Removed
get_tkc_kubeconfig - Added
issue_supervisor_kubeconfig - Added
issue_tkc_kubeconfig
6 tool updates
v2.0.0- Removed
list_vm_groups - Removed
list_vm_network_interfaces - Added
list_vm_service_groups - Added
list_vm_service_network_interfaces - Added
list_vm_service_snapshots - Removed
list_vm_snapshots
4 tool updates
v1.11.0- Changed
create_namespace5 fields changed- added
Input schema / properties / confirmAdded value: +{ + "default": false, + "description": "False (default) returns the blast radius and changes nothing. True applies it.", + "title": "Confirm", + "type": "boolean" +} - added
Input schema / properties / dry_run / anyOfAdded value: +[ + { + "type": "boolean" + }, + { + "type": "null" + } +] - changed
Input schema / properties / dry_run / defaultPrevious value: -trueNew value: +null - changed
Input schema / properties / dry_run / descriptionPrevious value: -"Preview only (default: True)."New value: +"Deprecated alias for confirm; removed in the next minor release. dry_run=False acts, dry_run=True previews." - removed
Input schema / properties / dry_run / typeRemoved value: -"boolean"
- Changed
create_tkc_cluster5 fields changed- added
Input schema / properties / confirmAdded value: +{ + "default": false, + "description": "False (default) returns the blast radius and changes nothing. True applies it.", + "title": "Confirm", + "type": "boolean" +} - added
Input schema / properties / dry_run / anyOfAdded value: +[ + { + "type": "boolean" + }, + { + "type": "null" + } +] - changed
Input schema / properties / dry_run / defaultPrevious value: -trueNew value: +null - changed
Input schema / properties / dry_run / descriptionPrevious value: -"YAML plan only (default: True)."New value: +"Deprecated alias for confirm; removed in the next minor release. dry_run=False acts, dry_run=True previews." - removed
Input schema / properties / dry_run / typeRemoved value: -"boolean"
- Changed
delete_namespace9 fields changed- added
Input schema / properties / confirmAdded value: +{ + "default": false, + "description": "False (default) returns the blast radius and changes nothing. True applies it.", + "title": "Confirm", + "type": "boolean" +} - added
Input schema / properties / confirmed / anyOfAdded value: +[ + { + "type": "boolean" + }, + { + "type": "null" + } +] - changed
Input schema / properties / confirmed / defaultPrevious value: -falseNew value: +null - changed
Input schema / properties / confirmed / descriptionPrevious value: -"Must be True to proceed."New value: +"Deprecated alias for confirm; removed in the next minor release. Acts only together with dry_run=False; confirmed=False previews." - removed
Input schema / properties / confirmed / typeRemoved value: -"boolean" - added
Input schema / properties / dry_run / anyOfAdded value: +[ + { + "type": "boolean" + }, + { + "type": "null" + } +] - changed
Input schema / properties / dry_run / defaultPrevious value: -trueNew value: +null - changed
Input schema / properties / dry_run / descriptionPrevious value: -"Preview only (default: True)."New value: +"Deprecated alias for confirm; removed in the next minor release. dry_run=True previews." - removed
Input schema / properties / dry_run / typeRemoved value: -"boolean"
- Changed
delete_tkc_cluster10 fields changed- added
Input schema / properties / confirmAdded value: +{ + "default": false, + "description": "False (default) returns the blast radius and changes nothing. True applies it.", + "title": "Confirm", + "type": "boolean" +} - added
Input schema / properties / confirmed / anyOfAdded value: +[ + { + "type": "boolean" + }, + { + "type": "null" + } +] - changed
Input schema / properties / confirmed / defaultPrevious value: -falseNew value: +null - changed
Input schema / properties / confirmed / descriptionPrevious value: -"Must be True to proceed."New value: +"Deprecated alias for confirm; removed in the next minor release. Acts only together with dry_run=False; confirmed=False previews." - removed
Input schema / properties / confirmed / typeRemoved value: -"boolean" - added
Input schema / properties / dry_run / anyOfAdded value: +[ + { + "type": "boolean" + }, + { + "type": "null" + } +] - changed
Input schema / properties / dry_run / defaultPrevious value: -trueNew value: +null - changed
Input schema / properties / dry_run / descriptionPrevious value: -"Preview only (default: True)."New value: +"Deprecated alias for confirm; removed in the next minor release. dry_run=True previews." - removed
Input schema / properties / dry_run / typeRemoved value: -"boolean" - changed
Input schema / properties / force / descriptionPrevious value: -"Skip the workload check (dangerous)."New value: +"Skip the running-workload check (dangerous)."
1 tool update
v1.9.1- Changed
get_supervisor_kubeconfig1 field changed- added
Input schema / properties / output_pathAdded value: +{ + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "default": null, + "description": "File to write, e.g. '~/.kube/supervisor.yaml'. Omit to return the kubeconfig inline. Creates parent directories and truncates the file.", + "title": "Output Path" +}
23 tool updates
v1.8.14- Changed
check_vks_compatibility2 fields changed- added
Input schema / additionalPropertiesAdded value: +false - added
Input schema / properties / target / descriptionAdded value: +"vCenter in config.yaml; omit for the default."
- Changed
create_namespace9 fields changed- added
Input schema / additionalPropertiesAdded value: +false - added
Input schema / properties / cluster_id / descriptionAdded value: +"Supervisor MoRef (from check_vks_compatibility)." - added
Input schema / properties / cpu_limit / descriptionAdded value: +"MHz. Omit for no limit." - added
Input schema / properties / description / descriptionAdded value: +"Free-text label. Omit for none." - added
Input schema / properties / dry_run / descriptionAdded value: +"Preview only (default: True)." - added
Input schema / properties / memory_limit_mib / descriptionAdded value: +"MiB. Omit for no limit." - added
Input schema / properties / name / descriptionAdded value: +"Namespace name (lowercase, no spaces)." - added
Input schema / properties / storage_policy / descriptionAdded value: +"Policy ID (from list_supervisor_storage_policies)." - added
Input schema / properties / target / descriptionAdded value: +"vCenter in config.yaml; omit for the default."
- Changed
create_tkc_cluster10 fields changed- added
Input schema / additionalPropertiesAdded value: +false - added
Input schema / properties / control_plane_count / descriptionAdded value: +"1 or 3." - added
Input schema / properties / dry_run / descriptionAdded value: +"YAML plan only (default: True)." - added
Input schema / properties / k8s_version / descriptionAdded value: +"e.g. 'v1.28.4+vmware.1'." - added
Input schema / properties / name / descriptionAdded value: +"Cluster name." - added
Input schema / properties / namespace / descriptionAdded value: +"Must already exist (see list_namespaces)." - added
Input schema / properties / storage_class / descriptionAdded value: +"Storage class." - added
Input schema / properties / target / descriptionAdded value: +"vCenter in config.yaml; omit for the default." - added
Input schema / properties / vm_class / descriptionAdded value: +"Node sizing, e.g. 'best-effort-large'." - added
Input schema / properties / worker_count / descriptionAdded value: +"Worker nodes (>= 1)."
- Changed
delete_namespace5 fields changed- added
Input schema / additionalPropertiesAdded value: +false - added
Input schema / properties / confirmed / descriptionAdded value: +"Must be True to proceed." - added
Input schema / properties / dry_run / descriptionAdded value: +"Preview only (default: True)." - added
Input schema / properties / name / descriptionAdded value: +"Namespace name to delete (discover via list_namespaces)." - added
Input schema / properties / target / descriptionAdded value: +"vCenter in config.yaml; omit for the default."
- Changed
delete_tkc_cluster7 fields changed- added
Input schema / additionalPropertiesAdded value: +false - added
Input schema / properties / confirmed / descriptionAdded value: +"Must be True to proceed." - added
Input schema / properties / dry_run / descriptionAdded value: +"Preview only (default: True)." - added
Input schema / properties / force / descriptionAdded value: +"Skip the workload check (dangerous)." - added
Input schema / properties / name / descriptionAdded value: +"Cluster name (via list_tkc_clusters)." - added
Input schema / properties / namespace / descriptionAdded value: +"Namespace holding it." - added
Input schema / properties / target / descriptionAdded value: +"vCenter in config.yaml; omit for the default."
- Changed
get_harbor_info2 fields changed- added
Input schema / additionalPropertiesAdded value: +false - added
Input schema / properties / target / descriptionAdded value: +"vCenter in config.yaml; omit for the default."
- Changed
get_namespace3 fields changed- added
Input schema / additionalPropertiesAdded value: +false - added
Input schema / properties / name / descriptionAdded value: +"Namespace name, e.g. 'dev' (discover via list_namespaces)." - added
Input schema / properties / target / descriptionAdded value: +"vCenter in config.yaml; omit for the default."
- Changed
get_supervisor_kubeconfig3 fields changed- added
Input schema / additionalPropertiesAdded value: +false - added
Input schema / properties / namespace / descriptionAdded value: +"vSphere Namespace to set as the kubeconfig context." - added
Input schema / properties / target / descriptionAdded value: +"vCenter in config.yaml; omit for the default."
- Changed
get_supervisor_status3 fields changed- added
Input schema / additionalPropertiesAdded value: +false - added
Input schema / properties / cluster_id / descriptionAdded value: +"Compute cluster MoRef, e.g. 'domain-c1' (wcp_clusters field of check_vks_compatibility)." - added
Input schema / properties / target / descriptionAdded value: +"vCenter in config.yaml; omit for the default."
- Changed
get_tkc_available_versions3 fields changed- added
Input schema / additionalPropertiesAdded value: +false - added
Input schema / properties / namespace / descriptionAdded value: +"vSphere Namespace used to reach the Supervisor K8s API." - added
Input schema / properties / target / descriptionAdded value: +"vCenter in config.yaml; omit for the default."
- Changed
get_tkc_cluster4 fields changed- added
Input schema / additionalPropertiesAdded value: +false - added
Input schema / properties / name / descriptionAdded value: +"Cluster name (via list_tkc_clusters)." - added
Input schema / properties / namespace / descriptionAdded value: +"Namespace holding it." - added
Input schema / properties / target / descriptionAdded value: +"vCenter in config.yaml; omit for the default."
- Changed
get_tkc_kubeconfig5 fields changed- added
Input schema / additionalPropertiesAdded value: +false - added
Input schema / properties / name / descriptionAdded value: +"TKC cluster name." - added
Input schema / properties / namespace / descriptionAdded value: +"Namespace holding it." - added
Input schema / properties / output_path / descriptionAdded value: +"File to write, e.g. '~/.kube/my.yaml'. Omit to return the kubeconfig inline." - added
Input schema / properties / target / descriptionAdded value: +"vCenter in config.yaml; omit for the default."
- Changed
list_namespace_storage_usage3 fields changed- added
Input schema / additionalPropertiesAdded value: +false - added
Input schema / properties / namespace / descriptionAdded value: +"Namespace to inspect." - added
Input schema / properties / target / descriptionAdded value: +"vCenter in config.yaml; omit for the default."
- Changed
list_namespaces2 fields changed- added
Input schema / additionalPropertiesAdded value: +false - added
Input schema / properties / target / descriptionAdded value: +"vCenter in config.yaml; omit for the default."
- Changed
list_supervisor_storage_policies2 fields changed- added
Input schema / additionalPropertiesAdded value: +false - added
Input schema / properties / target / descriptionAdded value: +"vCenter in config.yaml; omit for the default."
- Changed
list_tkc_clusters3 fields changed- added
Input schema / additionalPropertiesAdded value: +false - added
Input schema / properties / namespace / descriptionAdded value: +"vSphere Namespace to filter by. Omit to list every one." - added
Input schema / properties / target / descriptionAdded value: +"vCenter in config.yaml; omit for the default."
- Changed
list_vm_classes2 fields changed- added
Input schema / additionalPropertiesAdded value: +false - added
Input schema / properties / target / descriptionAdded value: +"vCenter in config.yaml; omit for the default."
- Added
list_vm_groups - Added
list_vm_network_interfaces - Added
list_vm_snapshots - Changed
scale_tkc_cluster6 fields changed- added
Input schema / additionalPropertiesAdded value: +false - added
Input schema / properties / name / descriptionAdded value: +"Cluster name (via list_tkc_clusters)." - added
Input schema / properties / namespace / descriptionAdded value: +"Namespace holding it." - added
Input schema / properties / pool_name / descriptionAdded value: +"Node pool (machineDeployment). Omit for the first; other pools are always preserved." - added
Input schema / properties / target / descriptionAdded value: +"vCenter in config.yaml; omit for the default." - added
Input schema / properties / worker_count / descriptionAdded value: +"Desired total, integer >= 1 (below 1 is rejected)."
- Changed
update_namespace6 fields changed- added
Input schema / additionalPropertiesAdded value: +false - added
Input schema / properties / cpu_limit / descriptionAdded value: +"New CPU limit in MHz. Omit to keep current." - added
Input schema / properties / memory_limit_mib / descriptionAdded value: +"New memory limit in MiB. Omit to keep current." - added
Input schema / properties / name / descriptionAdded value: +"Existing namespace name (discover via list_namespaces)." - added
Input schema / properties / storage_policy / descriptionAdded value: +"New storage policy ID. Omit to keep current." - added
Input schema / properties / target / descriptionAdded value: +"vCenter in config.yaml; omit for the default."
- Changed
upgrade_tkc_cluster5 fields changed- added
Input schema / additionalPropertiesAdded value: +false - added
Input schema / properties / k8s_version / descriptionAdded value: +"Target version from get_tkc_available_versions." - added
Input schema / properties / name / descriptionAdded value: +"Cluster name (via list_tkc_clusters)." - added
Input schema / properties / namespace / descriptionAdded value: +"Namespace holding it." - added
Input schema / properties / target / descriptionAdded value: +"vCenter in config.yaml; omit for the default."
8 tool updates
v1.8.9- Added
create_namespace - Added
delete_namespace - Added
delete_tkc_cluster - Added
get_supervisor_status - Added
get_tkc_cluster - Added
list_namespaces - Added
list_tkc_clusters - Added
list_vm_classes
9 tool updates
v1.8.8- Removed
create_namespace - Removed
delete_namespace - Removed
delete_tkc_cluster - Removed
get_supervisor_status - Removed
get_tkc_cluster - Removed
list_namespaces - Changed
list_supervisor_storage_policies1 field changed- changed
Output schema / (root)Previous value: -{ - "properties": { - "result": { - "items": { - "additionalProperties": true, - "type": "object" - }, - "title": "Result", - "type": "array" - } - }, - "required": [ - "result" - ], - "title": "list_supervisor_storage_policiesOutput", - "type": "object" -}New value: +null
- Removed
list_tkc_clusters - Removed
list_vm_classes
TDQS
Scored across 25 tools
Tools target distinct resources and actions, and descriptions explicitly cross-reference the correct tool for each job (e.g. issue_supervisor_kubeconfig vs issue_tkc_kubeconfig, list_supervisor_storage_policies vs list_namespace_storage_usage). The only mild overlap is check_vks_compatibility vs get_supervisor_status, both answering Supervisor questions, but their read/write breadcrumbs and hints make boundaries clear.
Uniform snake_case verb_noun pattern throughout: list_*, get_*, create_*, update_*, delete_*, issue_*, plus domain-specific verbs (scale_tkc_cluster, upgrade_tkc_cluster, check_vks_compatibility). No camelCase or stylistic mixing, and the [READ]/[WRITE] tags reinforce the verb semantics.
25 tools is at the heavy end of the scale, and while the domain is genuinely broad (namespace CRUD, TKC lifecycle, VM Service, storage, Harbor, kubeconfigs, compatibility), the surface feels larger than strictly necessary for a single server. Each tool is defensible but the count pushes into 'heavy' territory.
Strong lifecycle coverage: full namespace CRUD, full TKC lifecycle (create/get/list/scale/upgrade/delete/versions), kubeconfig issuance, and supporting compatibility, storage, Harbor, and access-info tools. Gaps exist on the VM Service side (only list operations for snapshots/groups/NICs, no create/delete) and no Harbor repository/image listing, but core platform workflows are covered.
Maintenance
Related MCP Connectors
The Google GKE MCP server is a managed Model Context Protocol server that provides AI applications with tools to manage Google Kubernetes Engine (GKE) clusters and Kubernetes resources. It exposes a structured, discoverable interface that allows AI agents to interact with GKE and Kubernetes APIs, enabling them to inspect cluster configurations, retrieve Kubernetes resource YAMLs, monitor operations like cluster upgrades, diagnose issues, and optimize costs—all without needing to parse text output or use complex kubectl commands.
Hosted MCP catalog with 30 tenant-isolated browser, RAG, AI, mail and media tools.
MCP server for AI agents to plan, verify, and deploy Cloudflare-native apps.
Compliance frameworks (SOC 2, ISO 27001, CMMC, NIST, more) delivered to AI agents as MCP tools.
Related MCP Servers
- AlicenseAqualityAmaintenanceAI-powered VMware vCenter/ESXi monitoring and operations. 20 MCP tools for inventory queries, health monitoring, VM lifecycle management, fast provisioning (Linked Clone, OVA, template deploy), snapshot management, and datastore browsing. Supports vSphere 6.5–8.0. Works with local models via Ollama/LM Studio.44398 PyPI87MIT
- AlicenseAqualityBmaintenanceAI-powered VMware NSX networking management. Configure segments, gateways, NAT, routing, and IPAM via natural language with 31 MCP tools.33215 PyPI5MIT
- AlicenseAqualityBmaintenanceAI-powered VMware storage management for vSphere. Manage datastores, iSCSI targets, and vSAN via natural language with 11 MCP tools.16322 PyPI3MIT
- AlicenseAqualityBmaintenanceAI-powered VMware Aria Operations monitoring and capacity planning. Query metrics, manage alerts, detect anomalies, and plan capacity with 18 MCP tools.46344 PyPI3MIT