Skip to main content
Glama

Related Servers

Alternatives to DBeast

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
      7
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      MCP server providing deep PostgreSQL context to AI assistants, including schema DDL, index health, foreign key associations, query execution plans, and performance statistics via read-only tools.
      12
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) Server that allows AI models to securely interact with data hosted in Azure Database for PostgreSQL. It enables natural language querying, schema exploration, and data management through MCP clients like Claude Desktop and Visual Studio Code.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A production-ready MCP server for PostgreSQL — built for Claude Desktop, Claude Code, and any MCP-compatible AI agent.
      Apache 2.0
    • A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that gives AI assistants deep visibility into databases, inspecting schemas, detecting index problems, analyzing table bloat, and explaining query plans across PostgreSQL, MySQL, and SQLite.
      9
      9
      1
      MIT
    • A
      license
      B
      quality
      A
      maintenance
      A production-grade Model Context Protocol server for PostgreSQL. Lets AI agents safely inspect, query, operate, and tune a Postgres database — over 100 tools spanning catalog introspection, query intelligence, natural-language SQL, structural diffs, hybrid search, graph queries, data movement, live ops, and more.
      12
      186
      10
      MIT

    TDQS

    A4.5/5.0

    Scored across 21 tools

    Disambiguation5/5

    Every tool has a clearly defined domain with detailed descriptions that differentiate it from others. For example, database_health focuses on live monitoring, health_check on connection status, and connect on establishing connections. Even similar-sounding tools like analyze_impact and execute_query are well-differentiated.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun in snake_case pattern (e.g., analyze_impact, configuration_review, database_health). The few exceptions like 'connect' and 'disconnect' are standard naming conventions and do not break consistency.

    Tool Count4/5

    With 21 tools, the set is slightly larger than the typical 3-15 range but fully justified by the comprehensive PostgreSQL DBA functionality covered. Each tool has a distinct purpose, so the count is appropriate for the domain.

    Completeness5/5

    The tool set covers virtually all major PostgreSQL administration aspects: connection management, health monitoring, query analysis/optimization, schema discovery, maintenance, data quality, security, replication, configuration, and auditing. No obvious gaps are present for a DBA assistant.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues