Skip to main content
Glama

Related Servers

Alternatives to mysql-aiops

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      Governed 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.
      35
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Governed 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.
      28
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Governed 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.
      38
      MIT
    • A
      license
      B
      quality
      A
      maintenance
      Governed Prometheus + Grafana operations — firing-alert and scrape-target RCA, alert noise/flapping analysis, silences, and dashboards, with unbypassable audit logging (MCP + CLI), budget/runaway guards, dry-run, and undo/rollback.
      39
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Governed OPNsense + pfSense firewall operations — gateway-health, rule-shadow, and blocked-traffic RCA, with guarded rule/alias writes, unbypassable audit logging (MCP + CLI), budget/runaway guards, dry-run, and undo/rollback.
      35
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Universal database copilot for diagnostics, operations, and performance analysis via MCP and CLI.
      -

    TDQS

    A3.9/5.0

    Scored across 35 tools

    Disambiguation5/5

    Each tool targets a distinct aspect of MySQL operations, from raw diagnostics (list_transactions, lock_waits) to interpreted RCA (lock_wait_rca, slow_query_rca). Even closely related tools like table_sizes vs table_fragmentation are clearly separated by their data focus, so an agent can select unambiguously.

    Naming Consistency3/5

    Naming mixes verb-first commands (kill_session, create_index), list_* nouns (list_transactions), and bare noun phrases (table_sizes, replica_status). While each category follows an internal pattern, the lack of a single convention across the whole surface makes the set feel less predictable.

    Tool Count2/5

    With 35 tools, the surface is well beyond the 25+ threshold for typical MCP servers. Several read tools (table_sizes, table_fragmentation, table_status) could be consolidated, so the count feels inflated even for a broad AIOps domain.

    Completeness5/5

    The set provides end-to-end coverage of MySQL AIOps: observability, RCA, maintenance actions, and safe undo. Both raw data and interpreted analyses are present, and write operations are paired with reversibility, leaving no obvious dead ends in common workflows.

    Maintenance

    ActivityActive
    ResponsivenessNo issues