Skip to main content
Glama

Related Servers

Alternatives to Postgres MCP Pro

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      A Model Context Protocol (MCP) server for PostgreSQL that provides safe, structured access to your database for AI assistants, enabling health checks, index tuning, lock analysis, and more.
      13
      8 npm
      MIT
    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      An open-source MCP server that provides AI agents with advanced PostgreSQL capabilities including index tuning, query plan optimization, and comprehensive database health analysis. It supports safe SQL execution through configurable access modes and offers both stdio and SSE transport options for various development environments.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server for PostgreSQL databases that enables AI agents to connect, query, and explore multiple databases with schema discovery and extension context.
      540
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      A Postgres MCP server with index tuning, explain plans, health checks, and safe SQL execution for AI agents.
      9
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that enables powerful PostgreSQL database management capabilities including analysis, schema management, data migration, and monitoring through natural language interactions.
      18
      928 npm
      200
      AGPL 3.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that provides AI assistants with secure, read-only access to PostgreSQL databases while offering comprehensive tools for schema exploration, query validation, and performance optimization.
      MIT

    TDQS

    B3.3/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no ambiguity: analyze_db_health focuses on health checks, analyze_query_indexes and analyze_workload_indexes target index optimization from different sources, execute_sql and explain_query handle query execution and analysis, get_object_details and list_objects provide object-level information, get_top_queries identifies performance issues, and list_schemas lists schemas. There is no overlap in functionality.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern using snake_case: analyze_db_health, analyze_query_indexes, analyze_workload_indexes, execute_sql, explain_query, get_object_details, get_top_queries, list_objects, and list_schemas. The naming is predictable and readable throughout.

    Tool Count5/5

    With 9 tools, the count is well-scoped for a Postgres database management server. Each tool earns its place by covering distinct aspects like health analysis, query optimization, execution, explanation, object listing, and performance monitoring, without being excessive or sparse.

    Completeness4/5

    The tool surface is nearly complete for Postgres database management, covering health checks, query analysis, execution, object inspection, and performance monitoring. Minor gaps exist, such as lack of tools for database creation, user management, or backup operations, but core workflows are well-covered and agents can work around these omissions.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues