postgresql-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | Yes | The API key generated by the web configurator, mapping to a PostgreSQL database URL. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_tableA | Create a table with custom columns. Example: table_name = "users" columns = { "id": "SERIAL PRIMARY KEY", "name": "TEXT NOT NULL", "age": "INT", "created_at": "TIMESTAMP DEFAULT CURRENT_TIMESTAMP" } |
| list_tablesA | List all tables in the public schema. |
| describe_tableA | Describe table structure (columns, types, nullability, default). |
| execute_sqlB | Execute any SQL query. WARNING: Full database access. |
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 4 tools
The structured tools (create_table, list_tables, describe_table) have clear, distinct purposes, and execute_sql is explicitly a general SQL escape hatch. However, execute_sql overlaps with all of them, especially create_table, since table creation can be done through either tool.
All tool names follow the same verb_noun snake_case pattern: create_table, list_tables, describe_table, execute_sql. There are no mixed conventions or inconsistent verb styles.
Four tools is a reasonable, well-scoped set for a PostgreSQL server: three schema-oriented helpers plus one arbitrary SQL tool. Each tool has a clear role and none feel redundant or missing.
The set covers schema creation, listing, and inspection, and execute_sql provides full database access as a fallback. Row-level CRUD and operations like ALTER/DROP are not exposed as first-class tools, but they can be handled through execute_sql, leaving only minor gaps.