Skip to main content
Glama
mathewsls

postgres-explorer

by mathewsls
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to postgres-explorer

No user-submitted related servers found.

    Related Servers

    • MCP PostgreSQL Read-Only

      japentaca
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables secure read-only access to PostgreSQL databases through SELECT queries only, with tools for exploring schemas, listing tables, and executing common queries while preventing any data modification operations.
      1,239 npm
      MIT

    • postgres-mcp

      nicolas-canfrere
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables safe interaction with PostgreSQL databases through read-only queries, schema exploration, and performance analysis.
      127 npm
      MIT

    • PostgreSQL MCP Server

      DemeoStep
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides secure, read-only access to PostgreSQL databases for schema inspection and data querying. It enables users to list tables, describe structures, and execute SELECT statements while strictly blocking destructive operations.
      8 npm
      1
      MIT

    • pg-mcp

      NeuroviaLabs
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables read-only PostgreSQL database access with query, table listing, and schema inspection tools.
      -

    • postgres-mcp

      hangdo-merkle
      A
      license
      A
      quality
      C
      maintenance
      Enables read-only exploration of PostgreSQL databases, allowing schema inspection and safe SELECT queries without data mutation.
      8
      Apache 2.0
    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.7/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: execute_query handles arbitrary SELECT queries, while get_schema retrieves metadata about tables and columns. No overlap or ambiguity exists.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun pattern (execute_query, get_schema) using snake_case, making the naming predictable and clear.

    Tool Count2/5

    With only 2 tools, the server feels minimal for a 'PostgreSQL explorer'. Typical exploration would benefit from additional tools like describe_table, list_schemas, or view_details, making 2 tools insufficient for a well-scoped exploration surface.

    Completeness3/5

    The server covers basic schema browsing and arbitrary read queries, but lacks more granular tools (e.g., specific table details, constraint info, index listing). Users cannot easily explore beyond the public schema or get metadata about individual objects without writing SQL.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources