Skip to main content
Glama
dfridkin

clawops

by dfridkin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to clawops

No user-submitted related servers found.

    Related Servers

    • Havlio

      kanduit-lab
      F
      license
      Not graded
      quality
      Not graded
      maintenance
      Self-hosted PaaS MCP server providing a write-capable control plane with over 100 tools to deploy, roll back, manage domains, and administer infrastructure, while ensuring agent permissions never exceed human RBAC.
      -

    • infra-mcp

      Phloraxx
      F
      license
      Not graded
      quality
      B
      maintenance
      Securely inspect and operate self-hosted infrastructure including Linux host health, Docker containers and logs, Dokploy deployments, and OCI resources through a narrowly scoped, auditable MCP gateway.
      -

    • InfraClaude

      batu-sonmez
      A
      license
      B
      quality
      D
      maintenance
      An MCP server that enables Claude to manage infrastructure across Kubernetes, Docker, Prometheus, and Terraform through natural language. It provides over 42 specialized tools with a safety-first design, including risk-based command classification and audit logging.
      43
      MIT

    • 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

    • InfraPilot

      Gsfrota
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables infrastructure operations including provisioning, configuration, monitoring, compliance auditing, and auto-remediation through natural language, using Terraform and Ansible tools exposed over MCP.
      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

    D1.7/5.0

    Scored across 19 tools

    Disambiguation2/5

    Many tools have overlapping or unclear purposes, such as clawops_status, clawops_monitor, clawops_doctor, and clawops_task_status, which all seem related to checking system state. Without descriptions, it's difficult for an agent to distinguish between these tools, leading to likely misselection.

    Naming Consistency4/5

    All tools follow a consistent pattern with the 'clawops_' prefix and snake_case naming (e.g., clawops_config_get, clawops_config_set). However, verb usage varies (status, plan, destroy, harden) and some names like 'clawops_doctor' or 'clawops_up' are less conventional, but the overall pattern is predictable.

    Tool Count3/5

    The server exposes 19 tools, which falls into the 'heavy' range (16-25). While the breadth suggests a comprehensive DevOps operations tool, the count feels slightly over-scoped for a single server, though it's not extreme enough to be detrimental.

    Completeness4/5

    The tool surface covers a wide range of operations: configuration management (get/set/unset/validate), lifecycle (plan/apply/destroy/up), monitoring (status/doctor/logs_tail/monitor), workflows (deploy_app/recover), and infrastructure control (stacks, agents, gateway). While some operations like a dedicated 'delete' or 'list' might be missing, the core workflows appear well-covered.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources