MCP servers for a DevOps agent
The MCP server bundle to build an AI that ships code and watches the systems it runs on.
3 servers · ~29 tools · Last updated June 17, 2026
TL;DR: A DevOps agent spans the lifecycle: source control, the infrastructure it deploys to, and the telemetry that tells it what's happening in production. This bundle wires all three together. Scope every credential tightly — this agent has reach.
Bottom line: start with GitHub MCP Server and add the rest as your needs grow. All 3 install together via the merged config below (~29 tools total).
Tool budget: this stack exposes about 29 tools. That's within Cursor's practical ~40-tool ceiling, so all servers can stay enabled together. Check your own config →
What's in the stack
Query metrics, logs and monitors to see production health.
Source ↗One-click config
All 3 servers merged into a single block — pick your client and paste.
{
"mcpServers": {
"github-mcp-server": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"GITHUB_PERSONAL_ACCESS_TOKEN",
"ghcr.io/github/github-mcp-server"
],
"env": {
"GITHUB_PERSONAL_ACCESS_TOKEN": "<your-github-pat>"
}
},
"kubernetes-mcp-server": {
"command": "npx",
"args": [
"-y",
"mcp-server-kubernetes"
],
"env": {
"ALLOW_ONLY_NON_DESTRUCTIVE_TOOLS": "true"
}
},
"datadog-mcp-server-official-remote": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.datadoghq.com/api/unstable/mcp-server/mcp"
]
}
}
}Paste into ~/Library/Application Support/Claude/claude_desktop_config.json and fully restart Claude Desktop. Replace any placeholder keys/tokens with your own.
Capabilities this stack covers
FAQ
Is a DevOps agent risky?
It can be — it touches infra and source. Use least-privilege tokens, prefer read/plan operations, and gate destructive actions behind human approval.
Can I add Terraform or Docker?
Yes — Terraform and Docker servers slot in if your workflow uses them. See the deploy-cloud-infra capability for options.