Rancher MCP Server
Related Servers
Alternatives to Rancher MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceModel Context Protocol (MCP) server for the Rancher ecosystem: multi-cluster Kubernetes, Harvester HCI (VMs, storage, networks), and Fleet GitOps.1012Apache 2.0
- FlicenseNot gradedqualityDmaintenanceA server implementation of the Model Context Protocol (MCP) that provides REST API endpoints for managing and interacting with MCP resources.-
- AlicenseAqualityAmaintenanceModel Context Protocol (MCP) server for debugging, analyzing, and diagnosing Kubernetes clusters directly from AI agents.66MIT
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that bridges MCP clients with local LLM services, enabling seamless integration with MCP-compatible applications through standard tools like chat completion, model listing, and health checks.-

OpsLevel MCPofficial
AlicenseNot gradedqualityCmaintenanceModel Context Protocol (MCP) server for OpsLevel12MIT- AlicenseBqualityDmaintenanceAn educational implementation of a Model Context Protocol server that demonstrates how to build a functional MCP server integrating with various LLM clients.2MIT
TDQS
Scored across 11 tools
Each tool targets a distinct resource or action (clusters, kubeconfig, pods, deployments, namespaces, nodes, projects, catalog apps). There is no overlap; even related tools like 'list_clusters' and 'get_cluster' are clearly different operations.
All tools follow a consistent verb_noun pattern (create_, get_, list_, scale_). The naming style is uniform and predictable, making it easy for an agent to infer the function of each tool.
With 11 tools, the server is well-scoped for a Rancher management interface. It covers a variety of essential operations without being bloated or too sparse.
The tool set is heavily read-oriented (list, get) with only two write operations (create_kubeconfig, scale_deployment). Missing critical CRUD operations for clusters, deployments, and other resources, which limits agent capabilities for full lifecycle management.