PostgreSQL MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_tablesB | List all tables in the database with basic information |
| describe_tableB | Get detailed schema information for a specific table |
| get_table_relationshipsC | Get foreign key relationships for a table |
| list_schemasB | List all schemas in the database |
| get_indexesC | Get indexes for a specific table |
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 5 tools
Every tool has a clearly distinct purpose targeting different aspects of PostgreSQL metadata. describe_table focuses on schema details, get_indexes on indexing, get_table_relationships on foreign keys, and list_schemas/list_tables on database structure overviews. There is no overlap or ambiguity between these functions.
All tools follow a consistent verb_noun naming pattern (describe_table, get_indexes, get_table_relationships, list_schemas, list_tables). The verbs are appropriate and descriptive, and the snake_case convention is maintained throughout without deviation.
Five tools is a reasonable number for a PostgreSQL metadata server, providing essential introspection capabilities. It is slightly lean but covers core needs like schema listing, table exploration, and relationship mapping, though it could potentially benefit from additional tools for views or constraints.
The toolset covers read-only metadata operations well, but there are notable gaps for a full PostgreSQL MCP server. It lacks tools for query execution, data manipulation (INSERT/UPDATE/DELETE), or administrative tasks like user management, which limits its utility for broader database interactions.