vibops-mcp
OfficialRelated Servers
Alternatives to vibops-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityAmaintenanceZero-quota GPU orchestration MCP server — lets AI agents discover, provision, and manage GPU compute across multi-datacenter partner nodes (H100/H200/B200) through a single control plane.488 npmMIT
- AlicenseAqualityAmaintenanceGoverned Kubernetes operations for AI agents with 15 MCP tools, audit logging, policy engine, and safety features.55MIT
- AlicenseNot gradedqualityBmaintenanceTurns 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.36 PyPI6Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables LLM agents to connect to multi-cloud DevOps control planes for Terraform plan inspection, drift detection and remediation, cost estimation, incident triage, and cloud resource discovery across Azure, AWS, and GCP. It supports autonomous workflows for PR review, FinOps optimization, and self-healing operations through MCP tools.MIT
- AlicenseAqualityBmaintenanceAI 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.3477AGPL 3.0
- FlicenseNot gradedqualityCmaintenanceProvides 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-
TDQS
Scored across 74 tools
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.
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.
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.
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.