SYSTEM Cited by 1 source
EKS MCP Server¶
EKS MCP Server (awslabs.github.io/mcp/servers/eks-mcp-server/) is an AWS-Labs-published Model Context Protocol server that exposes Kubernetes / Amazon EKS operations as MCP tools. Any MCP-compliant LLM agent (Claude Desktop, Cursor, custom Strands agents, etc.) can call EKS operations without hand-rolled kubectl wrappers.
Stub page — minimal viable for the 2025-12-11 conversational- observability blueprint ingest. Expand as future EKS MCP Server sources land.
Why it exists¶
Pre-MCP, every agent that needed to query a Kubernetes cluster wrote its own kubectl-wrapping code: parse proposed commands, shell out, capture output, format for the LLM. MCP standardizes the protocol so the cluster-operations surface can be advertised, discovered, and invoked by any compliant client. EKS MCP Server is the AWS-specific realization for EKS clusters.
Role in the conversational-observability blueprint (2025-12-11)¶
In the Strands deployment option, the K8s Specialist agent calls EKS MCP Server tools via MCP to run live cluster diagnostics. MCP replaces the custom "chatbot parses LLM command → routes to in-cluster assistant" plumbing from the RAG deployment option.
The troubleshooting surface is still bound by read-only allowlisting — MCP transport doesn't lift the principle-of-least- privilege constraint; the server exposes only safe operations, and the Pod Identity under which it runs has correspondingly scoped permissions.
Caveats¶
- Stub page based on one source. Specific tool inventory, schema surface, caching behavior, auth model, and transport details not characterized from wiki sources yet.
- Marketed as "EKS MCP Server integration enabled direct EKS API access through standardized MCP tools" but the tool catalog contents are not enumerated in the source post.
Seen in¶
- sources/2025-12-11-aws-architecting-conversational-observability-for-cloud-applications — EKS MCP Server is the K8s Specialist's tool-call surface in the Strands Agents deployment.