MCP servers for DevOps and cloud
TL;DR
DevOps and cloud MCP servers expose infrastructure tooling — deployments, containers, cloud services, CI/CD — to an agent. These often carry write and permissions capability, making them high-risk surfaces that require strong least-privilege control.
What they expose
Depending on the server, an agent could query or change infrastructure state. Read-only queries carry low risk; mutating operations carry high risk.
Contain the access
Limit the tool surface, the credentials, and the scope of what a DevOps server may touch. Prefer credentials bound to a narrow role.
In this collection
- Best MCP servers →
- How to choose an MCP server →
- Verified MCP servers →
- MCP server comparison methodology →
- MCP registries, directories, and marketplaces →
- MCP servers for databases →
- Read-only database access with MCP →
- MCP servers for developers →
- MCP browser automation →
- MCP servers for search and research →
- MCP servers for productivity →
- Enterprise MCP →
- Postgres MCP server guide →
- Playwright MCP →
- MCP server not showing in Claude Desktop →
- Cursor MCP tools not showing →
- MCP connection refused and timeout errors →
- Claude Desktop MCP configuration →
- VS Code MCP configuration →
- Remote MCP servers with OAuth →
- MCP server for GitHub →