Skip to main content
Glama
Maxim2324

MCP PostgreSQL Server

by Maxim2324
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

Related Servers

Alternatives to MCP PostgreSQL Server

No user-submitted related servers found.

    Related Servers

    • 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.
      -

    • mcp-postgres

      gbfeliped
      A
      license
      Not graded
      quality
      D
      maintenance
      Read-only PostgreSQL MCP server that enables running SELECT queries, listing tables and schemas, and describing columns, with built-in protection against writes and malicious SQL attacks.
      488 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.
      113 npm
      MIT

    • Kenning PG MCP

      kenningai
      A
      license
      A
      quality
      B
      maintenance
      A secure PostgreSQL Model Context Protocol server that provides read-only database access through tools like schema listing, object inspection, query execution, and EXPLAIN analysis, with database-enforced access control via read-only transactions and a minimal role rather than SQL text parsing.
      7
      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 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no ambiguity. 'execute' handles INSERT/UPDATE/DELETE, 'query' handles SELECT, 'list_tables' and 'list_schemas' are separate listing functions, 'describe_table' provides metadata, and 'connect_db' is for connection management. The separation between 'execute' and 'query' is particularly well-defined.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun pattern (describe_table, list_schemas, list_tables). The main deviation is 'execute' and 'query' which use single verbs without objects, and 'connect_db' uses a verb_object pattern but with abbreviated 'db' instead of 'database'. The naming is still readable and mostly predictable.

    Tool Count5/5

    Six tools is well-scoped for a PostgreSQL server. This covers essential database operations: connection management, schema/table discovery, metadata inspection, and both read (SELECT) and write (INSERT/UPDATE/DELETE) operations. Each tool earns its place without bloat.

    Completeness4/5

    The toolset covers core PostgreSQL workflows well: discovery (list_schemas, list_tables), inspection (describe_table), and query execution (query, execute). Minor gaps include lack of transaction control tools (BEGIN, COMMIT, ROLLBACK) and database management operations (CREATE/DROP database/table), but agents can work around these using the existing execute tool.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources