mcp-devops-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| kubectl_getC | Get Kubernetes resources |
| kubectl_describeC | Describe a Kubernetes resource |
| kubectl_logsC | Get logs from a Kubernetes pod |
| terraform_planC | Run terraform plan |
| terraform_showC | Show terraform state |
| helm_listC | List Helm releases |
| helm_diffB | Preview Helm upgrade changes |
| docker_psC | List Docker containers |
| docker_logsB | Get Docker container logs |
| aws_cost_summaryC | Get AWS cost summary |
| aws_resource_inventoryC | List AWS resources by service |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.