PostgreSQL MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| POSTGRES_DB | Yes | The name of the specific database to connect to | |
| POSTGRES_HOST | Yes | The hostname or IP address of your PostgreSQL server | |
| POSTGRES_PORT | No | The port number for your PostgreSQL server | 5432 |
| POSTGRES_USER | Yes | Your PostgreSQL username | |
| POSTGRES_PASSWORD | Yes | Your PostgreSQL password |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| test-postgres-connectionA | Test the Postgres connection and return connection status |
| get-all-tablesA | Execute SQL queries to get all tables in the database |
| execute-sql-queryA | Execute a SQL query on the database. Only SELECT statements are allowed for security. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: executing SELECT queries, listing all tables, and testing connection. There is no overlap.
All tool names follow a consistent verb_noun pattern with snake_case: execute-sql-query, get-all-tables, test-postgres-connection.
Only 3 tools for a PostgreSQL server is extremely limited. Typical servers require many more operations (CRUD, schema management, etc.), making this count too low for the domain.
The server only supports SELECT queries, listing tables, and connection testing. Missing essential operations like INSERT, UPDATE, DELETE, schema inspection, and index management, severely limiting usefulness.