k8s-mcp-server and mcp-kubernetes
These two tools appear to be ecosystem siblings: the Azure tool is an implementation of a Model Context Protocol (MCP) server designed to enable AI assistants to interact with Kubernetes, while the `reza-gholizade/k8s-mcp-server` tool is another server implementation, likely following the same MCP specification, for managing Kubernetes clusters.
About k8s-mcp-server
reza-gholizade/k8s-mcp-server
Manage Your Kubernetes Cluster with k8s mcp-server
Implements MCP protocol with three transport modes (stdio, SSE, streamable-http) for integrating cluster management into CLI tools and web applications. Provides comprehensive Kubernetes operations including resource CRUD, log retrieval, metrics querying, and event listing, with flexible authentication supporting kubeconfig, bearer tokens, and in-cluster service accounts. Includes read-only mode to restrict write operations and runs as non-root in containers.
About mcp-kubernetes
Azure/mcp-kubernetes
A Model Context Protocol (MCP) server that enables AI assistants to interact with Kubernetes clusters. It serves as a bridge between AI tools (like Claude, Cursor, and GitHub Copilot) and Kubernetes
Implements a unified `call_kubectl` tool that consolidates operations into a single interface (reducing context overhead compared to legacy multi-tool approaches), while supporting role-based access control through `readonly`, `readwrite`, and `admin` modes that filter operations at registration time. Integrates with kubectl and optional ecosystem tools (Helm, Cilium, Hubble), communicating via stdio transport by default and supporting OpenTelemetry tracing for observability.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work