MyMCPTools
Guides8 min read

Best MCP Servers for Docker and Kubernetes in 2026

Container orchestration is complex enough without context-switching. These MCP servers give your AI direct access to Docker, Kubernetes, Helm, and your observability stack — so debugging happens in conversation.

By MyMCPTools Team·

Kubernetes is notoriously complex. Between deployments, services, ingress rules, resource limits, and rolling updates, there's an enormous amount of state to track — spread across namespaces, clusters, and config files. Most of that context never makes it into your AI conversation.

MCP servers fix that. With the right setup, your AI assistant can inspect running pods, read Helm values, check Prometheus metrics, and tail logs from Grafana without you switching terminals. Here are the best MCP servers for Docker and Kubernetes workflows in 2026.

1. Kubernetes MCP Server — Your Cluster, AI-Accessible

The Kubernetes MCP server is the essential foundation for any container-heavy team. It exposes the Kubernetes API to your AI — pods, deployments, services, configmaps, events, and more — all queryable in natural language.

Key capabilities:

  • List and describe pods, deployments, services, and ingresses
  • Read pod logs and events across namespaces
  • Check resource requests, limits, and node capacity
  • Apply and patch manifests via kubectl-compatible commands

Best for: Platform engineers and SREs who want AI to help triage pod failures, explain CrashLoopBackOff errors, or identify resource-constrained nodes. Ask "why is my pod restarting?" and get a real answer based on live cluster state.

2. Docker MCP Server — Container Visibility Without the Terminal

Before production, everything runs in Docker. The Docker MCP server gives your AI access to running containers, images, volumes, and networks — locally or against a remote daemon.

Key capabilities:

  • List running and stopped containers with status
  • Read container logs and inspect configurations
  • Manage images (pull, tag, push) and volumes
  • Execute commands inside containers

Best for: Developers debugging local Docker setups and DevOps engineers managing Docker-based CI environments. Pair with the Filesystem MCP server to let AI read your Dockerfiles alongside live container output.

3. Helm MCP Server — Chart Management AI Can Navigate

Helm manages Kubernetes application packaging. The Helm MCP server exposes your releases, values, and chart templates to your AI — making it much easier to understand what's deployed and why it's configured that way.

Key capabilities:

  • List Helm releases and their status
  • Read values.yaml and rendered templates
  • Inspect chart hooks, notes, and NOTES.txt
  • Diff values between revisions

Best for: Platform teams managing multiple Helm releases who want AI to explain configuration differences between environments, or identify which release controls a specific service.

4. Argo CD MCP Server — GitOps Pipeline Intelligence

Argo CD is the GitOps deployment engine for Kubernetes. The Argo CD MCP server lets your AI check application sync status, health, and deployment history without opening the Argo dashboard.

Key capabilities:

  • List applications and their sync/health status
  • Read deployment history and revision diffs
  • Trigger sync operations (with appropriate permissions)
  • Inspect resource tree and current live state

Best for: GitOps teams who want AI to explain why an app is out-of-sync, identify the last successful deployment, or help debug degraded application health.

5. Prometheus MCP Server — Metrics Your AI Can Query

Prometheus collects your cluster metrics. The Prometheus MCP server makes those metrics queryable through your AI conversation — CPU, memory, request rates, error rates, latency percentiles.

Key capabilities:

  • Execute PromQL queries and return results
  • List available metrics and their labels
  • Query time-series data for trending analysis
  • Evaluate alert rules and their current state

Best for: SREs and platform engineers who want to ask "what's the current error rate for the payments service?" and get a real number from Prometheus rather than guessing from dashboards.

6. Grafana MCP Server — Dashboard Data in Conversation

Grafana visualizes your observability data. The Grafana MCP server extracts that data from dashboards and panels, making it available in your AI conversation without screenshot-based guesswork.

Key capabilities:

  • List dashboards and panels
  • Query panel data sources programmatically
  • Read dashboard annotations and alert rules
  • Export dashboard JSON for review or modification

Best for: Teams who want AI to read their Grafana dashboards and generate incident summaries or capacity reports based on current metrics.

7. Docker Compose MCP Server — Multi-Service Context

Most local development and staging environments use Docker Compose. The Docker Compose MCP server gives your AI visibility into your compose configurations — services, dependencies, volumes, and environment variables.

Key capabilities:

  • Read docker-compose.yml and override files
  • List defined services and their configurations
  • Check service dependency graphs
  • Inspect environment variable definitions

Best for: Developers working on multi-service applications locally who want AI to understand the full service topology before debugging networking issues between containers.

8. Datadog MCP Server — APM and Infrastructure in One

Datadog combines logs, metrics, traces, and APM. The Datadog MCP server is particularly powerful for Kubernetes environments because it surfaces application-level performance data alongside infrastructure metrics.

Key capabilities:

  • Query metrics and logs with Datadog's query language
  • Read APM trace data and service maps
  • List monitors and their alert status
  • Access infrastructure host and container data

Best for: Engineering teams using Datadog for full-stack observability who want AI to help triage incidents by correlating pod logs, APM traces, and infrastructure metrics simultaneously.

Recommended Stacks by Role

  • Platform engineer: Kubernetes + Helm + Argo CD (full deployment stack context)
  • SRE / on-call: Kubernetes + Prometheus + Grafana (cluster state + metrics + dashboards)
  • Backend developer: Docker + Docker Compose + Sentry (local containers + error tracking)
  • DevOps generalist: Kubernetes + Helm + Datadog (K8s + releases + observability)
  • Full platform team: All 8 — Kubernetes is complex enough to warrant every layer of context

Browse all DevOps MCP servers on MyMCPTools. For cloud infrastructure context alongside your container stack, see Best MCP Servers for AWS and Best MCP Servers for Cloud Engineers.

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

🔧

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✓
🔧

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
🔧

Helm

Kubernetes package manager MCP server. Install, upgrade, and roll back Helm charts. Inspect release history, manage repositories, and debug chart templates.

Local✓
🔧

Argo CD

Declarative GitOps continuous delivery for Kubernetes. Manage applications, sync deployments, inspect health status, and rollback releases via AI.

Local✓
🔧

Prometheus

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

Local✓
📊

Grafana MCP Server

The official Grafana MCP server connects Claude and other AI assistants directly to your Grafana instance and its surrounding observability ecosystem, turning natural-language questions into dashboard lookups, incident investigations, and datasource queries. Dashboard tools cover search, retrieval, JSONPath-scoped property extraction, patch-based editing, and per-panel query/datasource introspection, with context-window-aware helpers like get_dashboard_summary so an agent never has to pull a full multi-megabyte dashboard JSON just to answer a simple question. Query tools speak PromQL against Prometheus (including histogram-percentile helpers), LogQL against Loki, and native query languages for InfluxDB, ClickHouse, CloudWatch, Graphite, Athena, Snowflake, Elasticsearch/OpenSearch, and Quickwit datasources — most gated behind opt-in --enabled-tools flags to keep the default tool surface lean. It also wraps Grafana Incident for creating and updating incidents, Sift for automated error-pattern and slow-request investigations, full alerting CRUD (rules, contact points, notification policies) across Grafana-managed and external Alertmanager sources, Grafana OnCall schedule/shift/alert-group management, RBAC-gated admin tools for teams/users/roles, deeplink generation so the LLM never has to guess a dashboard URL, annotations, snapshots, PNG rendering via the Grafana Image Renderer, and provisioning-repo validation for git-sync workflows. Ships as a Go binary or via uvx, authenticates with a Grafana service account token (Editor role or granular RBAC scopes), and every tool category can be individually disabled to control context-window usage.

Local✓
🔧

Docker Compose

Manage multi-container Docker applications with Compose MCP. Start, stop, and scale services, inspect container logs, and manage service dependencies.

Local
🔧

Kubernetes Dashboard

Advanced Kubernetes cluster management MCP. Manage namespaces, deployments, services, ingresses, and custom resources beyond what the basic kubectl server offers.

Local
📊

Datadog MCP Server

The Datadog MCP Server is Datadog's official Model Context Protocol integration that connects AI assistants directly to your Datadog observability platform — metrics, logs, APM traces, infrastructure, and monitors. Built and maintained by Datadog, the server uses your API and application keys to expose tools for querying live time-series metrics with full DQL expressions, searching log events with Datadog Log Management query syntax, retrieving distributed APM traces and service performance summaries, listing infrastructure hosts and their tags, and checking the status of Datadog monitors and downtime windows. This gives Claude real-time visibility into your production systems: ask "What's the p99 latency for the payments service over the last hour?" or "Find all ERROR-level logs from the auth service since the last deploy," and receive answers backed by live Datadog data rather than stale dashboards. Authentication requires a Datadog API key (DD_API_KEY) and an Application key (DD_APP_KEY) with appropriate scope — both available from Organization Settings > API Keys and Application Keys in the Datadog UI. Set DD_SITE to your Datadog region (e.g., datadoghq.com, datadoghq.eu, or us3.datadoghq.com). Works with Claude Desktop, Cursor, Windsurf, and any MCP-compatible client. Especially powerful for SRE, DevOps, and on-call workflows where engineers need AI to correlate metrics, logs, and traces during incident response without context-switching away from their conversation.

Local✓
🔧

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✓

📚 More from the Blog

Guides

Best MCP Servers for Developers in 2026: The Complete Guide

Discover the top MCP servers that every developer should know about. From filesystem access to database queries, these Model Context Protocol servers supercharge your AI coding workflow.

8 min readGuides

Best MCP Servers for Data Engineering: Database, ETL & Analytics

Top MCP servers for data engineers and analysts. Connect your AI to PostgreSQL, BigQuery, Snowflake, and more for AI-powered data workflows.

7 min readTutorials

Getting Started with MCP: A Beginner's Guide to Model Context Protocol

New to MCP? Learn what Model Context Protocol is, how it works, and how to set up your first MCP server in under 5 minutes. Complete beginner's guide.

10 min read