awesome s-devops

This repository is a curated collection of MCP (Model Context Protocol) servers for DevOps workflows. It does not itself run as a single MCP server but aggregates links to multiple MCP implementations across source control platforms. To use it, browse the sections to identify servers that align with your needs (e.g., Source Control, Infrastructure as Code, Kubernetes, CI/CD, Observability, Security). Each listed item points to an MCP server implementation with its own capabilities, such as repository operations, IaC tooling, cloud integrations, or monitoring and security tasks. When you find a server you want to try, visit the linked repo to review its installation instructions and usage details. You can also use this page as a jumping-off point to discover community variations and forks of MCP server implementations for DevOps workflows.

Prerequisites:

• Git installed on your machine
• Internet access to clone repositories
• Optional: Node.js, Python, or other runtimes depending on the MCP server you choose to run from the list

Step-by-step:

1. Clone this curated repository to your local machine

git clone https://github.com/WagnerAgent/awesome-mcp-servers-devops.git
cd awesome-mcp-servers-devops

2. Explore the sections in the README to identify MCP servers that match your tooling (e.g., Terraform MCP server, Kubernetes MCP server, GitHub/GitLab MCP servers).
3. For each MCP server you want to try, follow the installation instructions provided in that server’s own repository. Each server will have its own prerequisites and run commands.
4. If you simply want to browse offline, you can read the README locally or open the linked repos in your browser to get started with configuration and usage details.

Note: Since this repository is a curated list rather than a single runnable server, there is no single install command or runtime to execute from this repo itself. Each MCP server linked within has its own installation flow.

Tips:

• The page aggregates MCP servers across many categories (e.g., Source Control, IaC, Kubernetes, CI/CD, Cloud, Observability, Security). Use the repository links to evaluate compatibility with your tech stack.
• Some MCP servers require specific platform versions (e.g., GitHub/GitLab API changes, Terraform versions). Always check the upstream docs for version compatibility.
• If you contribute a new MCP server, ensure you provide clear usage, prerequisites, and environment variables in your repository so users can onboard quickly.
• Consider security implications (e.g., lockdown modes, secrets handling) as highlighted in the curated list for related projects.