Skip to main content
Glama
NotHarshhaa

devops-mcp

by NotHarshhaa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to devops-mcp

No user-submitted related servers found.

    Related Servers

    • KubeWhisper

      abdulhusainahk
      A
      license
      Not graded
      quality
      D
      maintenance
      An AI-DevOps MCP server that gives LLMs read-only-by-default access to Kubernetes clusters, Prometheus metrics, and GitHub Actions, enabling natural language queries about infrastructure status and safe write operations with previews.
      MIT

    • DevOps Agent Harness

      stwins60
      A
      license
      Not graded
      quality
      B
      maintenance
      Turns any AI coding agent or MCP client into a governed DevOps engineer by exposing policy-enforced tools for Kubernetes, Docker, Jira, Git/PR, CI/CD, AWS, Terraform, and incident response, with approvals, audit logging, secret redaction, and rollback enforced outside the model.
      390 PyPI
      5
      Apache 2.0

    • LUMINO MCP Server

      spre-sre
      A
      license
      Not graded
      quality
      C
      maintenance
      An open source MCP server empowering SREs with intelligent observability, predictive analytics, and AI-driven automation across Kubernetes, OpenShift, and Tekton environments.
      31 PyPI
      11
      Apache 2.0

    • k8scortex-mcp

      apatilgtn
      A
      license
      B
      quality
      D
      maintenance
      A production-grade MCP server providing a secure, natural-language interface to Kubernetes for developers and AI agents, with multi-cluster routing, OIDC authentication, RBAC, and audit logging.
      75
      45 npm
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3/5.0

    Scored across 21 tools

    Disambiguation5/5

    Each tool targets a distinct resource-action pair with clear descriptions. For example, list_pods, get_pod_logs, and describe_resource are all distinct. No overlapping functionality.

    Naming Consistency4/5

    All tools follow the pattern `k8s__verb_noun`. Verbs are consistent (list, get, describe, etc.), but there is minor inconsistency in singular vs plural nouns (e.g., get_pod_logs vs list_pods). Overall pattern is strong.

    Tool Count4/5

    21 tools cover a wide range of Kubernetes operations from monitoring to management. The count is slightly on the high side but well-scoped for a comprehensive DevOps tool.

    Completeness3/5

    Covers many common tasks (viewing, scaling, applying manifests) but lacks explicit create/update operations for many resource types (beyond apply). Missing rollback, secrets/configmaps, and other lifecycle operations.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources