awslabs.eks-mcp-server 0.1.1__tar.gz → 0.1.3__tar.gz

{awslabs_eks_mcp_server-0.1.1 → awslabs_eks_mcp_server-0.1.3}/Dockerfile

@@ -1,15 +1,18 @@
 # Copyright Amazon.com, Inc. or its affiliates. All Rights Reserved.
 #
-# Licensed under the Apache License, Version 2.0 (the "License"). You may not use this file except in compliance
-# with the License. A copy of the License is located at
+# Licensed under the Apache License, Version 2.0 (the "License");
+# you may not use this file except in compliance with the License.
+# You may obtain a copy of the License at
 #
-#    http://www.apache.org/licenses/LICENSE-2.0
+#     http://www.apache.org/licenses/LICENSE-2.0
 #
-# or in the 'license' file accompanying this file. This file is distributed on an 'AS IS' BASIS, WITHOUT WARRANTIES
-# OR CONDITIONS OF ANY KIND, express or implied. See the License for the specific language governing permissions
-# and limitations under the License.
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
 
-FROM public.ecr.aws/sam/build-python3.10@sha256:a40f492a0cd8d76557f8a187fc00e49e8864b3cea683e74718ce317790c1ce61 AS uv
+FROM public.ecr.aws/sam/build-python3.10@sha256:e78695db10ca8cb129e59e30f7dc9789b0dbd0181dba195d68419c72bac51ac1 AS uv
 
 # Install the project into `/app`
 WORKDIR /app
@@ -43,7 +46,7 @@ RUN --mount=type=cache,target=/root/.cache/uv \
 # Make the directory just in case it doesn't exist
 RUN mkdir -p /root/.local
 
-FROM public.ecr.aws/sam/build-python3.10@sha256:a40f492a0cd8d76557f8a187fc00e49e8864b3cea683e74718ce317790c1ce61
+FROM public.ecr.aws/sam/build-python3.10@sha256:e78695db10ca8cb129e59e30f7dc9789b0dbd0181dba195d68419c72bac51ac1
 
 # Place executables in the environment at the front of the path and include other binaries
 ENV PATH="/app/.venv/bin:$PATH:/usr/sbin"

{awslabs_eks_mcp_server-0.1.1 → awslabs_eks_mcp_server-0.1.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: awslabs.eks-mcp-server
-Version: 0.1.1
+Version: 0.1.3
 Summary: An AWS Labs Model Context Protocol (MCP) server for EKS
 Project-URL: homepage, https://awslabs.github.io/mcp/
 Project-URL: docs, https://awslabs.github.io/mcp/servers/eks-mcp-server/
@@ -89,30 +89,36 @@ For read operations, the following permissions are required:
 
 ### Write Operations Policy
 
-For write operations, the following permissions are required:
-
-```
-{
-  "Version": "2012-10-17",
-  "Statement": [
-    {
-      "Effect": "Allow",
-      "Action": [
-        "cloudformation:CreateStack",
-        "cloudformation:UpdateStack",
-        "cloudformation:DeleteStack",
-        "iam:PutRolePolicy"
-      ],
-      "Resource": "*",
-      "Condition": {
-        "StringEquals": {
-          "aws:RequestTag/CreatedBy": "EksMcpServer"
-        }
+For write operations, we recommend the following IAM policies to ensure successful deployment of EKS clusters using the CloudFormation template in `/awslabs/eks_mcp_server/templates/eks-templates/eks-with-vpc.yaml`:
+
+* [**IAMFullAccess**](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/IAMFullAccess.html): Enables creation and management of IAM roles and policies required for cluster operation
+* [**AmazonVPCFullAccess**](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AmazonVPCFullAccess.html): Allows creation and configuration of VPC resources including subnets, route tables, internet gateways, and NAT gateways
+* [**AWSCloudFormationFullAccess**](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AWSCloudFormationFullAccess.html): Provides permissions to create, update, and delete CloudFormation stacks that orchestrate the deployment
+* **EKS Full Access (provided below)**: Required for creating and managing EKS clusters, including control plane configuration, node groups, and add-ons
+   ```
+  {
+    "Version": "2012-10-17",
+    "Statement": [
+      {
+        "Effect": "Allow",
+        "Action": "eks:*",
+        "Resource": "*"
       }
-    }
-  ]
-}
-```
+    ]
+  }
+   ```
+
+
+**Important Security Note**: Users should exercise caution when `--allow-write` and `--allow-sensitive-data-access` modes are enabled with these broad permissions, as this combination grants significant privileges to the MCP server. Only enable these flags when necessary and in trusted environments. For production use, consider creating more restrictive custom policies.
+
+### Kubernetes API Access Requirements
+
+All Kubernetes API operations will only work when one of the following conditions is met:
+
+1. The user's principal (IAM role/user) actually created the EKS cluster being accessed
+2. An EKS Access Entry has been configured for the user's principal
+
+If you encounter authorization errors when using Kubernetes API operations, verify that an access entry has been properly configured for your principal.
 
 ## Quickstart
 
@@ -124,6 +130,30 @@ This quickstart guide walks you through the steps to configure the Amazon EKS MC
 2. Click the gear icon (⚙️) in the top right to open the settings panel, click **MCP**, **Add new global MCP server**.
 3. Paste your MCP server definition. For example, this example shows how to configure the EKS MCP Server, including enabling mutating actions by adding the `--allow-write` flag to the server arguments:
 
+   **For Mac/Linux:**
+
+	```
+	{
+	  "mcpServers": {
+	    "awslabs.eks-mcp-server": {
+	      "autoApprove": [],
+	      "disabled": false,
+	      "command": "uvx",
+	      "args": [
+	        "awslabs.eks-mcp-server@latest",
+	        "--allow-write"
+	      ],
+	      "env": {
+	        "FASTMCP_LOG_LEVEL": "ERROR"
+	      },
+	      "transportType": "stdio"
+	    }
+	  }
+	}
+	```
+
+   **For Windows:**
+
 	```
 	{
 	  "mcpServers": {
@@ -132,7 +162,9 @@ This quickstart guide walks you through the steps to configure the Amazon EKS MC
 	      "disabled": false,
 	      "command": "uvx",
 	      "args": [
+	        "--from",
 	        "awslabs.eks-mcp-server@latest",
+	        "awslabs.eks-mcp-server.exe",
 	        "--allow-write"
 	      ],
 	      "env": {
@@ -153,6 +185,8 @@ This quickstart guide walks you through the steps to configure the Amazon EKS MC
 1. Install the [Amazon Q Developer CLI](https://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/command-line-installing.html) .
 2. The Q Developer CLI supports MCP servers for tools and prompts out-of-the-box. Edit your Q developer CLI's MCP configuration file named mcp.json following [these instructions](https://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/command-line-mcp-configuration.html). For example:
 
+   **For Mac/Linux:**
+
 	```
 	{
 	  "mcpServers": {
@@ -169,6 +203,24 @@ This quickstart guide walks you through the steps to configure the Amazon EKS MC
 	}
 	```
 
+   **For Windows:**
+
+	```
+	{
+	  "mcpServers": {
+	    "awslabs.eks-mcp-server": {
+	      "command": "uvx",
+	      "args": ["--from", "awslabs.eks-mcp-server@latest", "awslabs.eks-mcp-server.exe"],
+	      "env": {
+	        "FASTMCP_LOG_LEVEL": "ERROR"
+	      },
+	      "autoApprove": [],
+	      "disabled": false
+	    }
+	  }
+	}
+	```
+
 3. Verify your setup by running the `/tools` command in the Q Developer CLI to see the available EKS MCP tools.
 
 Note that this is a basic quickstart. You can enable additional capabilities, such as [running MCP servers in containers](https://github.com/awslabs/mcp?tab=readme-ov-file#running-mcp-servers-in-containers) or combining more MCP servers like the [AWS Documentation MCP Server](https://awslabs.github.io/mcp/servers/aws-documentation-mcp-server/) into a single MCP server definition. To view an example, see the [Installation and Setup](https://github.com/awslabs/mcp?tab=readme-ov-file#installation-and-setup) guide in AWS MCP Servers on GitHub. To view a real-world implementation with application code in context with an MCP server, see the [Server Developer](https://modelcontextprotocol.io/quickstart/server) guide in Anthropic documentation.
@@ -179,13 +231,36 @@ Note that this is a basic quickstart. You can enable additional capabilities, su
 
 The `args` field in the MCP server definition specifies the command-line arguments passed to the server when it starts. These arguments control how the server is executed and configured. For example:
 
+**For Mac/Linux:**
+```
+{
+  "mcpServers": {
+    "awslabs.eks-mcp-server": {
+      "command": "uvx",
+      "args": [
+        "awslabs.eks-mcp-server@latest",
+        "--allow-write",
+        "--allow-sensitive-data-access"
+      ],
+      "env": {
+        "AWS_PROFILE": "your-profile",
+        "AWS_REGION": "us-east-1"
+      }
+    }
+  }
+}
+```
+
+**For Windows:**
 ```
 {
   "mcpServers": {
     "awslabs.eks-mcp-server": {
       "command": "uvx",
       "args": [
+        "--from",
         "awslabs.eks-mcp-server@latest",
+        "awslabs.eks-mcp-server.exe",
         "--allow-write",
         "--allow-sensitive-data-access"
       ],
@@ -198,11 +273,17 @@ The `args` field in the MCP server definition specifies the command-line argumen
 }
 ```
 
-#### `awslabs.eks-mcp-server@latest` (required)
+#### Command Format
+
+The command format differs between operating systems:
 
-Specifies the latest package/version specifier for the MCP client config.
+**For Mac/Linux:**
+* `awslabs.eks-mcp-server@latest` - Specifies the latest package/version specifier for the MCP client config.
 
-* Enables MCP server startup and tool registration.
+**For Windows:**
+* `--from awslabs.eks-mcp-server@latest awslabs.eks-mcp-server.exe` - Windows requires the `--from` flag to specify the package and the `.exe` extension.
+
+Both formats enable MCP server startup and tool registration.
 
 #### `--allow-write` (optional)
 
@@ -396,24 +477,45 @@ Features:
 Parameters:
 
 * cluster_name, log_type (application, host, performance, control-plane, custom), resource_type (pod, node, container, cluster),
-resource_name, minutes (optional), start_time (optional), end_time (optional), limit (optional), filter_pattern (optional), fields (optional)
+resource_name (optional), minutes (optional), start_time (optional), end_time (optional), limit (optional), filter_pattern (optional), fields (optional)
 
 #### `get_cloudwatch_metrics`
 
-Retrieves metrics from CloudWatch for a specific EKS cluster resource.
+Retrieves metrics from CloudWatch for Kubernetes resources.
 
 Features:
 
-* Fetches metrics based on resource type (pod, node, container, cluster), resource name, and metric name.
-* Allows specification of CloudWatch namespace, Kubernetes namespace, and time range.
+* Fetches metrics based on metric name and dimensions.
+* Allows specification of CloudWatch namespace and time range.
 * Configurable period, statistic (Average, Sum, etc.), and limit for data points.
 * Supports providing custom dimensions for fine-grained metric querying.
 
 Parameters:
 
-* cluster_name, metric_name, resource_type (pod, node, container, cluster), resource_name, namespace (optional), k8s_namespace
-(optional), minutes (optional), start_time (optional), end_time (optional), limit (optional), stat (optional), period (optional), custom_dimensions
- (optional)
+* cluster_name, metric_name, namespace, dimensions, minutes (optional), start_time (optional), end_time (optional), limit (optional), stat (optional), period (optional)
+
+#### `get_eks_metrics_guidance`
+
+Provides guidance on available CloudWatch metrics for different resource types in EKS clusters.
+
+Features:
+
+* Returns a list of available Container Insights metrics for the specified resource type, including metric names, dimensions, and descriptions.
+* Helps determine the correct dimensions to use with the `get_cloudwatch_metrics` tool.
+* Supports the following resource types:
+  * `cluster`: Metrics for EKS clusters (e.g., cluster_node_count, cluster_failed_node_count)
+  * `node`: Metrics for EKS nodes (e.g., node_cpu_utilization, node_memory_utilization, node_network_total_bytes)
+  * `pod`: Metrics for Kubernetes pods (e.g., pod_cpu_utilization, pod_memory_utilization, pod_network_rx_bytes)
+  * `namespace`: Metrics for Kubernetes namespaces (e.g., namespace_number_of_running_pods)
+  * `service`: Metrics for Kubernetes services (e.g., service_number_of_running_pods)
+
+Parameters:
+
+* resource_type
+
+Implementation:
+
+The data in `/awslabs/eks_mcp_server/data/eks_cloudwatch_metrics_guidance.json` is generated by a Python script (`/awslabs/eks_mcp_server/scripts/update_eks_cloudwatch_metrics_guidance.py`) that scrapes the [Container Insights metrics table](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Container-Insights-metrics-EKS.html) from AWS documentation. Running the script requires installing BeautifulSoup (used for parsing HTML content) with uv: `uv pip install bs4`.
 
 ### IAM Integration
 
@@ -500,6 +602,7 @@ The EKS MCP Server can be used for production environments with proper security
 
 An array within the MCP server definition that lists tool names to be automatically approved by the EKS MCP Server client, bypassing user confirmation for those specific tools. For example:
 
+**For Mac/Linux:**
 ```
 {
   "mcpServers": {
@@ -530,6 +633,39 @@ An array within the MCP server definition that lists tool names to be automatica
 }
 ```
 
+**For Windows:**
+```
+{
+  "mcpServers": {
+    "awslabs.eks-mcp-server": {
+      "command": "uvx",
+      "args": [
+        "--from",
+        "awslabs.eks-mcp-server@latest",
+        "awslabs.eks-mcp-server.exe"
+      ],
+      "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"
+      ]
+    }
+  }
+}
+```
+
 ### IAM Permissions Management
 
 When the `--allow-write` flag is enabled, the EKS MCP Server can create missing IAM permissions for EKS resources through the `add_inline_policy` tool. This tool enables the following:

{awslabs_eks_mcp_server-0.1.1 → awslabs_eks_mcp_server-0.1.3}/README.md

@@ -55,30 +55,36 @@ For read operations, the following permissions are required:
 
 ### Write Operations Policy
 
-For write operations, the following permissions are required:
-
-```
-{
-  "Version": "2012-10-17",
-  "Statement": [
-    {
-      "Effect": "Allow",
-      "Action": [
-        "cloudformation:CreateStack",
-        "cloudformation:UpdateStack",
-        "cloudformation:DeleteStack",
-        "iam:PutRolePolicy"
-      ],
-      "Resource": "*",
-      "Condition": {
-        "StringEquals": {
-          "aws:RequestTag/CreatedBy": "EksMcpServer"
-        }
+For write operations, we recommend the following IAM policies to ensure successful deployment of EKS clusters using the CloudFormation template in `/awslabs/eks_mcp_server/templates/eks-templates/eks-with-vpc.yaml`:
+
+* [**IAMFullAccess**](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/IAMFullAccess.html): Enables creation and management of IAM roles and policies required for cluster operation
+* [**AmazonVPCFullAccess**](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AmazonVPCFullAccess.html): Allows creation and configuration of VPC resources including subnets, route tables, internet gateways, and NAT gateways
+* [**AWSCloudFormationFullAccess**](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AWSCloudFormationFullAccess.html): Provides permissions to create, update, and delete CloudFormation stacks that orchestrate the deployment
+* **EKS Full Access (provided below)**: Required for creating and managing EKS clusters, including control plane configuration, node groups, and add-ons
+   ```
+  {
+    "Version": "2012-10-17",
+    "Statement": [
+      {
+        "Effect": "Allow",
+        "Action": "eks:*",
+        "Resource": "*"
       }
-    }
-  ]
-}
-```
+    ]
+  }
+   ```
+
+
+**Important Security Note**: Users should exercise caution when `--allow-write` and `--allow-sensitive-data-access` modes are enabled with these broad permissions, as this combination grants significant privileges to the MCP server. Only enable these flags when necessary and in trusted environments. For production use, consider creating more restrictive custom policies.
+
+### Kubernetes API Access Requirements
+
+All Kubernetes API operations will only work when one of the following conditions is met:
+
+1. The user's principal (IAM role/user) actually created the EKS cluster being accessed
+2. An EKS Access Entry has been configured for the user's principal
+
+If you encounter authorization errors when using Kubernetes API operations, verify that an access entry has been properly configured for your principal.
 
 ## Quickstart
 
@@ -90,6 +96,30 @@ This quickstart guide walks you through the steps to configure the Amazon EKS MC
 2. Click the gear icon (⚙️) in the top right to open the settings panel, click **MCP**, **Add new global MCP server**.
 3. Paste your MCP server definition. For example, this example shows how to configure the EKS MCP Server, including enabling mutating actions by adding the `--allow-write` flag to the server arguments:
 
+   **For Mac/Linux:**
+
+	```
+	{
+	  "mcpServers": {
+	    "awslabs.eks-mcp-server": {
+	      "autoApprove": [],
+	      "disabled": false,
+	      "command": "uvx",
+	      "args": [
+	        "awslabs.eks-mcp-server@latest",
+	        "--allow-write"
+	      ],
+	      "env": {
+	        "FASTMCP_LOG_LEVEL": "ERROR"
+	      },
+	      "transportType": "stdio"
+	    }
+	  }
+	}
+	```
+
+   **For Windows:**
+
 	```
 	{
 	  "mcpServers": {
@@ -98,7 +128,9 @@ This quickstart guide walks you through the steps to configure the Amazon EKS MC
 	      "disabled": false,
 	      "command": "uvx",
 	      "args": [
+	        "--from",
 	        "awslabs.eks-mcp-server@latest",
+	        "awslabs.eks-mcp-server.exe",
 	        "--allow-write"
 	      ],
 	      "env": {
@@ -119,6 +151,8 @@ This quickstart guide walks you through the steps to configure the Amazon EKS MC
 1. Install the [Amazon Q Developer CLI](https://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/command-line-installing.html) .
 2. The Q Developer CLI supports MCP servers for tools and prompts out-of-the-box. Edit your Q developer CLI's MCP configuration file named mcp.json following [these instructions](https://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/command-line-mcp-configuration.html). For example:
 
+   **For Mac/Linux:**
+
 	```
 	{
 	  "mcpServers": {
@@ -135,6 +169,24 @@ This quickstart guide walks you through the steps to configure the Amazon EKS MC
 	}
 	```
 
+   **For Windows:**
+
+	```
+	{
+	  "mcpServers": {
+	    "awslabs.eks-mcp-server": {
+	      "command": "uvx",
+	      "args": ["--from", "awslabs.eks-mcp-server@latest", "awslabs.eks-mcp-server.exe"],
+	      "env": {
+	        "FASTMCP_LOG_LEVEL": "ERROR"
+	      },
+	      "autoApprove": [],
+	      "disabled": false
+	    }
+	  }
+	}
+	```
+
 3. Verify your setup by running the `/tools` command in the Q Developer CLI to see the available EKS MCP tools.
 
 Note that this is a basic quickstart. You can enable additional capabilities, such as [running MCP servers in containers](https://github.com/awslabs/mcp?tab=readme-ov-file#running-mcp-servers-in-containers) or combining more MCP servers like the [AWS Documentation MCP Server](https://awslabs.github.io/mcp/servers/aws-documentation-mcp-server/) into a single MCP server definition. To view an example, see the [Installation and Setup](https://github.com/awslabs/mcp?tab=readme-ov-file#installation-and-setup) guide in AWS MCP Servers on GitHub. To view a real-world implementation with application code in context with an MCP server, see the [Server Developer](https://modelcontextprotocol.io/quickstart/server) guide in Anthropic documentation.
@@ -145,13 +197,36 @@ Note that this is a basic quickstart. You can enable additional capabilities, su
 
 The `args` field in the MCP server definition specifies the command-line arguments passed to the server when it starts. These arguments control how the server is executed and configured. For example:
 
+**For Mac/Linux:**
+```
+{
+  "mcpServers": {
+    "awslabs.eks-mcp-server": {
+      "command": "uvx",
+      "args": [
+        "awslabs.eks-mcp-server@latest",
+        "--allow-write",
+        "--allow-sensitive-data-access"
+      ],
+      "env": {
+        "AWS_PROFILE": "your-profile",
+        "AWS_REGION": "us-east-1"
+      }
+    }
+  }
+}
+```
+
+**For Windows:**
 ```
 {
   "mcpServers": {
     "awslabs.eks-mcp-server": {
       "command": "uvx",
       "args": [
+        "--from",
         "awslabs.eks-mcp-server@latest",
+        "awslabs.eks-mcp-server.exe",
         "--allow-write",
         "--allow-sensitive-data-access"
       ],
@@ -164,11 +239,17 @@ The `args` field in the MCP server definition specifies the command-line argumen
 }
 ```
 
-#### `awslabs.eks-mcp-server@latest` (required)
+#### Command Format
+
+The command format differs between operating systems:
 
-Specifies the latest package/version specifier for the MCP client config.
+**For Mac/Linux:**
+* `awslabs.eks-mcp-server@latest` - Specifies the latest package/version specifier for the MCP client config.
 
-* Enables MCP server startup and tool registration.
+**For Windows:**
+* `--from awslabs.eks-mcp-server@latest awslabs.eks-mcp-server.exe` - Windows requires the `--from` flag to specify the package and the `.exe` extension.
+
+Both formats enable MCP server startup and tool registration.
 
 #### `--allow-write` (optional)
 
@@ -362,24 +443,45 @@ Features:
 Parameters:
 
 * cluster_name, log_type (application, host, performance, control-plane, custom), resource_type (pod, node, container, cluster),
-resource_name, minutes (optional), start_time (optional), end_time (optional), limit (optional), filter_pattern (optional), fields (optional)
+resource_name (optional), minutes (optional), start_time (optional), end_time (optional), limit (optional), filter_pattern (optional), fields (optional)
 
 #### `get_cloudwatch_metrics`
 
-Retrieves metrics from CloudWatch for a specific EKS cluster resource.
+Retrieves metrics from CloudWatch for Kubernetes resources.
 
 Features:
 
-* Fetches metrics based on resource type (pod, node, container, cluster), resource name, and metric name.
-* Allows specification of CloudWatch namespace, Kubernetes namespace, and time range.
+* Fetches metrics based on metric name and dimensions.
+* Allows specification of CloudWatch namespace and time range.
 * Configurable period, statistic (Average, Sum, etc.), and limit for data points.
 * Supports providing custom dimensions for fine-grained metric querying.
 
 Parameters:
 
-* cluster_name, metric_name, resource_type (pod, node, container, cluster), resource_name, namespace (optional), k8s_namespace
-(optional), minutes (optional), start_time (optional), end_time (optional), limit (optional), stat (optional), period (optional), custom_dimensions
- (optional)
+* cluster_name, metric_name, namespace, dimensions, minutes (optional), start_time (optional), end_time (optional), limit (optional), stat (optional), period (optional)
+
+#### `get_eks_metrics_guidance`
+
+Provides guidance on available CloudWatch metrics for different resource types in EKS clusters.
+
+Features:
+
+* Returns a list of available Container Insights metrics for the specified resource type, including metric names, dimensions, and descriptions.
+* Helps determine the correct dimensions to use with the `get_cloudwatch_metrics` tool.
+* Supports the following resource types:
+  * `cluster`: Metrics for EKS clusters (e.g., cluster_node_count, cluster_failed_node_count)
+  * `node`: Metrics for EKS nodes (e.g., node_cpu_utilization, node_memory_utilization, node_network_total_bytes)
+  * `pod`: Metrics for Kubernetes pods (e.g., pod_cpu_utilization, pod_memory_utilization, pod_network_rx_bytes)
+  * `namespace`: Metrics for Kubernetes namespaces (e.g., namespace_number_of_running_pods)
+  * `service`: Metrics for Kubernetes services (e.g., service_number_of_running_pods)
+
+Parameters:
+
+* resource_type
+
+Implementation:
+
+The data in `/awslabs/eks_mcp_server/data/eks_cloudwatch_metrics_guidance.json` is generated by a Python script (`/awslabs/eks_mcp_server/scripts/update_eks_cloudwatch_metrics_guidance.py`) that scrapes the [Container Insights metrics table](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Container-Insights-metrics-EKS.html) from AWS documentation. Running the script requires installing BeautifulSoup (used for parsing HTML content) with uv: `uv pip install bs4`.
 
 ### IAM Integration
 
@@ -466,6 +568,7 @@ The EKS MCP Server can be used for production environments with proper security
 
 An array within the MCP server definition that lists tool names to be automatically approved by the EKS MCP Server client, bypassing user confirmation for those specific tools. For example:
 
+**For Mac/Linux:**
 ```
 {
   "mcpServers": {
@@ -496,6 +599,39 @@ An array within the MCP server definition that lists tool names to be automatica
 }
 ```
 
+**For Windows:**
+```
+{
+  "mcpServers": {
+    "awslabs.eks-mcp-server": {
+      "command": "uvx",
+      "args": [
+        "--from",
+        "awslabs.eks-mcp-server@latest",
+        "awslabs.eks-mcp-server.exe"
+      ],
+      "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"
+      ]
+    }
+  }
+}
+```
+
 ### IAM Permissions Management
 
 When the `--allow-write` flag is enabled, the EKS MCP Server can create missing IAM permissions for EKS resources through the `add_inline_policy` tool. This tool enables the following:

awslabs_eks_mcp_server-0.1.3/awslabs/__init__.py

@@ -0,0 +1,16 @@
+# Copyright Amazon.com, Inc. or its affiliates. All Rights Reserved.
+#
+# Licensed under the Apache License, Version 2.0 (the "License");
+# you may not use this file except in compliance with the License.
+# You may obtain a copy of the License at
+#
+#     http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+
+# This file is part of the awslabs namespace.
+# It is intentionally minimal to support PEP 420 namespace packages.

awslabs_eks_mcp_server-0.1.3/awslabs/eks_mcp_server/__init__.py

@@ -0,0 +1,17 @@
+# Copyright Amazon.com, Inc. or its affiliates. All Rights Reserved.
+#
+# Licensed under the Apache License, Version 2.0 (the "License");
+# you may not use this file except in compliance with the License.
+# You may obtain a copy of the License at
+#
+#     http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+
+"""awslabs.eks-mcp-server"""
+
+__version__ = '0.1.0'