FastPostgresMCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Server logging level: debug, info, warn, error | info |
| DB_ALIASES | Yes | Comma-separated list of unique DB aliases | main,reporting |
| ENABLE_AUTH | No | Enable API Key auth (primarily for network transports) | false |
| MCP_API_KEY | No | API key for authentication when ENABLE_AUTH is true | |
| DEFAULT_DB_ALIAS | Yes | Default alias if 'dbAlias' is omitted in tool calls | main |
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 |
|---|---|
| query_toolC | Safely execute a read-only SQL query and retrieve results |
| execute_toolC | Safely execute a data-modifying SQL statement |
| schema_toolC | Retrieve detailed schema information for a specific table |
| transaction_toolB | Execute multiple SQL statements as a single atomic transaction |
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
Each tool has a well-defined and distinct purpose: execute_tool for data modification, query_tool for read-only queries, schema_tool for table metadata, and transaction_tool for atomic operations. There is no ambiguity or overlap.
All tool names follow a consistent verb_tool pattern using snake_case (execute_tool, query_tool, schema_tool, transaction_tool). The naming is predictable and clear.
With four tools, the set is minimal but covers essential database operations (read, write, schema, transactions). While missing some auxiliary functions like listing tables, the count is appropriate for a focused server.
The tools cover the main CRUD lifecycle (via query and execute) and add schema retrieval and transactions. Minor gaps exist, such as lacking a tool to list all tables, but the core workflows are supported.