rancher-mcpRancher tooling as a standalone MCP server

A focused TypeScript MCP service for Rancher cluster, project, namespace, access-control, and Fleet workflows — published on GitHub Pages.

Read the guide

Client examples

Rancher workflows

Cluster, project, namespace, principal, and Fleet operations are exposed through the MCP surface.

Identity-aware transport

Caller Authorization headers are forwarded first, then Rancher credentials are used as a fallback.

Built for agents

The docs include practical examples for Claude, Copilot, and Codex clients.

What this project is for

rancher-mcp packages the Rancher-side MCP tool surface as a standalone service. It is designed for agentic workflows that need to create or inspect Rancher resources, manage Fleet GitRepos, and connect to Rancher with the caller’s identity when available.

How the tooling is grouped

Group	What it covers	Typical use
Rancher core	clusters, projects, namespaces	Provisioning and cleanup
Access control	principals, project members	Finding users/groups and binding access
Fleet	GitRepos, bundles, sync and error inspection	GitOps workflows

Start here

Guide for setup and validation
Client examples for Claude, Copilot, and Codex configuration
API reference for the complete tool inventory