A
licenseNot graded
qualityD
maintenanceEnables AI assistants to perform DevOps tasks including Kubernetes management, cloud provider operations, CI/CD, security scanning, and infrastructure monitoring through natural language.
MIT
mcp-devops-server
by basel5001
Related Servers
Alternatives to mcp-devops-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables read-only integration with GitHub, Jenkins, and Artifactory for DevOps monitoring, analysis, and troubleshooting. Provides repository inspection, build log retrieval, and artifact management through natural language.MIT
- AlicenseNot gradedqualityBmaintenanceEnables natural language Kubernetes operations, including smart resource queries, pod root-cause analysis, cross-environment diffs, and manifest generation.MIT
- AlicenseNot gradedqualityCmaintenanceProvides read-only access to Kubernetes clusters for AI assistants.23MIT
- 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
- AlicenseBqualityDmaintenanceAI-native control plane for Kubernetes and GitOps. Provides 30+ tools for service deployment, database provisioning, and log management via natural language.11MIT
TDQS
B3/5.0
Scored across 11 tools
Disambiguation5/5
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.
Naming Consistency4/5
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.
Tool Count5/5
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.
Completeness2/5
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
ActivityMaintained
ResponsivenessSyncing