clusters
Retrieves a list of Kubernetes clusters (also known as managed clusters or spoke clusters).
LABSCO SUMMARY
Which cluster to talk to becomes an argument, so one session covers the fleet instead of one kubeconfig context at a time.
The reach comes from kubectl accepting arbitrary commands and YAML rather than from a long tool list — 3 tools cover the whole surface, and anything kubectl can express is in scope. That also sets where the boundary is: connect_cluster binds cluster-admin unless a narrower ClusterRole is named on the call, so the scoping decision is yours to make on each connection rather than one the server makes for you.
What it is
A hub-side entry point to a fleet of managed Kubernetes clusters, turning the choice of cluster into an argument on the kubectl call.
What you get
- clusters, which retrieves the Kubernetes clusters registered as managed or spoke clusters.
- connect_cluster, which generates the KUBECONFIG for a managed cluster and binds it to a ClusterRole, defaulting to cluster-admin.
- kubectl, which runs a kubectl command or applies YAML against a named cluster.
Requirements
A hub that already registers the managed clusters you want to reach, and the rights on them to generate a KUBECONFIG and bind a ClusterRole.
Setup effort
One command — npx -y multicluster-mcp-server@latest
USE CASES
01
Reaching a spoke cluster you have no kubeconfig for
The hub lists what it manages, and connect_cluster generates the KUBECONFIG for the one you name. The ClusterRole it binds is cluster-admin unless you pass a narrower one.
02
Applying a manifest to a cluster you pick by name
The kubectl tool takes either a command or YAML plus the cluster it should run against, so moving between clusters is an argument change instead of a context switch.
3 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
connect_cluster
Generates the KUBECONFIG for the managed cluster and binds it to the specified ClusterRole (default: cluster-admin).
kubectl
Securely run a kubectl command or apply YAML. Provide either 'command' or 'yaml'.
BEFORE YOU INSTALL
What to know first
Tools you get
3 tools when we connected.
Requires
npx on PATH
CONTEXT COST
Light Standing cost
Rated by the size of the 3 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"multicluster-mcp-server": {
"command": "npx",
"args": [
"-y",
"multicluster-mcp-server@latest"
]
}
}
}npx
TERMINAL
npx -y multicluster-mcp-server@latest
