Skip to main content
Glama
1Levick3

PostgreSQL MCP Server

by 1Levick3

Related Servers

Alternatives to PostgreSQL MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that enables powerful PostgreSQL database management capabilities including analysis, schema management, data migration, and monitoring through natural language interactions.
      18
      928 npm
      200
      AGPL 3.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server for PostgreSQL that enables database operations like querying, schema inspection, performance analysis, and administration through a JSON-RPC 2.0 interface.
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      A standardized Model Context Protocol server for interacting with PostgreSQL databases, enabling full CRUD operations, schema management, and database introspection.
      1
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that enables connecting to PostgreSQL databases and executing queries, listing tables, retrieving schema, and obtaining database statistics through MCP tools.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      A Model Context Protocol server that enables interaction with PostgreSQL databases to list tables, retrieve schemas, and execute read-only SQL queries.
      4 npm
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server implementation that provides a simple interface to interact with PostgreSQL databases, enabling SQL queries, database operations, and schema management through MCP.
      -

    TDQS

    A3.9/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of confusion or overlap between tools. The tool's purpose is clearly defined and distinct by default.

    Naming Consistency5/5

    The single tool follows a clear verb_noun pattern (execute_custom_query), and there are no other tools to create inconsistency. The naming is straightforward and predictable.

    Tool Count2/5

    A single tool for a PostgreSQL server is too few for the apparent scope, as it lacks basic CRUD operations, schema management, or other database functions. This minimal set limits functionality and forces all interactions through a generic query tool.

    Completeness1/5

    The tool surface is severely incomplete for a database server. There are no tools for common operations like listing tables, inserting data, or managing connections, leaving significant gaps that will cause agent failures in typical database workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues