Skip to main content
Glama
mattcat10

postgres-mcp

by mattcat10
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to postgres-mcp

No user-submitted related servers found.

    Related Servers

    • 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
      14 npm
      ISC

    • @mhdd_24/dbeaver-mcp

      Mhdd-24
      A
      license
      A
      quality
      C
      maintenance
      Enables natural language interaction with PostgreSQL databases via MCP, supporting database exploration, schema listing, and SQL queries with profile-based connections.
      7
      ISC

    • PlainQuery

      Jarvis-27
      A
      license
      Not graded
      quality
      C
      maintenance
      Ask your database questions in plain English. Connects PostgreSQL databases to MCP clients and answers with real, structured data instead of guesses.
      MIT

    • mcp-data-cluster

      nhj048
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables natural language querying of PostgreSQL via MCP, combining SQL, vector search, and knowledge graph with automatic routing and token-aware curation.
      Apache 2.0

    • 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
    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.5/5.0

    Scored across 3 tools

    Disambiguation5/5

    The three tools have clearly distinct purposes: listing tables, describing a table's schema, and executing arbitrary SQL. There is no overlap in their intended use, making selection unambiguous.

    Naming Consistency5/5

    All tools follow a consistent snake_case verb_noun pattern (describe_table, query_database, list_tables). This is predictable and readable.

    Tool Count4/5

    Three tools is minimal but appropriate for a database query interface; each tool serves a distinct, necessary function. The count is slightly low but well-scoped.

    Completeness4/5

    The set covers the core workflow of exploring and querying a database: list tables, inspect schema, and run SQL (which can handle reads and writes). Some auxiliary functions like listing schemas or databases are absent but can be achieved via query_database.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources