Skip to main content
Glama

Related Servers

Alternatives to pgharbor

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to analyze, optimize, and safely interact with PostgreSQL databases, including health checks, index recommendations, query planning, and SQL execution with read-only and production protection modes.
      15
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to safely explore, analyze, and maintain PostgreSQL databases with read-only mode by default, SQL injection prevention, query performance analysis, and optional write operations.
      87 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to inspect PostgreSQL health, tune indexes, review and optimize EXPLAIN plans, understand schemas for context-aware SQL, and execute SQL safely with read-only/restricted or unrestricted access modes.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to register PostgreSQL connections on demand, explore schemas, run read-only queries, and require approval for writes.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI coding assistants to securely inspect PostgreSQL schemas, understand table relationships, search schema metadata, and run bounded read-only queries without exposing database credentials. It also supports query plan inspection to help optimize slow SQL.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to query PostgreSQL databases securely with read-only defaults, PII masking, rate limiting, and human-approved, expiring mutation tokens.
      9
      1
      Apache 2.0

    TDQS

    A3.7/5.0

    Scored across 50 tools

    Disambiguation4/5

    Most tools target a clearly distinct object or diagnostic question, and the descriptions explicitly separate close pairs such as pg_list_tables/pg_list_objects and pg_describe_table/pg_describe_object. The main ambiguity is among aggregate checks like pg_health_check, pg_integrity_check, pg_security_audit, and pg_vacuum_status, plus the generic pg_stat_view fallback, though their focus areas are documented.

    Naming Consistency4/5

    Every tool uses the pg_ snake_case prefix and readable domain terms, so the set is predictable overall. However, conventions vary between verb_noun forms (pg_list_tables, pg_describe_table) and noun-only or adjective_noun forms (pg_connections, pg_activity, pg_health_check), so it is not uniformly consistent.

    Tool Count2/5

    With 50 tools, the server is far above the practical 3-15 range and over the 25+ 'too many' threshold, creating a heavy selection burden for an agent. The tools are individually meaningful, but the surface could be consolidated into fewer grouped operations.

    Completeness5/5

    The set covers connection/policy management, querying and validation, schema/object discovery, DDL reconstruction, dependency analysis, performance and lock diagnostics, replication, security audit, extensions, and integrity checks. For a read-only PostgreSQL introspection server, this is an unusually complete surface; only write/maintenance execution actions are absent by design.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues