Awesome DevOps MCP Servers

Created By
rohitg00a year ago
A curated list of awesome MCP servers focused on DevOps tools and capabilities.
Overview

What is Awesome DevOps MCP Servers?

Awesome DevOps MCP Servers is a curated list of Model Context Protocol (MCP) servers that focus on enhancing DevOps tools and capabilities through AI integration.

How to use Awesome DevOps MCP Servers?

Users can explore the list of MCP servers available on the GitHub repository, where they can find links to various implementations and resources related to DevOps.

Key features of Awesome DevOps MCP Servers?

  • Comprehensive collection of MCP servers tailored for DevOps.
  • Categorization of servers based on functionality (e.g., cloud infrastructure, container orchestration, version control).
  • Links to official implementations and community resources.

Use cases of Awesome DevOps MCP Servers?

  1. Automating cloud infrastructure management using MCP servers.
  2. Enhancing CI/CD pipelines with AI-driven tools.
  3. Integrating AI assistants with Kubernetes for easier management.

FAQ from Awesome DevOps MCP Servers?

  • What is MCP?

MCP stands for Model Context Protocol, which allows AI models to interact with local and remote resources securely.

  • How can I contribute to this project?

Contributions are welcome! Please refer to the contribution guidelines in the repository.

  • Is there a license for this project?

Yes, this project is licensed under the MIT License.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
rohitg00
Star
13
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.

9 minutes ago