vcluster-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| vcluster_listB | List all vclusters in the current Kubernetes context. |
| vcluster_describeB | Status, resources and configuration of one vcluster. Namespace defaults to vcluster-. |
| vcluster_certs_checkA | Report control-plane certificates and expiry for a vcluster. Read-only. Worth checking when a vcluster looks healthy but is unreachable, since expired certs surface as opaque connection failures. |
| vcluster_kubeconfigA | Export a vcluster kubeconfig without switching the caller's context. Returns the path to a private (0600) temp file, not the contents, because it holds client credentials. Pass the path to other tools; delete it after use. |
| vcluster_pauseA | Pause a running vcluster, stopping its workloads without deleting state. |
| vcluster_resumeC | Resume a paused vcluster. |
| vcluster_deleteB | Delete a vcluster. Irreversible. The host namespace is preserved by default. |
| vcluster_createB | Create a vcluster. Never switches the caller's kube context. |
| vcluster_callB | Run a command inside a vcluster via Output is capped; prefer narrow queries over |
| vcluster_disconnectB | Disconnect from the currently connected vcluster. |
| namespace_metadata_getB | Read labels and/or annotations on a namespace. |
| namespace_metadata_setA | Set or delete one label or annotation on a namespace. Deleting a key that does not exist succeeds. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Each tool has a clearly distinct purpose: listing, describing, checking certs, exporting kubeconfig, pausing/resuming, creating, executing commands, deleting, disconnecting, and managing namespace metadata. There is no overlap that would cause misselection, and the two namespace metadata tools are cleanly separated by get/set.
Most tools follow a clean vcluster_<verb> pattern (list, describe, pause, resume, create, call, delete, disconnect). Minor deviations exist: vcluster_certs_check (noun-verb), vcluster_kubeconfig (noun only), and the namespace_metadata_get/set pair uses a different prefix. These are readable but not perfectly uniform.
With 12 tools, the server is well-scoped for vcluster management. Each tool provides a necessary operation, and the count is comfortably within the ideal 3-15 range, neither bloated nor thin.
The toolset covers the full vcluster lifecycle (create, list, describe, delete, pause/resume) plus operational utilities (certs, kubeconfig, command execution, disconnect). Minor gaps exist: no update/modify tool for vcluster configuration and no explicit connect tool to pair with disconnect, though kubeconfig and call can serve access needs.