Rancher MCP server

<!-- mcp-name: io.github.rex/rancher-mcp -->

Operate Rancher-managed Kubernetes through any MCP client — discovery, generic resource access, and curated operator workflows, wrapped in an audit-logged, rate-limited, confirmation-guarded safety model.

Quick start · Tool surface · Architecture · Safety model · Compatibility · Development

Why this exists

Rancher is how real fleets run Kubernetes — and it speaks two APIs (the legacy Norman /v3 plane and the modern Steve /v1 plane), varies by version, and wraps every cluster behind its own proxy. Pointing a generic Kubernetes MCP server at it misses everything Rancher-specific; pointing an agent at raw kubectl gives up auditability, guardrails, and the management-plane view entirely.

MCP Rancher is built for that reality:

actually supports instead of assuming. One binary spans 2.6.5 → 2.9.3 with the same tool surface.

• Capability-aware, not version-naive. It detects what each connected Rancher

read_only: true and every mutation is refused at the config layer, before any guard even has to fire.

• Multi-instance first. Lab, staging, prod — configure them all; mark prod

engine reaches every resource either API plane exposes — even types nobody wrote a tool for yet.

• Nothing is out of reach. Curated tools cover the common 95%; the generic

The tool surface

206 tools: 178 read-only · 28 writes · 5 destructive — counted from the registry itself, not by hand. docs/tool-manifest.json is generated from the live FastMCP registry (make tool-manifest) and a CI gate fails the build if it ever drifts from the code. Per-tool descriptions, safety annotations, and parameters all live there; the narrative registry with slice tracking is docs/tool-catalog.md.

Shortened. The full README is on GitHub.