Skip to main content
Glama
VibOpsai

vibops-mcp

Official
by VibOpsai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to vibops-mcp

No user-submitted related servers found.

    Related Servers

    • 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.
      3
      Apache 2.0

    • FleetQ

      escapeboy
      A
      license
      A
      quality
      A
      maintenance
      AI Agent Mission Control — 200+ MCP tools across 31 domains. Manage agents, experiments, workflows, crews, skills, tools, credentials, approvals, signals, budgets, marketplace, knowledge bases, chatbots, and more. Self-hosted, open-source (AGPL-3.0). Supports stdio + Streamable HTTP/SSE with OAuth 2.0 auth.
      34
      68
      AGPL 3.0

    • codinfy-agent-monitor

      bakalagoin
      F
      license
      Not graded
      quality
      A
      maintenance
      Provides real-time monitoring of AI agents, context, usage limits, workflows, files, Git, tests, builds, errors, secrets, and model-economy advice for tools like Claude Code, Codex, and Cursor, with 30 MCP tools for comprehensive observability.
      1
      -
    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

    A3.8/5.0

    Scored across 74 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with detailed descriptions. Even closely related tools like list_anomalies and get_open_anomalies differ in scope and are well explained, preventing confusion.

    Naming Consistency5/5

    Tool names consistently follow a verb_noun pattern (e.g., create_agent_identity, list_clusters). Subsystem prefixes like registry_, helm_, and slurm_ are used uniformly, maintaining a predictable structure.

    Tool Count2/5

    With 74 tools, the server covers a vast scope. While each tool is justified, the count far exceeds typical well-scoped ranges (3-15 tools) and falls into the 'too many' category, making navigation challenging.

    Completeness3/5

    The tool surface is broad but has notable gaps: missing delete_secret, cancel_job (non-Slurm), and create/update/delete for pipelines. Core workflows are covered, but lifecycle operations for some resources are incomplete.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources