mcp-devops-server
Allows listing Docker containers and retrieving container logs.
Allows listing Helm releases and previewing Helm upgrade changes.
Allows getting and describing Kubernetes resources, and retrieving pod logs.
Allows running terraform plan and showing terraform state.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-devops-server show me all pods in the default namespace"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mcp-devops-server
An MCP (Model Context Protocol) server that gives AI agents access to DevOps tools — kubectl, terraform, helm, docker, and AWS cost analysis.
Works with Claude Desktop, Cursor, GitHub Copilot, and any MCP-compatible client.
Tools
Tool | Description |
| Get Kubernetes resources |
| Describe a Kubernetes resource |
| Get pod logs |
| Run terraform plan |
| Show terraform state |
| List Helm releases |
| Preview Helm upgrade changes |
| List Docker containers |
| Get container logs |
| Get AWS cost summary (last 7/30 days) |
| List AWS resources by service |
Related MCP server: K8s MCP Server
Installation
Using npx (no install)
npx @basel5001/mcp-devops-serverGlobal install
npm install -g @basel5001/mcp-devops-server
mcp-devops-serverFrom source
git clone https://github.com/basel5001/mcp-devops-server.git
cd mcp-devops-server
npm install
npm run build
npm startConfiguration
Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"devops": {
"command": "npx",
"args": ["-y", "@basel5001/mcp-devops-server"]
}
}
}Cursor
Add to .cursor/mcp.json:
{
"mcpServers": {
"devops": {
"command": "npx",
"args": ["-y", "@basel5001/mcp-devops-server"]
}
}
}Security Considerations
Command allowlist: Only
kubectl,terraform,helm,docker, andawscommands can be executed.Argument sanitization: Shell metacharacters (
;,&,|,`,$) and path traversal (..) are rejected.No shell execution: Commands run via
execFile(notexec), preventing shell injection.Timeouts: All commands have configurable timeouts (default 30s) to prevent hanging.
Read-only by design: No destructive operations (delete, apply, destroy) are exposed.
Development
npm install
npm run dev # watch mode
npm run build # compile
npm run lint # lintLicense
MIT
Available Tools
11 toolsaws_cost_summaryC
Get AWS cost summary
Inputs: days, granularity.
aws_resource_inventoryC
List AWS resources by service
Inputs: service (required), region.
docker_logsB
Get Docker container logs
Inputs: container (required), tail, since.
docker_psC
List Docker containers
Inputs: all, filter.
helm_diffB
Preview Helm upgrade changes
Inputs: chart (required), release (required), values, namespace.
helm_listC
List Helm releases
Inputs: namespace, allNamespaces.
kubectl_describeC
Describe a Kubernetes resource
Inputs: name (required), resource (required), namespace.
kubectl_getC
Get Kubernetes resources
Inputs: resource (required), name, output, namespace.
kubectl_logsC
Get logs from a Kubernetes pod
Inputs: pod (required), tail, since, container, +1 more.
terraform_planC
Run terraform plan
Inputs: directory (required), vars.
terraform_showC
Show terraform state
Inputs: directory (required), json.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 11 tools
Every tool uses a platform prefix that clearly separates Kubernetes, Terraform, Helm, Docker, and AWS concerns. Within each platform, the actions target distinct resources or operations, so no two tools are easily confused.
Tool names mostly follow a predictable <platform>_<command-or-action> pattern, such as kubectl_get, terraform_show, and helm_list. The two AWS tools use noun phrases instead of verbs, which is a minor deviation from the otherwise consistent style.
With 11 tools, the server covers a broad DevOps range without feeling bloated. Each tool represents a distinct and useful operation for infrastructure inspection and planning.
The toolset is heavily oriented toward read-only and planning operations: logs, describe, list, plan, show, and diff. There are no apply, deploy, delete, or mutation actions, so core DevOps workflows like applying Terraform changes or upgrading Helm releases cannot be completed.
Maintenance
Related MCP Connectors
Fail-closed policy guardrails for AI agents running kubectl, terraform, helm, and argocd.
Query your team's drift, vulnerability, and upgrade data from any AI assistant. OAuth 2.1, 51 tools.
Read-only AI coding tools for change verification, release readiness, capacity, and guidance.
Safe, read-only Postgres and MySQL access for AI agents. Audit log + column-level controls.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceProvides read-only access to Kubernetes clusters for AI assistants.25MIT
- AlicenseNot gradedqualityDmaintenanceEnables LLMs like Claude to securely execute Kubernetes CLI tools (kubectl, helm, istioctl, argocd) across multiple clusters through dynamic kubeconfig support, allowing natural language Kubernetes management and operations.5MIT
- AlicenseBqualityFmaintenanceAI-native control plane for Kubernetes and GitOps. Provides 30+ tools for service deployment, database provisioning, and log management via natural language.11MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to perform DevOps tasks including Kubernetes management, cloud provider operations, CI/CD, security scanning, and infrastructure monitoring through natural language.MIT