| name | eks-mcp-server |
| description | Install, configure, and troubleshoot the EKS MCP Server connection in your AI assistant (Claude Code, Cursor, Kiro). Use ONLY for MCP server setup problems — config file location (.mcp.json), IAM permissions for eks-mcp actions, uvx installation, choosing AWS-hosted vs self-hosted mode, or debugging why MCP tools fail to appear after config. Also activate if user mentions "eks mcp", "mcp server", "mcp.json", or "mcp tools not showing". Do NOT use for actual cluster operations once MCP is working — those go to eks-recon (discovery), eks-operation-review (audits), or eks-upgrade-check (upgrades). Use when this capability is needed. |
| metadata | {"author":"aws-samples"} |
EKS MCP Server Setup
This skill guides you through configuring the EKS MCP Server to enable live EKS cluster operations through your AI assistant.
When NOT to Use This Skill
- Operational cluster work (listing resources, troubleshooting pods, reading K8s state) — use the EKS MCP tools directly once configured
- EKS concept questions — use the other EKS skills
Setup Workflow
Step 0: Quick Check — Is EKS MCP Already Configured?
Before proceeding with setup, check if EKS MCP tools are already available:
- Look for MCP tools in your current environment starting with
eks or mcp__eks
- Try a simple command: Ask to list EKS clusters — if it works, you're already set up
If MCP tools are available and working, stop here — skip this skill and proceed with your EKS task directly.
Step 1: Hosting Mode
Ask which hosting mode: AWS-Hosted (managed by AWS, requires IAM, CloudTrail audit logging) or (local via , supports kubeconfig/OIDC, works air-gapped). Explain the trade-off: AWS-Hosted is simplest if you have credentials; Self-Hosted if you need OIDC/kubeconfig auth or air-gapped support.
