Skip to main content
Glama
it-romanov

Postgres MCP Pro

by it-romanov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
DATABASE_URIYesPostgres database connection URI, e.g. postgresql://username:password@localhost:5432/dbname
OPENAI_API_KEYNoOptional OpenAI API key for experimental index tuning by LLM

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_schemasA

List all schemas in the database

list_objectsC

List objects in a schema

get_object_detailsA

Show detailed information about a database object

explain_queryB

Explains the execution plan for a SQL query, showing how the database will execute it and provides detailed cost estimates.

analyze_workload_indexesB

Analyze frequently executed queries in the database and recommend optimal indexes

analyze_query_indexesA

Analyze a list of (up to 10) SQL queries and recommend optimal indexes

analyze_db_healthA

Analyzes database health. Here are the available health checks:

  • index - checks for invalid, duplicate, and bloated indexes

  • connection - checks the number of connection and their utilization

  • vacuum - checks vacuum health for transaction id wraparound

  • sequence - checks sequences at risk of exceeding their maximum value

  • replication - checks replication health including lag and slots

  • buffer - checks for buffer cache hit rates for indexes and tables

  • constraint - checks for invalid constraints

  • all - runs all checks You can optionally specify a single health check or a comma-separated list of health checks. The default is 'all' checks.

get_top_queriesB

Reports the slowest or most resource-intensive queries using data from the 'pg_stat_statements' extension.

execute_sqlC

Execute any SQL query

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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.3/5.0

Scored across 9 tools

Disambiguation4/5

Most tools have distinct purposes, but the two index analysis tools (analyze_query_indexes vs analyze_workload_indexes) could cause confusion as both recommend indexes, though descriptions clarify their different inputs. All other tools are clearly differentiated.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with snake_case (e.g., analyze_db_health, execute_sql, list_schemas). No mixing of conventions or ambiguous verbs.

Tool Count5/5

With 9 tools, the server is well-scoped for PostgreSQL management, covering health checks, index analysis, SQL execution, query explanation, and object listing. This is neither too sparse nor overwhelming.

Completeness4/5

The toolset covers core database diagnostics and performance tuning, but lacks tools for schema modification (e.g., create/drop index) or user management, which are reasonable omissions for a read-heavy diagnostic tool.

Maintenance

ActivityStale
ResponsivenessNo issues

Resources