Skip to main content
Glama
Sign In
postgres-aiops

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
      B
      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

    • MCP-PostgreSQL-Ops

      CharlotteDejager60506
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to perform read-only PostgreSQL DBA work across versions 12–18, including performance analysis, slow query identification, bloat detection, lock and deadlock monitoring, autovacuum and schema inspection, and replication/WAL checks via natural language. Works with regular user permissions on RDS/Aurora without requiring any extensions, while optionally leveraging pg_stat_statements and pg_stat_monitor for deeper query analytics.
      -

    • MCP-PostgreSQL-Ops

      xu18613
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables natural-language PostgreSQL operations and monitoring across PG 12-18 without requiring extensions, covering performance analysis, slow-query identification, bloat detection, lock and connection monitoring, autovacuum inspection, replication/WAL status, and schema relationship discovery. All operations are read-only and production-safe, working with regular user permissions on RDS/Aurora as well as self-hosted instances.
      -

    • MCP-PostgreSQL-Ops

      henrielliott86
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to monitor and operate PostgreSQL databases through natural language queries, covering performance analysis, bloat detection, lock/deadlock monitoring, autovacuum and schema inspection, and maintenance recommendations with read-only, extension-optional workflows across PostgreSQL 12–18.
      -
    • pgtriage

      pgtriageofficial

      pgtriage
      A
      license
      A
      quality
      A
      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.
      6
      MIT

    • MCP-PostgreSQL-Ops

      panagiotismaxwell
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to perform PostgreSQL operations and monitoring through natural language, including performance analysis, bloat detection, lock/deadlock monitoring, autovacuum inspection, schema discovery, and maintenance recommendations with production-safe read-only tools across PostgreSQL 12–18.
      -
    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.6/5.0

    Scored across 35 tools

    Disambiguation4/5

    Most tools have clearly distinct resource/action targets: cancel_query vs terminate_backend, top_queries vs slow_query_rca, and the index diagnostics are separable. However, table_bloat, bloat_and_vacuum_analysis, and autovacuum_status overlap heavily around dead-tuple/vacuum diagnostics, and several index tools require careful reading to distinguish.

    Naming Consistency4/5

    All tool names consistently use snake_case, so there is no camelCase/snake_case mixing. The pattern is not uniform verb_noun: some are noun-phrase diagnostics (long_running_queries, index_bloat, table_sizes) while write tools use verbs (run_vacuum, create_index, drop_index, update_setting), making it mostly consistent with minor deviations.

    Tool Count2/5

    35 tools is far above the 3-15 well-scoped range and exceeds the 25+ 'too many' threshold. While Postgres operations is broad, many read-only diagnostic tools (table_bloat, autovacuum_status, index_bloat, etc.) could be consolidated or deferred behind a single analysis tool, so the surface feels heavy.

    Completeness4/5

    The set covers core operational read/write workflows: activity/locks/queries, index maintenance, vacuum/analyze, settings, replication/WAL, and a reversible-write/undo mechanism. Missing pieces like database/role lifecycle DDL, backup/restore, and schema introspection are notable but likely outside a focused AIOps scope, so the surface is mostly complete with minor gaps.

    Maintenance

    ActivityActive
    ResponsivenessSyncing

    Resources