VibOps MCP server — control your GPU infrastructure from any MCP-compatible client
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"vibops-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# vibops-mcp [](https://opensource.org/licenses/MIT) [](https://www.python.org/downloads/) [](https://github.com/VibOpsai/vibops-mcp) []() The MCP server for **VibOps — The AI Infrastructure Engine**. From code to GPU in one conversation. ## The problem Getting an AI app from code to production on GPUs requires stitching together 9+ tools — git, Docker, CI/CD, Helm, kubectl, GPU monitoring, cost management, compliance, alerting. Each with its own API, dashboard, and cost model. No single interface spans the full pipeline. ## The solution `vibops-mcp` connects your AI assistant to VibOps — the engine that clones, builds, deploys, scales, monitors, fixes, and bills your apps and agents on any GPU, any cluster, any cloud. One `pip install`, 117 tools, one conversation. - **Ship** — clone repos, build containers, deploy models, run Helm/kubectl, trigger pipelines, submit Slurm jobs - **Operate** — scale deployments, manage VMs (Proxmox/XO/vSphere/HPE VME), detect and remediate GPU anomalies - **Observe** — GPU utilisation, workload breakdown, MTTR, cost estimates, live K8s deployments - **Govern** — AI Act compliance, SOC 2/RGPD reports, immutable audit chain, policy management - **FinOps** — per-agent cost tracking, budget enforcement, chargeback, spend trends, waste analysis Every operation goes through your VibOps instance and is recorded in the immutable audit log. ## Installation ```bash pip install git+https://github.com/VibOpsai/vibops-mcp.git ``` Released versions are also on PyPI, if you prefer a pinned one: ```bash pip install vibops-mcp ``` ## Configuration You need two environment variables: | Variable | Description | |----------|-------------| | `VIBOPS_URL` | Base URL o…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.