Rancher MCP Server
Related Servers
Alternatives to Rancher MCP Server
- AlicenseCqualityAmaintenanceTypeScript implementation of Kubernetes cluster operations for pods, deployments, services.184,455 npm1,580MIT
Related Servers
- FlicenseAqualityDmaintenanceA Model Context Protocol (MCP) server that exposes the Rancher Manager v2.x API to LLM clients.113-

argocd-mcpofficial
AlicenseCqualityCmaintenanceAn implementation of Model Context Protocol (MCP) server for Argo CD.1417,824 npm570Apache 2.0
OpsLevel MCPofficial
AlicenseNot gradedqualityFmaintenanceModel Context Protocol (MCP) server for OpsLevel12MIT- FlicenseNot gradedqualityDmaintenanceA server implementation of the Model Context Protocol (MCP) that provides REST API endpoints for managing and interacting with MCP resources.-
- AlicenseNot gradedqualityAmaintenanceMCP server to lint and validate Kubernetes-related manifests(Helm, FluxCD, ArgoCD, Kustomize, etc.)MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for Talos Linux cluster management via the native gRPC API3MIT
TDQS
Scored across 10 tools
Each tool targets a distinct Harvester resource type (addons, hosts, images, networks, settings, subnets, VMs, volumes, VPCs). The only potential overlap is between harvester_vm_get and harvester_vm_list, but they are clearly differentiated for single vs. list operations.
All tools follow the pattern 'harvester_<resource>_<action>' except 'harvester_settings' which omits the '_list' suffix. This is a minor inconsistency, but overall the naming is predictable and consistent.
10 tools is well-scoped for managing a Harvester environment. It covers major resource categories without being overwhelming or too sparse.
The tool set is almost entirely read-only (list/get), lacking create, update, or delete operations for any resource. This is a significant gap for lifecycle management, likely causing agent failures when mutations are needed.