Awesome DevOps MCP Servers

Created By
derisk-aia year ago
MCPServers in the DevOps domain.
Overview

What is Awesome DevOps MCP Servers?

Awesome DevOps MCP Servers is a curated list of Model Context Protocol (MCP) servers designed for DevOps workflows, enabling AI models to interact with resources securely.

How to use Awesome DevOps MCP Servers?

Users can explore the repository on GitHub to find various MCP servers categorized by their functionalities, such as Infrastructure as Code, CI/CD, and Monitoring.

Key features of Awesome DevOps MCP Servers?

  • Comprehensive list of production-ready and experimental MCP servers.
  • Categorization of servers based on their use cases (e.g., CI/CD, monitoring).
  • Links to official implementations and codebases in various programming languages.

Use cases of Awesome DevOps MCP Servers?

  1. Managing infrastructure as code with Terraform MCP servers.
  2. Executing CI/CD pipelines using ArgoCD and Jenkins MCP servers.
  3. Monitoring applications with Prometheus and Grafana MCP servers.

FAQ from Awesome DevOps MCP Servers?

  • What is MCP?

MCP stands for Model Context Protocol, which allows AI models to interact with resources through standardized server implementations.

  • Are these servers production-ready?

Yes, the list includes both production-ready and experimental servers for various DevOps tasks.

  • Where can I find more information?

You can find more information and the complete list of servers on the GitHub repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
derisk-ai
Star
1
Language
-
License
MIT license

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago