observability-aiops
Related Servers
Alternatives to observability-aiops
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceGoverned CI/CD operations for self-hosted GitLab and Gitea — pipeline-failure, runner, artifact-bloat, and stale-branch RCA, with unbypassable audit logging (MCP + CLI), budget/runaway guards, dry-run, and undo/rollback.28MIT
- AlicenseAqualityAmaintenanceGoverned reverse-proxy operations for Traefik, Caddy, and HAProxy — backend-health, cert-expiry, 5xx, and route-conflict RCA, with unbypassable audit logging (MCP + CLI), budget/runaway guards, dry-run, and undo/rollback.28MIT
- AlicenseAqualityAmaintenanceGoverned Docker + Portainer container-host operations (non-Kubernetes) — restart-loop, resource-pressure, and image/volume-bloat RCA, with guarded lifecycle writes, unbypassable audit logging (MCP + CLI), budget/runaway guards, dry-run, and undo/rollback.38MIT
- AlicenseBqualityAmaintenanceGoverned MinIO object-storage operations — capacity, exposure-surface audit, lifecycle, and healing RCA, with guarded bucket writes, unbypassable audit logging (MCP + CLI), budget/runaway guards, dry-run, and undo/rollback.48MIT
- AlicenseNot gradedqualityBmaintenanceMCP server that provides guarded, audited, read-only access to ops tooling (alerts, metrics, logs, deploys, runbooks) and a triage agent that diagnoses incidents end-to-end with CI-verified root cause analysis.MIT
- AlicenseAqualityAmaintenanceGoverned PostgreSQL DBA operations — slow-query, bloat, and blocking-lock RCA, index management, vacuum/analyze, and replication lag, with unbypassable audit logging (MCP + CLI), budget/runaway guards, dry-run, and undo/rollback.35MIT
TDQS
Scored across 39 tools
Most tools have clearly distinct purposes, well separated by backend (Prometheus/Loki/Grafana/Alertmanager) and by raw-read vs analysis. Minor overlaps exist in the scrape-health cluster (list_targets vs target_scrape_health vs target_scrape_health_analysis) and between loki_query and the canned loki_tail_errors, but the descriptions distinguish raw vs summarized vs analyzed views reasonably.
Names are consistently snake_case, with verb prefixes for mutations (create_/delete_/update_/expire_/reload_/undo_) and analysis-suffixed diagnostics. Many read/state tools are noun-phrases (firing_alerts, prometheus_tsdb_status, instant_query) rather than verb_noun, which is a minor deviation but internally predictable.
39 tools is heavy and well above the comfortable range, raising selection cost. However, the server legitimately spans four backends plus a cross-signal analysis layer and an undo/governance layer, so most tools do map to a real capability rather than being redundant.
Coverage is strong: full silence lifecycle (create/list/expire), alerts, rules, scrape targets, Loki queries, PromQL queries, dashboard read/update/delete, and a rollback layer. The notable gap is the absence of a create_dashboard tool (only update/delete exist), plus datasource/annotation operations are mostly read-only.