vibops-mcp
OfficialRelated Servers
Alternatives to vibops-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceZero-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.479 npmMIT
- AlicenseAqualityBmaintenanceGoverned 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.6Apache 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.3483AGPL 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 117 tools
Most tools group cleanly into domain namespaces (slurm_, registry_, proxmox_, xo_, vsphere_, vme_) with descriptions that cross-reference related tools, so the majority are easy to tell apart. However, real overlaps exist: list_anomalies and get_open_anomalies both surface open anomalies, and the overloaded term 'jobs' spans VibOps operations (list_jobs/get_job), Slurm jobs (slurm_list_jobs), job SLIs (get_job_metrics), and eval results (get_job_evaluations), which invites misselection at 117 tools.
The dominant convention is consistent snake_case verb_noun, usually with a domain prefix (slurm_submit_job, registry_list_tags, vsphere_get_vm). Minor deviations exist: helm_upgrade/helm_uninstall reverse to noun_verb, run_kubectl uses a different verb style, and get_vm_usage is un-namespaced despite living beside the prefixed hypervisor tools.
117 tools is an extreme mismatch for any single agent surface, far beyond the 3-15 healthy range. The set aggregates six or more distinct product domains (HPC, registries, four hypervisors, FinOps, compliance, identity, audit), so an agent must navigate a huge selection space for any given task.
Coverage across most domains is strong and often full lifecycle: identities (create/list/rotate/revoke), policies (get/update), Slurm (submit/cancel/list/status/output), and per-hypervisor VM start/stop/snapshot/migrate. Gaps remain — pipelines can be listed and triggered but not created or deleted/updated, and secrets can be created and listed but not deleted or rotated.