Skip to main content
Glama
sbfulfil

PostgreSQL MCP Server

by sbfulfil
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

Related Servers

Alternatives to PostgreSQL MCP Server

No user-submitted related servers found.

    Related Servers

    • Postgres MCP Server

      eddykuhan
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with PostgreSQL databases through MCP, allowing users to explore database structures, inspect table schemas, and execute read-only SQL queries.
      -

    • postgres-mcp-server

      abdulsammad-lgtm
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to securely interact with PostgreSQL databases through a standardized MCP interface, supporting SQL queries, schema inspection, and database management.
      MIT

    • PostgreSQL MCP Server

      PhySci
      A
      license
      C
      quality
      D
      maintenance
      Enables querying PostgreSQL database metadata including table lists and schema information through the MCP protocol. Supports stdio transport for Cursor/IDE integration as well as HTTP transport with health check endpoints.
      2
      MIT

    • PgAdmin-MCP

      Mhdd-24
      A
      license
      A
      quality
      C
      maintenance
      Enables PostgreSQL schema exploration and SQL querying through natural language in MCP clients like Cursor, with support for dev/qa profile switching and read-only safety controls.
      7
      4 npm
      ISC

    • pgsql-mcp-server

      twn39
      A
      license
      Not graded
      quality
      F
      maintenance
      Enables interaction with PostgreSQL databases through MCP, supporting queries, DDL, DML, and schema inspection.
      33 PyPI
      6
      MIT
    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

    B3.4/5.0

    Scored across 5 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose targeting different aspects of PostgreSQL metadata. describe_table focuses on schema details, get_indexes on indexing, get_table_relationships on foreign keys, and list_schemas/list_tables on database structure overviews. There is no overlap or ambiguity between these functions.

    Naming Consistency5/5

    All tools follow a consistent verb_noun naming pattern (describe_table, get_indexes, get_table_relationships, list_schemas, list_tables). The verbs are appropriate and descriptive, and the snake_case convention is maintained throughout without deviation.

    Tool Count4/5

    Five tools is a reasonable number for a PostgreSQL metadata server, providing essential introspection capabilities. It is slightly lean but covers core needs like schema listing, table exploration, and relationship mapping, though it could potentially benefit from additional tools for views or constraints.

    Completeness3/5

    The toolset covers read-only metadata operations well, but there are notable gaps for a full PostgreSQL MCP server. It lacks tools for query execution, data manipulation (INSERT/UPDATE/DELETE), or administrative tasks like user management, which limits its utility for broader database interactions.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources