Skip to main content
Glama

Related Servers

Alternatives to Inference AIops

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents and SREs to diagnose Kubernetes incidents, perform root cause analysis, and generate safety-guardrailed GitOps remediation patches or kubectl commands. It supports live clusters, Alertmanager webhooks, and offline simulation scenarios.
      7
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to inspect and operate multiple Kubernetes clusters through natural language, providing multi-cluster diagnostics, RBAC analysis, security checks, and app-centric deployment with GitOps and smart workload placement.
      2
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Diagnose GPU/ML training failures (CUDA OOM, NCCL timeouts, Xid faults, NaN loss, and checkpoint corruption) directly from your AI tool. Includes root cause analysis, escalating fixes, distributed/NCCL hang culprit detection, and a local zero-egress mode.
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      VibOps MCP is the control plane between your AI agents and your GPU infrastructure. 74 tools covering: GPU fleet management (deploy, scale, monitor across NVIDIA, AMD, Intel, AWS, Google, Groq), Agent Infrastructure Control Plane (per-agent GPU cost, budget enforcement, model policies, dependency graph), governance (AI Act, SOC 2, immutable HMAC audit chain), and GPU FinOps (chargeback, waste..)..
      117
      491 PyPI
      20
      MIT

    TDQS

    B3.4/5.0

    Scored across 39 tools

    Disambiguation3/5

    Several tool pairs overlap heavily: engine_request_metrics vs request_metrics, engine_queue_depth vs queue_depth, and diagnose_engine_latency vs diagnose_latency_spike differ only by the engine-agnostic vs vLLM-specific nuance, which relies on careful reading. model_undeploy, scale_to_zero, and deployment_redeploy also have fuzzy boundaries when the goal is 'stop serving'. Descriptions do help disambiguate, but the near-duplicate pairs invite misselection.

    Naming Consistency3/5

    The set mixes verb_noun (scale_replicas_up, lora_load, model_deploy) with noun_verb patterns (engine_request_metrics, serve_deployment_list, replica_restart, deployment_status, cost_per_token). Prefixes like engine_/ray_/serve_ add grouping but are applied inconsistently. It stays readable but no single predictable convention governs the set.

    Tool Count2/5

    39 tools is well above the comfortable range and the surface is heavy for what is essentially a monitoring/ops console. The count is inflated by engine-agnostic vs engine-specific duplicates and by three tools that only ever return a refusal. It feels overstated for the domain.

    Completeness4/5

    Coverage is broad: deploy/undeploy, replica scaling, autoscale config, LoRA load/unload, sleep/wake, health/inventory/queue/cache metrics, RCA diagnostics, Ray cluster/job control, and an undo lifecycle. Gaps are minor, though routing_policy_update, replica_restart, and drain_replica exist only to reject requests, which adds surface without capability.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues