Skip to main content
Glama
AIops-tools

postgres-aiops

by AIops-tools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to postgres-aiops

No user-submitted related servers found.

    Related Servers

    • mysql-aiops

      AIops-tools
      A
      license
      A
      quality
      A
      maintenance
      Governed MySQL + MariaDB DBA operations — slow-query, lock-wait/deadlock, replication, and fragmentation RCA, with unbypassable audit logging (MCP + CLI), budget/runaway guards, dry-run, and undo/rollback.
      35
      MIT
    • pgtriage by pgtriage

      pgtriageofficial

      pgtriage
      A
      license
      A
      quality
      B
      maintenance
      Read-only PostgreSQL performance auditing via MCP. Collects metrics from PostgreSQL system views, applies deterministic checks for index, query, vacuum, configuration, and connection issues, and returns structured findings for MCP clients.
      5
      MIT

    • cicd-aiops

      AIops-tools
      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

    • observability-aiops

      AIops-tools
      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

    • container-host-aiops

      AIops-tools
      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

    • MCP PostgreSQL Operations

      call518
      A
      license
      A
      quality
      B
      maintenance
      Enables comprehensive PostgreSQL database monitoring, analysis, and management through natural language queries. Provides performance insights, bloat analysis, vacuum monitoring, and intelligent maintenance recommendations across PostgreSQL versions 12-17.
      34
      161
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 35 tools

    Disambiguation3/5

    Most tools target distinct resources or actions, but several read/RCA tools overlap: table_bloat, bloat_and_vacuum_analysis, and autovacuum_status all expose dead-tuple/vacuum data, while list_activity, long_running_queries, and top_queries can be confused. Descriptions usually clarify intent, but agents choosing among bloat/vacuum and activity tools could easily select the wrong one.

    Naming Consistency4/5

    Snake_case is used throughout, and writes mostly follow a clear verb_noun pattern (create_index, drop_index, terminate_backend), while enumerations use list_*. Minor deviations like reindex, undo_list vs undo_apply, and the *_rca nouns break the dominant pattern but remain readable and predictable.

    Tool Count3/5

    35 tools is heavy for a single server; the bloat, vacuum, activity, and RCA clusters could be consolidated without losing much capability. The broad Postgres-ops scope justifies more tools than a typical server, but the selection cost and overlap make the count feel above the ideal range.

    Completeness5/5

    The tool surface covers the core Postgres operations loop: health/status, query analysis, lock and blocking analysis, bloat/vacuum/index maintenance, configuration changes, replication/WAL diagnostics, and undo for every write. Every remediation has a corresponding read-side diagnostic, and most writes are reversible, so there are no significant dead-ends.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources