Skip to main content
Glama
pleware

postgres-mcp

by pleware
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to postgres-mcp

No user-submitted related servers found.

    Related Servers

    • pgguard-mcp

      Azzaraell
      A
      license
      A
      quality
      B
      maintenance
      Read-only Postgres access with a policy gate that blocks writes and restricts visible tables and columns.
      6
      5 npm
      MIT

    • pgmcp

      sbamin
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables safe, read-only querying of PostgreSQL databases with defense-in-depth protections including single-statement SELECT guard, row caps, and per-identity audit logging.
      1
      MIT

    • pg-guard-mcp

      BerkantACUN
      A
      license
      A
      quality
      C
      maintenance
      Enables read-only PostgreSQL interaction through safe query execution, query planning, table and column inspection, and privilege checks, with multi-layer defenses against write operations and transaction-control exploits.
      5
      MIT

    • mcp-read-only-sql

      lukleh
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides secure read-only SQL access to PostgreSQL and ClickHouse databases with built-in safety features like read-only enforcement, timeouts, and managed result files.
      MIT

    • PostgreSQL MCP Server

      jplwunder
      F
      license
      Not graded
      quality
      D
      maintenance
      Provides read-only access to PostgreSQL databases with schema inspection, query execution in multiple formats (JSON, CSV, Markdown), and query history tracking with built-in security features.
      -
    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

    A3.8/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: query runs ad-hoc read-only SQL, list_tables enumerates tables, describe_table returns column metadata, and relationships exposes foreign keys. There is no overlap in their intended use, so an agent can easily select the right tool.

    Naming Consistency4/5

    Three tools follow a verb_noun pattern (list_tables, describe_table) or a clear verb (query), while relationships is a noun. This is a minor deviation, but all names use snake_case and remain readable and predictable overall.

    Tool Count5/5

    Four tools is well-scoped for a read-only Postgres introspection server. Each tool serves a distinct, necessary function (querying, listing, describing, and mapping relationships) without redundancy or bloat.

    Completeness4/5

    The toolset covers the core read-only workflows: running queries, listing base tables, describing columns, and discovering foreign keys. However, it lacks tools for listing views or schemas (list_tables only covers public base tables), which are minor gaps for full schema exploration.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources