"kubernetes" matching MCP servers:

Enables MCP clients to inspect and operate Kubernetes clusters across multiple contexts, with read-only/read-write/admin access modes and security flags controlling namespaces, contexts, deletes, applies, and exec.

MCP server that gives AI assistants full access to Kubernetes clusters and Helm, exposing 73 tools for managing pods, deployments, services, configs, secrets, logs, exec, port-forwarding, Helm lifecycle, and more.

Manages Kubernetes clusters through kubectl and Helm operations including pod cleanup, node management, and troubleshooting.

Enables connection to a Kubernetes cluster to list and manage pods, services, deployments, and nodes, create/delete/describe pods, inspect namespaces, and retrieve logs for debugging.

Enables connecting to a Kubernetes cluster through kubectl context to list and manage pods, services, deployments, nodes, and namespaces, create or delete pods, describe pods, and retrieve logs for debugging.

Enables connection to a Kubernetes cluster to list and manage pods, services, deployments, nodes, and namespaces, including creating, deleting, describing pods and retrieving logs for debugging.

Enables connecting to a Kubernetes cluster to manage resources and troubleshoot workloads with kubectl and Helm operations, including logs, scaling, port forwarding, and non-destructive mode.

TypeScript implementation of Kubernetes cluster operations for pods, deployments, services.

Connects to a Kubernetes cluster through the current kubectl context and enables listing, creating, deleting, and describing pods, services, deployments, nodes, and namespaces, plus retrieving logs for debugging.

Enables connecting to a Kubernetes cluster to manage it, including listing pods, services, deployments, nodes, and namespaces, creating and deleting pods, describing pods, and retrieving logs for debugging.

Connects to a Kubernetes cluster using your current kubectl context, letting an assistant list pods, services, deployments, nodes, and namespaces, create, delete, and describe pods, and pull logs for debugging. It turns everyday cluster management into natural-language tool calls.

Enables comprehensive Kubernetes cluster management through kubectl operations, Helm chart deployments, pod troubleshooting, and node management. Supports both read-only and full cluster administration capabilities with built-in safety features.

Enables AI assistants to manage Docker containers and Kubernetes resources through natural language, supporting operations like container management, image building, and pod/deployment/service management.

An MCP server that gives AI assistants direct access to Kubernetes clusters for pod management and network debugging (DNS, NetworkPolicy, ingress, service mesh) and correlates Dynatrace observability with OpenTelemetry self-monitoring, which automatically ships traces, metrics, and logs to Dynatrace.

Provides Kubernetes cluster management capabilities through natural language via MCP protocol over HTTP/SSE. Supports Pod, Service, Deployment operations, log retrieval, and resource management with JWT authentication and RBAC permissions.

Connects Claude Desktop to any Kubernetes cluster, enabling natural language queries for diagnostics and operations such as listing pods, viewing logs, scaling deployments, and more.

Enables AI agents to interact with Kubernetes clusters through progressive disclosure, where agents discover TypeScript modules via filesystem, write and execute code, and receive summarized console output for cluster management tasks.

Exposes a Kubernetes cluster to MCP-compatible AI clients, enabling read-only and optional write operations on cluster resources like pods, deployments, and namespaces through natural language.

A satirical MCP server that diagnoses Kubernetes incidents through theological doctrine and provides real kubectl remediation steps.

A read-only server that enables AI agents to triage Kubernetes CronJobs in a single tool call: whether runs happened and stayed on schedule, whether durations are trending slower or overrunning, which jobs have silently stopped succeeding, and why a given run failed, with evidence and stated basis for each verdict. It also lists active runs and recent failures while enforcing namespace allowlists and no write access.