LabscoMCP early access ↗
mrostamiiMCP SERVER

Rancher MCP Server

Read a whole Rancher estate through one connection: downstream cluster health, Kubernetes objects and their events, Fleet GitOps drift, and Harvester virtual machines, volumes and networks.

by mrostamii ↗Containers, Kubernetes & Cluster OperationsCommunity

LABSCO SUMMARY

Out of the box, an agent can answer questions about the estate without being able to change it.

The default launch writes nothing: --read-only is on unless you pass --read-only=false, and deletes also need --disable-destructive=false, so until you add those flags what you hand an agent is limited to what it can read. The audit log and legacy catalog calls degrade rather than fail, returning JSON that carries _source unavailable and a note when a Rancher build does not expose them. The cluster argument on the Kubernetes tools is a Rancher cluster ID.

What it is

A server over Rancher that starts read-only, reaching its Norman v3 API, the Kubernetes resources of the clusters it manages, Fleet GitOps state and Harvester virtualisation; the write and delete tools come on only with launch flags.

What you get

  • Cluster inventory with health, Kubernetes version, provider and node count, plus a cross-cluster total of clusters and projects.
  • Kubernetes access on a named cluster: get or list any apiVersion and kind, describe-style output with recent events, namespace event lists, pod log tails and a capacity summary drawn from Nodes.
  • Fleet GitOps state — GitRepos, bundles, registered clusters, and a drift report of BundleDeployments sitting in Modified state.
  • Harvester inventory: virtual machines with status, IP, node and CPU or memory, one VM in full spec, Longhorn-backed volumes, host maintenance and disk status, VM images with download progress, VLAN networks, KubeOVN subnets and VPCs, addons and cluster settings.
  • Rancher administration reads: users, global role bindings, auth configs, tokens, cloud credentials, settings, feature flags, node drivers, catalogs, cluster repos and cluster registration tokens.
  • Norman schema discovery, which reports the types, collection links and actions this particular Rancher exposes.

Requirements

A reachable Rancher server and an API token for it. The KubeOVN subnet and VPC tools need the kubeovn-operator addon enabled, and token and cloud credential values come back redacted unless show-sensitive-data is turned on.

Setup effort

One command plus a key — npm install -g rancher-mcp-server, then supply credentials