Skip to main content
Glama
pg-readonly-mcp

pg-readonly-mcp

by milad-codes

Related Servers

Alternatives to pg-readonly-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to explore PostgreSQL schemas and run safe, read-only queries in plain English. It applies SQL validation, row limits, and read-only sessions to prevent writes and unsafe operations.
      6
      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
      Not graded
      quality
      B
      maintenance
      Gives AI agents read-only access to Postgres with parser-checked queries, hidden tables and columns, row limits and timeouts, caller-bound Row-Level Security, and a tamper-evident audit log.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to safely explore PostgreSQL schemas, inspect sample rows, draft queries, and read EXPLAIN plans through a read-only enforced interface for MCP clients.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI clients to safely query PostgreSQL databases using plain English, with read-only access and built-in SQL safety checks.
      4
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to safely explore and query PostgreSQL databases through read-only SQL validation, sensitive-data masking, and audit logging of every attempt.
      MIT

    TDQS

    A3.9/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: listing relations, describing one relation, executing a read-only SELECT, and explaining a SELECT plan. run_query and explain_query could superficially overlap, but the descriptions make the execution-vs-plan boundary explicit.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern: list_tables, describe_table, run_query, explain_query. The convention is predictable and readable.

    Tool Count5/5

    Four tools is well-scoped for a read-only PostgreSQL introspection/query server. Each tool earns its place and the surface avoids unnecessary breadth.

    Completeness4/5

    The core read-only workflow is covered: discover tables, inspect table structure, run ad-hoc SELECTs, and inspect query plans. Minor gaps exist around listing schemas, functions, or server-level metadata, but agents can work around these with run_query.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues