Skip to main content
Glama
luislopezsanchez

Postgres MCP Pro

by luislopezsanchez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ACCESS_MODENoAccess mode: restricted (read-only) or unrestricted (read-write)unrestricted
DATABASE_URIYesPostgreSQL connection URI, e.g., postgresql://user:password@host:5432/dbname
OPENAI_API_KEYNoOptional OpenAI API key for experimental index tuning

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_detailsB

Show detailed information about a database object

explain_queryA

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_queriesA

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

execute_sqlB

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

A3.7/5.0

Scored across 9 tools

Disambiguation5/5

Each tool targets a distinct aspect of database management: health checks, index analysis, SQL execution, query explanation, object details, and listing. No tools have overlapping purposes; an agent can easily distinguish them.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern (e.g., analyze_db_health, execute_sql, list_schemas). The verb choices vary appropriately per action, maintaining predictability.

Tool Count5/5

With 9 tools, the set is well-scoped for database analysis and management. Each tool serves a clear purpose without redundancy, and the count feels neither too sparse nor bloated.

Completeness5/5

The tool surface covers core database analysis needs: health checks, index recommendations, query execution and explanation, object browsing, and performance insights. Missing operations like object creation can be handled via execute_sql, so no critical gaps exist.

Maintenance

ActivityMaintained
ResponsivenessSyncing

Resources