Skip to main content
Glama
llm-graph

FastPostgresMCP

by llm-graph
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to FastPostgresMCP

No user-submitted related servers found.

    Related Servers

    • postgres-mcp

      hc-hyun
      A
      license
      Not graded
      quality
      B
      maintenance
      A Python MCP server that provides PostgreSQL database connectivity for Text-to-SQL workflows, enabling AI agents to explore schemas and execute parameterized SQL queries across multiple data marts.
      MIT

    • postgresql-mcp

      udaykumar-dhokia
      A
      license
      A
      quality
      D
      maintenance
      A secure MCP server that lets AI assistants directly interact with PostgreSQL databases via tools like create_table, list_tables, and execute_sql, plus a web configurator for managing connections.
      4
      1
      MIT

    • anydb-mcp

      officialalexeev
      A
      license
      Not graded
      quality
      D
      maintenance
      Zero-config MCP server that empowers AI agents to safely query SQL and NoSQL databases like PostgreSQL, MySQL, SQLite, MongoDB, and Redis.
      8 npm
      1
      MIT

    • Postgres MCP Pro

      linh1306
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      An open-source MCP server that provides AI agents with advanced PostgreSQL capabilities including index tuning, query plan optimization, and comprehensive database health analysis. It supports safe SQL execution through configurable access modes and offers both stdio and SSE transport options for various development environments.
      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.2/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a well-defined and distinct purpose: execute_tool for data modification, query_tool for read-only queries, schema_tool for table metadata, and transaction_tool for atomic operations. There is no ambiguity or overlap.

    Naming Consistency5/5

    All tool names follow a consistent verb_tool pattern using snake_case (execute_tool, query_tool, schema_tool, transaction_tool). The naming is predictable and clear.

    Tool Count4/5

    With four tools, the set is minimal but covers essential database operations (read, write, schema, transactions). While missing some auxiliary functions like listing tables, the count is appropriate for a focused server.

    Completeness4/5

    The tools cover the main CRUD lifecycle (via query and execute) and add schema retrieval and transactions. Minor gaps exist, such as lacking a tool to list all tables, but the core workflows are supported.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources