freemcplab / Directory / Playground / Awesome DevOps MCP Servers

● Community rohitg00 🔑 Needs your key

Awesome DevOps MCP Servers

Name: Awesome DevOps MCP Servers MCP Server
Author: rohitg00

by rohitg00 · rohitg00/awesome-devops-mcp-servers

Curated list of MCP servers focused on DevOps tools — cloud infra, CLI ops, version control, and security scanning.

Awesome DevOps MCP Servers is an MCP server maintained by rohitg00. Curated list of MCP servers focused on DevOps tools — cloud infra, CLI ops, version control, and security scanning. See the repo README for installation, auth, and configuration: https://github.com/rohitg00/awesome-devops-mcp-servers

▶ Watch demo 📦 Install 💡 Use Cases

Why use it

Key features

Curated list of MCP servers focused on DevOps tools — cloud infra, CLI ops, version control, and security scanning.
Language: Markdown
983+ GitHub stars at verification time
Community project

Live Demo

What it looks like in practice

awesome-devops-mcp-servers.replay ▶ ready

0/0

Install

Author repository · MCP documentation

Use Cases

Real-world ways to use Awesome DevOps MCP Servers

Use Awesome DevOps MCP Servers for its primary workflow

👤 Claude Code users / MCP clients ⏱ ~20 min intermediate

When to use: See repo README for canonical use cases.

Prerequisites

Server installed / connection details ready — See https://github.com/rohitg00/awesome-devops-mcp-servers

Flow

Configure

Provide credentials/config as instructed.✓ Copied

→ Successful auth/init
Use

Run a sample task with Awesome DevOps MCP Servers.✓ Copied

→ Expected output

Outcome: You can drive the documented workflow end-to-end.

Pitfalls

Skipping README — Read the repo README and CHANGELOG before shipping to prod.

Tools

What this MCP exposes

Tool	Inputs	When to call	Cost
primary	see README	Primary action	free

Cost & Limits

What this costs to run

API quota: Bounded by upstream provider quotas (if any)
Tokens per call: Depends on usage
Monetary: Open source — check repo LICENSE
Tip: Review upstream API costs (if any) before automating.

Security

Permissions, secrets, blast radius

Minimum scopes: Whatever the upstream provider requires

Credential storage: Env vars or local config — never commit secrets

Data egress: Forwards data per its README

Never grant: Full admin to untrusted prompts

Project moves fast — pin a version in production.

Troubleshooting

Common errors and fixes

Auth fails

Verify credentials and required scopes match README.

Verify: Re-read repo README auth section.

Tool not found by client

Ensure MCP client config points to correct command/path.

Verify: Restart the client after editing config.

Resources

📖 Read the official README on GitHub

🐙 Browse open issues

🔍 Browse all 400+ MCP servers and Skills