Amazon EKS MCP Server
EKS cluster management, Kubernetes resources and troubleshooting.
Labels are provisional (from the project README/docs, checked Nov 3, 2026). Not yet tested in our sandbox.
Read-only switch
Writes need --allow-write; pod logs/events/secrets need --allow-sensitive-data-access. Leave both off.
Preset
Claude Code
{
"mcpServers": {
"eks": {
"command": "uvx",
"args": ["awslabs.eks-mcp-server@latest"]
}
}
}Optional third layer: add "deny": ["mcp__eks__<write tool>"] under permissions in .claude/settings.json.
Codex
# Generated by redpresets.dev on 2026-11-03. Unverified preset. Also use a read-only credential. Not a security guarantee.
[mcp_servers.eks]
command = "uvx"
args = ["awslabs.eks-mcp-server@latest"]
default_tools_approval_mode = "writes"default_tools_approval_mode = "writes" asks before any tool the server does not mark read-only.
Cursor
{
"mcpServers": {
"eks": {
"type": "stdio",
"command": "uvx",
"args": ["awslabs.eks-mcp-server@latest"]
}
}
}Don't add write tools to mcpAllowlist in .cursor/permissions.json. Leave them on approval. Cursor's docs say the allowlist is not a security boundary.
Credential layer
IAM read-only plus Kubernetes view RBAC.
Facts
- Vendor
- AWS Labs official
- Source
- awslabs/mcp
- License
- Apache-2.0
- GitHub stars
- 9.8k
- Latest release
- 2026.10.20261027104512 (Oct 27, 2026)
- Last push
- Oct 27, 2026
- Status
- Active
- Last checked
- Nov 3, 2026
Sources
- README: --allow-write, --allow-sensitive-data-access · checked Oct 27, 2026
Spotted something wrong? Labels change when vendors change. Suggest a correction
Read-only alternatives in Cloud
Metrics, alarms and Logs Insights queries from CloudWatch.
Runs AWS CLI commands for the agent across services.
Query CloudTrail events and Lake for audit investigations.