Skip to main content
Glama
mirenqinggege

postgres-mcp

by mirenqinggege
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
DATABASE_URIYesPostgres database connection URI
OPENAI_API_KEYNoOpenAI 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_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

execute_sql_fileA

Execute a SQL file containing migration scripts or DDL statements. The entire file is executed as a single transaction - all changes are rolled back if any statement fails. Only available in unrestricted access mode.

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 10 tools

Disambiguation4/5

Most tools have distinct purposes, but the two index analysis tools (analyze_query_indexes and analyze_workload_indexes) overlap somewhat, though descriptions clarify their different scopes.

Naming Consistency5/5

All tools use consistent snake_case verb_noun naming pattern (e.g., analyze_db_health, execute_sql, list_objects), making it predictable.

Tool Count5/5

10 tools is well-scoped for a database management server, covering health checks, index analysis, SQL execution, query analysis, and object browsing without being excessive.

Completeness4/5

The tool set covers most essential database operations (health, indexing, SQL, query analysis, schema browsing), though minor gaps like user management or lock monitoring exist but are not critical.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources