← Explore all mcp servers

CLOUD OPERATIONS / Amazon Web Services

AWS EKS MCP Server

Inspects Amazon EKS. It is not a generic Kubernetes server.

“The Amazon EKS MCP server provides AI code assistants with resource management tools and real-time cluster state visibility.”

01 / THE REASONING

Why this made the selection.

  • The README covers EKS and Kubernetes operations for a code assistant, with read-only and sensitive-data access off unless flags are set.
  • add_inline_policy is documented as creating a new inline policy and rejecting changes to existing policies.

02 / THE REVIEW RECORD

What we actually inspected.

Source review has boundaries.
A clear record is more useful than a “safe” badge.

Material inspected

  • src/eks-mcp-server/README.md
  • LICENSE

Our findings

  • README contains awslabs.eks-mcp-server.
  • README contains a uvx command.
  • The server gives a code assistant EKS and Kubernetes resource tools and live cluster state. Write operations for apply_yaml, manage_k8s_resource, manage_eks_stacks, and add_inline_policy stay disabled because --allow-write defaults to false.
  • Sensitive reads, including pod logs and Kubernetes Secrets, also default to off. Outbound calls to the Kubernetes API can be sent through HTTP_PROXY or HTTPS_PROXY.
  • add_inline_policy will not modify existing IAM policies. It only creates new ones and rejects requests to change policies that already exist.

Not established by this review

  • No AWS API call was made.
  • The server was not started and its tools were not called.
  • A pin does not verify transitive dependencies.
  • No tools/list or tool call was made.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

Connect a server deliberately.

Upstream setup instructions ↗

DOCUMENTED COMMAND

uvx awslabs.eks-mcp-server@latest

Copying does not execute this command. It may retrieve a newer version than the reviewed source.

  1. Register the uvx command.
  2. Use credentials for the account you mean.
  3. The one-line command above is the uvx launch in the README client block at this commit, not a separate installer. It was not run.

Before you start

  • uv
  • AWS credentials for the service

Documented configuration example

Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.

{
  "mcpServers": {
    "awslabs.eks-mcp-server": {
      "command": "uvx",
      "args": [
        "awslabs.eks-mcp-server@latest"
      ],
      "env": {
        "AWS_PROFILE": "eks-mcp-readonly-profile",
        "AWS_REGION": "us-east-1",
        "FASTMCP_LOG_LEVEL": "INFO"
      },
      "autoApprove": [
        "manage_eks_stacks",
        "manage_k8s_resource",
        "list_k8s_resources",
        "get_pod_logs",
        "get_k8s_events",
        "get_cloudwatch_logs",
        "get_cloudwatch_metrics",
        "get_policies_for_role",
        "search_eks_troubleshoot_guide",
        "list_api_versions"
      ]
    }
  }
}

04 / FOLLOW THE EVIDENCE

The source trail.

Our notes are separate from the original resource.
Check upstream before adopting a new version.

  1. Server documentation ↗Checked

    https://github.com/awslabs/mcp/blob/49de7cc11ae064b9224f07ae050c612c3f92dd55/src/eks-mcp-server/README.md

    Supports: Install command and stated scope

  2. Repository licence ↗Checked

    https://github.com/awslabs/mcp/blob/49de7cc11ae064b9224f07ae050c612c3f92dd55/LICENSE

    Supports: Redistribution terms

Evidence & Ask