Guides8 min read

Best MCP Servers for Kubernetes & Cloud-Native Operations in 2026

The essential MCP servers for Kubernetes engineers and platform teams: cluster management, observability, container ops, cloud infrastructure, and incident response — all from your AI workflow.

By MyMCPTools Team·

Kubernetes engineers operate complex distributed systems where the gap between asking a question and getting an answer is usually "write a kubectl command, parse YAML, cross-reference Grafana, check Slack." MCP servers collapse that gap — your AI assistant can query your cluster, inspect metrics, check deployments, and pull incident context in a single conversation.

1. Kubernetes MCP Server — Cluster Operations in Plain Language

The Kubernetes MCP server is the core of any cloud-native AI workflow. It gives your AI assistant direct access to your cluster state via kubectl-equivalent operations — without you running commands or parsing YAML manually.

Key capabilities:

  • List and describe pods, deployments, services, and namespaces
  • Check pod logs and recent events
  • Apply and delete manifests
  • View resource usage and limits
  • Query ConfigMaps and Secrets (with proper RBAC)

K8s workflow: "Why is the payments-api pod in CrashLoopBackOff?" "List all pods in the production namespace with less than 10% CPU headroom." "Show me the last 100 lines of logs from the auth-service deployment."

2. Docker MCP Server — Container-Level Context

Before workloads reach Kubernetes, they run in Docker locally. During incidents, container-level inspection often reveals what cluster-level views miss. The Docker MCP server gives your AI assistant visibility into running containers, images, and compose stacks.

Key capabilities:

  • List and inspect running containers
  • View container logs and resource stats
  • Manage images and volumes
  • Control Docker Compose stacks

K8s workflow: "Is the local dev stack running correctly?" "Check the container logs for the database container in the staging compose stack." "Pull the latest api:main image and check its layer diff."

3. Prometheus MCP Server — Metrics Without the Dashboard

Every serious Kubernetes deployment runs Prometheus. The Prometheus MCP server gives your AI assistant the ability to query your metrics store using PromQL — so you can ask questions about system health without opening Grafana.

Key capabilities:

  • Execute PromQL queries against your Prometheus instance
  • List available metrics and labels
  • Retrieve time-series data for specific ranges
  • Check alert rules and their current state

K8s workflow: "What's the current p99 latency for the checkout-api?" "Is the error rate for any service above 1% right now?" "Show me the memory usage trend for the redis pod over the last 2 hours."

4. AWS MCP Server — Cloud Infrastructure Context

Most Kubernetes clusters run on EKS, with workloads connecting to RDS, S3, SQS, and other AWS services. The AWS MCP server gives your AI assistant access to your cloud infrastructure so you can diagnose cross-boundary issues.

Key capabilities:

  • Query EC2, EKS, RDS, S3, and Lambda resources
  • View CloudWatch logs and metrics
  • Check IAM policies and resource permissions
  • Monitor CloudFormation and CDK stack status

K8s workflow: "Is the RDS instance that payments-api connects to healthy?" "Check if the S3 bucket policy allows the EKS service account to write." "What's the disk throughput on the EKS node group that's hosting the slow pods?"

5. GitHub MCP Server — Code and Infrastructure Changes

Most Kubernetes incidents trace back to a recent code or config change. The GitHub MCP server gives your AI assistant visibility into what changed, when, and who approved it — the three most important questions during an incident.

Key capabilities:

  • View recent commits and their diffs
  • Browse Helm chart and Kubernetes manifest changes
  • Check PR approval status and review comments
  • Search for recent changes to specific files

K8s workflow: "What changed in the Helm values for payments-api in the last 24 hours?" "Who last modified the production-ingress.yaml and what did they change?" "Did any infrastructure PRs merge today before the incident started?"

6. Sentry MCP Server — Application Errors in Cluster Context

Kubernetes tells you a pod is crashing. Sentry tells you why. The Sentry MCP server surfaces application-level error data alongside your cluster operations context — so you can correlate infrastructure state with application behavior.

Key capabilities:

  • View recent errors grouped by frequency and impact
  • Read stack traces and error context
  • Check performance metrics and slow transactions
  • Search errors by service, environment, or release

K8s workflow: "Are there Sentry errors from payments-api that correlate with the CrashLoopBackOff start time?" "What's the error rate for the production environment right now?" "Show me the stack trace for the most frequent new error in the last hour."

7. Slack MCP Server — Incident Context and Communication

Incidents live in Slack — the initial alert, the response thread, the "we found it" moment. The Slack MCP server gives your AI assistant access to incident communication history so it can understand what's already been tried and who's working the problem.

Key capabilities:

  • Search messages and threads by keyword and date
  • Read incident channel history
  • Post status updates to channels

K8s workflow: "Summarize what happened in #incidents in the last 2 hours." "Post an incident update to #status: payments service is degraded, investigation underway." "What was the resolution for the last payments-api incident?"

The Cloud-Native MCP Stack

Priority order for Kubernetes teams:

  1. Kubernetes — cluster state and operations
  2. Prometheus — metrics and alerting
  3. GitHub — change causation
  4. Sentry — application errors
  5. Slack — incident communication

Add AWS/Docker based on your infrastructure. The goal is giving your AI assistant enough context to answer "what broke, when, and why" without you context-switching across five different dashboards during an incident.

Related guides:

Recommended Tools

Better Stack

Free Plan

Get alerted when your APIs, browser tests, payment pipelines, or MCP server dependencies go down. Used by 100K+ developers.

Start monitoring free →

1Password

14-day Free Trial

Store and inject API keys, payment credentials, tokens, and file access secrets into your MCP server configs. Trusted by 150K+ developers.

Try 1Password free →

🔧 MCP Servers Mentioned in This Article

🔧

Kubernetes MCP Server

The Kubernetes MCP server (mcp-server-kubernetes, built by Flux159) brings cluster management capabilities into AI assistant workflows, letting developers and platform engineers query and manage Kubernetes resources through natural-language interactions with Claude, Cursor, and other MCP-compatible clients. It loads your existing kubeconfig automatically, so it works with any cluster — local minikube and kind setups, Amazon EKS, Google GKE, Azure AKS, or on-premises deployments — with no separate credential setup required. Core tools exposed by the server include: listing pods, deployments, services, and namespaces; describing individual resources and their status; fetching pod logs for debugging; applying and updating manifests; scaling deployments; checking rollout status and history; and querying resource utilization and cluster events. A built-in non-destructive mode can disable delete/scale-down operations entirely, making it safe to point at production clusters for read-only diagnostics. DevOps engineers use it to debug failing deployments by asking Claude to inspect pod logs and recent events, identify resource constraints causing OOMKilled pods, or summarize the current state of a namespace before a production release. For SREs responding to incidents, it enables rapid triage through conversational commands — no memorizing kubectl flags or switching terminal windows mid-incident — and optional OpenTelemetry integration adds observability into what the AI agent actually did against the cluster. Install with: `npx mcp-server-kubernetes`. Pairs well with the GitHub MCP server for full GitOps review workflows.

Local
🔧

Docker MCP Server

The Docker MCP server connects your AI assistant directly to your local or remote Docker daemon, exposing container lifecycle management and image orchestration as Model Context Protocol tools. With this integration, developers can prompt Claude, Cursor, or Windsurf to inspect running containers, view real-time logs, build new images from Dockerfiles, start and stop services using Docker Compose, and prune unused system resources through natural language. Rather than switching to a terminal to type complex docker inspect commands, you can simply ask your AI to "find out why the postgres container keeps crashing" or "tail the last 100 lines of the frontend container logs and find the React error". This is a game-changer for DevOps engineers, backend developers, and system administrators who want to streamline container debugging, automate compose cluster orchestration, and troubleshoot networking issues faster. The server interacts securely with the Docker Engine API, meaning it can both read system state and execute commands like port binding or volume inspection. It works cross-platform wherever Docker Desktop or the Docker daemon is running. Docker's official implementation ships as the Docker MCP Gateway (docker/mcp-gateway), a `docker mcp` CLI plugin that acts as a single secure gateway in front of many containerized MCP servers from the Docker MCP Catalog — each downstream server runs in its own isolated container with resource limits and secret injection, so an assistant connects once to the gateway instead of wiring up dozens of individual servers. Start it with `docker mcp gateway run`, then point Claude Desktop, Cursor, or another client at the gateway; `docker mcp server enable <name>` toggles which catalog servers (including the Docker/container-management tools) are exposed. This container-per-server isolation is the key security benefit over running MCP servers directly on the host.

Local
🔧

Prometheus

Query Prometheus metrics using PromQL from AI assistants. Analyze time-series data, set up alerting rules, and monitor infrastructure performance.

Local
☁️

AWS MCP Servers

AWS Labs maintains a monorepo of specialized, open-source MCP servers that bring AWS best practices directly into AI-assisted development workflows, spanning infrastructure, data, AI/ML, cost management, and healthcare/life-sciences domains. Rather than one monolithic server, the project ships dozens of focused servers you install individually depending on the task: the AWS Documentation MCP Server for real-time official docs and API references, dedicated servers for Terraform/CDK/CloudFormation infrastructure-as-code, container and serverless platforms (ECS, EKS, Lambda), SQL/NoSQL databases (DynamoDB, RDS, Aurora), search and analytics (OpenSearch), messaging (SQS/SNS), and cost/billing analysis. Most servers install via uvx with a package name like awslabs.aws-documentation-mcp-server, run locally over stdio, and use standard AWS credential chains (IAM roles, profiles, or access keys) rather than exposing raw account credentials to the model. AWS also now offers a managed, remote "AWS MCP Server" (in preview) that combines full API coverage with pre-built agent SOPs, syntactically validated API calls, and complete CloudTrail audit logging for teams that want centralized governance instead of running servers locally. The Getting Started with Kiro/Cursor/VS Code/Claude Code sections in the repo provide one-click install configs for each server, making it straightforward to wire up only the AWS services a given project actually touches.

Local
💻

GitHub MCP Server

The GitHub MCP server is GitHub's official Model Context Protocol integration, giving AI assistants like Claude and Cursor direct, authenticated access to the GitHub platform and its full developer surface. With this MCP server, you can ask your AI to read and write repository files, create and merge branches, open and review pull requests, comment on and close issues, trigger GitHub Actions workflows, search across code repositories with GitHub's code search, and inspect commit history — all through natural-language prompts in your AI interface. Developers use it to supercharge code review workflows, automate issue triage, generate PR descriptions from diffs, bulk-update repository settings, and wire AI agents into CI/CD pipelines. The GitHub MCP server connects via a GITHUB_PERSONAL_ACCESS_TOKEN environment variable with scopes for the operations you need, keeping authentication clean and auditable. Install with Docker: `docker run -e GITHUB_PERSONAL_ACCESS_TOKEN=<token> ghcr.io/github/github-mcp-server` — or configure it as a remote MCP server in Claude Desktop, Cursor, VS Code, Windsurf, and Cline. With over 8,000 GitHub stars, it is the most widely deployed official code-platform MCP server and the reference implementation for AI-native GitHub automation.

Auth required
🔧

Sentry MCP Server

The Sentry MCP Server is Sentry's official Model Context Protocol integration, purpose-built for human-in-the-loop coding agents like Claude Code, Cursor, and Windsurf. Rather than exposing every Sentry API endpoint, it focuses tightly on developer debugging workflows: searching and triaging issues, pulling stack traces and event details, inspecting performance traces, and querying project/team/org metadata in natural language. The primary deployment is a hosted remote MCP server at mcp.sentry.dev, built on Cloudflare's remote-MCP infrastructure, so most users connect with zero local setup — just add the remote URL to their client. For self-hosted Sentry instances or local development, a stdio transport is also available via npx @sentry/mcp-server, authenticated with a Sentry User Auth Token scoped to org:read, project:read, project:write, team:read, team:write, and event:write. AI-powered search tools (search_events, search_issues) translate natural-language queries into Sentry's query syntax, but require a configured LLM provider (OpenAI, Azure OpenAI, Anthropic, or OpenRouter) — all other tools work without one. Claude Code users can also install it as a plugin (claude plugin install sentry-mcp@sentry-mcp) for automatic subagent delegation whenever a conversation touches Sentry errors, issues, or traces. This turns "why did this deploy break in production" into a direct conversational debugging session instead of tab-switching into the Sentry dashboard.

Auth required
💬

Slack MCP Server

The Slack MCP server (built by Ivan Korotovsky) connects AI assistants like Claude, Cursor, and Windsurf directly to Slack workspaces, enabling conversational access to your team communication channels without requiring workspace admin approval for a bot install. Its standout feature is a "no permission" stealth mode — it authenticates using your own personal Slack session tokens (xoxc/xoxd, or a stored browser session) rather than requiring a Slack App with OAuth scopes, so it works even in locked-down workspaces where you cannot create bots. It also supports full OAuth Bot Token auth and Enterprise/GovSlack deployments for teams that prefer a conventional app install. Tools exposed include reading channel and DM/group-DM history with smart pagination, searching messages across the workspace, posting messages and thread replies, listing channels and users, and adding reactions. Common use cases include automating standups by posting summaries directly to team channels, searching past Slack conversations to surface decisions or context, monitoring specific channels for keywords or alerts, and drafting replies to thread discussions — all from natural-language prompts. Supports both Stdio and SSE transports plus proxy configuration for corporate networks. Install with: `npx slack-mcp-server@latest --transport stdio`. A separate official-style integration exists from Zencoder (@zencoderai/slack-mcp-server) for teams that prefer standard Bot Token OAuth over session-token auth. Compatible with Claude Desktop, Cursor, VS Code, Windsurf, and Cline.

Local
📋

Linear MCP Server

The Linear MCP server connects your AI assistant directly to Linear's project management platform via an officially hosted remote endpoint at mcp.linear.app — no local installation required. This is Linear's own first-party server, authenticated with OAuth 2.1 and centrally managed so you always run the latest version without updates. Available tools let you search issues by keyword, team, cycle, or filter; create new issues with title, description, and assignee; update status, priority, labels, and comments; and navigate Linear's project and cycle structure. In Claude Code, add it with: `claude mcp add --transport http linear-server https://mcp.linear.app/mcp`, then run /mcp to complete the OAuth flow. For older clients, use the mcp-remote bridge for backwards compatibility. Claude Desktop and Claude.ai users can connect via Settings > Connectors. Cursor and Codex have native support via their MCP config. Linear is used by thousands of engineering and product teams to plan, track, and ship software — the Linear MCP server brings that data into every AI-powered workflow without copy-paste or context-switching.

Auth required

📚 More from the Blog