MyMCPTools
Guides7 min read

Best MCP Servers for DevOps: Kubernetes, Docker, Cloud & CI/CD

Top MCP servers for DevOps engineers. Manage Kubernetes clusters, Docker containers, cloud infrastructure, and CI/CD pipelines through your AI assistant.

By MyMCPTools Team·

DevOps workflows involve constant context-switching — between terminals, dashboards, documentation, and incident channels. MCP servers collapse this by giving your AI assistant direct access to your infrastructure tools.

Here's the essential MCP server stack for DevOps engineers.

Container & Orchestration Servers

Kubernetes MCP Server

The Kubernetes MCP server is arguably the highest-impact MCP server for DevOps. It transforms kubectl interactions into conversational commands, and more importantly, gives your AI the context to understand your cluster state.

What you can do:

  • List and inspect pods, deployments, services, and other resources
  • Check pod logs and events for debugging
  • Describe resources to understand configuration
  • Apply manifests (with appropriate caution)
  • Monitor resource usage and health

Real-world scenario: "Why is the payment service throwing 503s?" — Your AI checks the deployment, finds the pods are in CrashLoopBackoff, pulls the logs, identifies the failing health check, and suggests a fix. All in one conversation.

Docker MCP Server

Manage containers, images, and Docker Compose stacks through your AI. Particularly useful for local development environments and debugging container networking issues.

Key capabilities:

  • Container lifecycle management (start, stop, inspect, logs)
  • Image listing and management
  • Network and volume inspection
  • Docker Compose operations

Cloud Platform Servers

AWS MCP Server

AWS has a staggering number of services. The AWS MCP server helps by giving your AI direct access to inspect and manage resources across EC2, S3, Lambda, RDS, and more.

Best used for:

  • Debugging infrastructure issues across AWS services
  • Cost analysis and resource optimization
  • Security group and IAM policy review
  • CloudWatch log exploration

Terraform MCP Server

Infrastructure as Code gets an AI co-pilot. The Terraform MCP server understands your HCL files, state, and plan output — making it invaluable for reviewing infrastructure changes.

Best used for:

  • Reviewing terraform plan output with AI analysis
  • Understanding resource dependencies
  • Writing and validating HCL configurations
  • Drift detection and remediation

CI/CD Servers

GitHub Actions MCP Server

Combined with the GitHub MCP server, you get full visibility into your CI/CD pipelines. Check workflow runs, inspect failures, review logs, and debug flaky tests — all conversationally.

Real-world scenario: "Why did the deploy fail?" — AI checks the latest workflow run, finds the failing step, pulls the logs, identifies a dependency version mismatch, and opens a PR with the fix.

The DevOps MCP Stack

Here's the recommended combination for a complete DevOps AI workflow:

  1. Kubernetes MCP — Cluster management and debugging
  2. Docker MCP — Local container management
  3. AWS/GCP/Azure MCP — Cloud resource access
  4. Terraform MCP — Infrastructure as Code
  5. GitHub MCP — Code and CI/CD pipelines
  6. Filesystem MCP — Configuration files and scripts

Safety Considerations for DevOps MCP

DevOps MCP servers carry higher stakes than most — a misfire can take down production. Follow these safety rules:

  • Read-only by default — Start with read-only access. Add write/mutate capabilities only for specific, well-understood operations.
  • Never connect to production clusters without approval gates — Use MCP for staging and dev environments freely. Production should require explicit confirmation.
  • Audit log everything — Enable logging on your MCP servers to track what actions your AI takes on infrastructure.
  • Use separate credentials — Don't share your personal admin credentials with MCP servers. Create service accounts with minimal required permissions.

The Future of AI-Assisted DevOps

MCP is still early for infrastructure management, but the direction is clear. We're moving toward AI assistants that can:

  • Detect and respond to incidents autonomously
  • Optimize cloud costs by analyzing usage patterns
  • Generate and review infrastructure changes
  • Provide real-time system explanations during on-call

The MCP servers available today are the foundation for this future. Start integrating them into your workflow now to build the muscle memory and processes you'll need.

Browse all DevOps MCP servers and Cloud MCP servers in our directory.

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✓
☁️

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

Terraform MCP Server

The Terraform MCP Server is HashiCorp's official integration that brings Terraform's infrastructure-as-code capabilities into AI assistants via the Model Context Protocol. It connects Claude Desktop, Cursor, VS Code, and other MCP clients to the Terraform ecosystem — letting you explore providers, look up module schemas, validate configurations, and work with HCP Terraform (Terraform Cloud) all through natural-language conversation. Core tools include: search the Terraform Registry for modules and providers by keyword, retrieve full provider schema documentation including resource arguments and attribute types, look up specific module input/output variables and their defaults, resolve provider version constraints and compatibility matrices, and run Terraform operations against HCP Terraform workspaces including plan, apply, and state inspection. A key use case is AI-assisted IaC authoring: ask Claude to "generate a Terraform module for an AWS VPC with public and private subnets using the latest aws provider schema" and the server fetches the live provider schema to ensure accurate attribute names and types rather than hallucinating outdated syntax. For HCP Terraform users, workspace integration supports listing workspaces, triggering runs, and checking plan output. HashiCorp maintains the server at hashicorp/terraform-mcp-server and distributes it as a pre-built binary for Linux, macOS (arm64 + amd64), and Windows. Install via: `npx @hashicorp/terraform-mcp-server`. Pairs well with GitHub MCP for full IaC PR review workflows.

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✓

📚 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