awesome-mcp-servers-devops — DevOps MCP Servers List

Main

• Use the “Getting Started” section to pick one workflow (e.g., GitHub + Kubernetes) and stand it up end-to-end first.

• Prefer official servers when available; treat community servers as evaluative and verify permissions/safety modes.

• Keep a shortlist per environment: local dev vs CI vs production—tooling needs and guardrails differ.

• When testing servers, log tool calls and measure latency so agent workflows stay predictable.

README (excerpt)

Awesome MCP Servers for DevOps

A curated list of Model Context Protocol servers for DevOps workflows — infrastructure, CI/CD, monitoring, security, and cloud operations.

Curated by Wagner — The first AI DevOps teammate

Star History

Contents

• Source Control
• Infrastructure as Code
• Kubernetes and Containers
• Command Line and Local Ops
• Browser Automation
• Code Execution
• Coding Agents
• Aggregators
• CI/CD
• Cloud Platforms
• Observability
• Security
• Collaboration
• Getting Started

🔀 Source Control

GitHub

The official GitHub MCP server — battle-tested and feature-complete.

Community options

GitLab

Native GitLab integration via their Duo platform.

Source-backed notes

• README positions the repo as a DevOps-focused MCP server list with sections like Source Control, IaC, Kubernetes, CI/CD, Observability, and Security.
• README contains a “Getting Started” section to help readers onboard MCP servers.
• GitHub metadata verifies CC0-1.0 license, stars, and last push date for attribution.

FAQ

• Is this a server itself?: No—it's a curated list. You still install each MCP server from its own repo.
• How should I choose one?: Start from your bottleneck (Git/K8s/observability) and prioritize official or read-only modes.
• How do I avoid risky tool calls?: Use servers that support permissions/guardrails and test in a sandbox first.