k8s-mcp-server

danoliver1/k8s-mcp-server

3.1

If you are the rightful owner of k8s-mcp-server and would like to certify it and/or have it hosted online, please leave a comment on the right or send an email to henry@mcphub.com.

This Kubernetes MCP server allows GitHub Copilot to access and interact with Kubernetes cluster metadata, aiding in debugging and troubleshooting.

Kubernetes MCP Server

This MCP server enables GitHub Copilot to access Kubernetes cluster metadata for debugging and troubleshooting. It provides comprehensive tools for monitoring pods, deployments, services, external secrets, autoscaling, policy compliance, and overall namespace health.

Capabilities

  • Core Resources: Pods, deployments, services, namespaces, nodes, and events
  • External Secrets: Monitor secret synchronisation and provider connectivity
  • KEDA Autoscaling: Debug autoscaling behaviour and trigger issues
  • Policy Compliance: Check Kyverno policy reports and security violations
  • Health Monitoring: Comprehensive namespace health checks with detailed status reports

Demo

https://github.com/user-attachments/assets/c1b270b6-1709-499b-88b7-9499f8401369

Setup

Architecture

For maximum portability, it runs locally as a Docker container. It works by mounting the .kube/config file to allow the Docker container to authenticate to Kubernetes using the same credential you use locally. It also mounts .aws/config for AWS EKS authentication, enabling it to work with both local and EKS clusters.

Configuration

This MCP server can be enabled for all VS Code instances or for just one project, based on the location of the .vscode/mcp.json file. More info: GitHub MCP Server Setup

Building

Note: currently the Docker image must be built locally because it is not pushed to a Docker registry yet.

docker build -t k8s-mcp-server .