Skip to main content
Glama
YawLabs

@yawlabs/postgres-mcp

by YawLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to @yawlabs/postgres-mcp

No user-submitted related servers found.

    Related Servers

    • postgres-mcp

      sajjad-hk
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables read-only, SELECT-only querying of any Postgres database through MCP-compatible clients like Claude, with schema introspection and guarded SQL execution.
      MIT

    • postgres-mcp

      RachelHuangZW
      A
      license
      A
      quality
      B
      maintenance
      Exposes PostgreSQL query execution, EXPLAIN, and schema inspection tools to MCP-compatible clients like Claude Desktop.
      3
      1
      MIT

    • pg-mcp

      awaketai
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables natural language querying of PostgreSQL databases through the Model Context Protocol. It translates user questions into validated SQL, executes read-only queries safely, and returns results to MCP-compatible clients like Claude Desktop.
      -

    • PostgreSQL MCP Server with

      kevin29a
      F
      license
      Not graded
      quality
      D
      maintenance
      Provides authenticated access to PostgreSQL databases for Claude AI, enabling users to browse database tables, discover schemas, and execute custom SQL queries through natural language interaction.
      -

    • PostgreSQL MCP Server

      longgoll
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to safely interact with PostgreSQL databases, perform queries, inspect schemas, and analyze query performance.
      2
      -
    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

    A4.1/5.0

    Scored across 23 tools

    Disambiguation4/5

    Tools are mostly distinct with clear purposes, but pg_health aggregates connections and active queries, which have dedicated tools (connections, active_queries), creating minor overlap. Descriptions are detailed enough to differentiate, but an agent might initially confuse pg_health with these dedicated tools.

    Naming Consistency3/5

    Most tools follow the pg_ prefix convention (pg_explain, pg_health, pg_kill), but three tools (connections, active_queries, database_stats) break this pattern without the prefix. This inconsistency is minor but noticeable, making the naming slightly unpredictable.

    Tool Count3/5

    With 23 tools, the server is at the upper edge of the borderline range (16-25). While each tool serves a specific monitoring or management purpose, the large number could feel heavy, though it is justified given the comprehensive coverage of PostgreSQL features.

    Completeness5/5

    The tool set covers a wide range of PostgreSQL operations: query execution, health checks, connection monitoring, active queries, I/O stats, schema inspection, index advisory, performance analysis, locks, roles, privileges, replication, bloat, and a roll-up advisor. This is a complete surface for DBA-style monitoring and management, with no obvious gaps.

    Maintenance

    ActivityNo data
    ResponsivenessResponsive

    Resources