Awesome Agentic DevOps

A curated, official-first catalog of MCP servers, agent skills, AI agents, frameworks, and supporting resources for DevOps, Cloud, SRE, and Platform Engineering. It includes vendor and open-source project resources alongside a clearly labeled community-driven section.

Most agent lists stop at discovery. This one is built for operators:

• Official-first, community-inclusive — 79 entries organized into 15 catalog sections; official vendor and project resources are prioritized, while community-driven entries are separated in a dedicated community section.
• Scored, not just listed — every entry records action capability, human-approval controls, tracing evidence, maturity, and operational risk (how entries are scored).
• Audited by CI — GitHub repository entries are checked weekly for reachability and archived status; non-GitHub documentation links are outside this automated check and require curator review.
• Installable, not just readable — one command installs hundreds of skills from cataloged Google, Microsoft, Azure, Azure DevOps, and Harness sources — plus a separate community set — into Claude Code, Cursor, Codex, VS Code, or Antigravity.
• Runnable, not just theoretical — documented reference-agent examples cover Terraform plan review, drift detection, and policy-driven container image releases.

Safety first: some cataloged tools and agents can change infrastructure. Prefer read-only or proposal mode, require human approval before write actions, and use least-privilege credentials — full guidance in the safety model.

Contents

• Evaluation labels
• Compliance evidence checklist
• Top picks by use case
• Install skills into your coding agent
• Recently added
• Local reference agents
• Curated catalog
• How to contribute

Evaluation labels

Labels are shorthand for structured fields recorded on every entry in data/repos.yaml — how entries are scored explains each field and how it is verified.

Compliance evidence checklist

Production-adjacent agent runs need a reviewable evidence packet, not just a chat transcript. Use the compliance evidence checklist to capture request context, identity and data boundaries, redacted tool calls, approval records, validation output, and follow-ups for MCP servers, skills, incident copilots, Terraform reviewers, and other DevOps agents.

At minimum, record an explicit approval before any write-capable agent mutates infrastructure, source control, CI/CD, identity, secrets, incidents, or production telemetry configuration. If the approval cannot be captured, keep the agent in read-only or proposal mode.

Top picks by use case

Install skills into your coding agent

I