F
licenseNot graded
qualityB
maintenanceEnables AI assistants to query, validate, and create vCluster YAML configurations directly from GitHub, supporting version-specific queries and automatic validation.
15 npm
-
vcluster-mcp
by mmpyro
Related Servers
Alternatives to vcluster-mcp
No user-submitted related servers found.
Related Servers
- FlicenseBqualityDmaintenanceEnables managing Kubernetes clusters through natural language by providing tools to list resources, view logs, port-forward services, scale deployments, and execute kubectl operations via AI assistants.81-
- AlicenseAqualityCmaintenanceEnables AI assistants to interact with and manage Kubernetes clusters, supporting operations on pods, deployments, services, configmaps, secrets, namespaces, metrics, and events with built-in safety features for destructive actions.95 npm1MIT
- AlicenseNot gradedqualityFmaintenanceEnables AI-powered management of multi-cluster Kubernetes environments through natural language, supporting kubectl operations, function execution, and agent interactions with multiple AI providers.7Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to manage virtual machines via natural language, including creating, editing, and VNC control.7 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to manage VMware vSphere infrastructure through 55 typed tools built on the govc CLI. It supports comprehensive operations including VM lifecycle management, snapshot control, datastore navigation, and networking configuration.10 npm3MIT
TDQS
A3.6/5.0
Scored across 16 tools
Disambiguation4/5
Most tools target a distinct resource/action: create/delete/pause/resume/describe/list are clearly separated, and label vs annotation operations are differentiated. The main ambiguity is vcluster_disconnect, whose purpose is vague and could be confused with vcluster_call or vcluster_kubeconfig context handling.
Naming Consistency3/5
The vcluster_* prefix provides some cohesion, but conventions are mixed: vcluster_kubeconfig and vcluster_certs_check break the verb pattern, and the namespace metadata tools use a separate get/set/delete_namespace_* style. Everything is snake_case and readable, but the two naming schemes create inconsistency.
Tool Count3/5
At 16 tools, the server sits at the heavy end of the typical range, and several namespace label/annotation utilities feel peripheral to core vcluster management. A dedicated disconnect tool with no clear connect counterpart also adds questionable value.
Completeness4/5
The core vcluster lifecycle is well covered: create, list, describe, pause, resume, delete, plus call, kubeconfig export, and certificate checking. Minor gaps exist such as no dedicated upgrade/update tool and no obvious connect counterpart for vcluster_disconnect, but agents can work around these.
Maintenance
ActivityMaintained
ResponsivenessNo issues