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 |
|---|---|
| execute_custom_queryA | Execute a custom SQL query against the database. WARNING: Use with care. Do not expose to untrusted input. |
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 1 tool
With only one tool, there is no possibility of confusion or overlap between tools. The tool's purpose is clearly defined and distinct by default.
The single tool follows a clear verb_noun pattern (execute_custom_query), and there are no other tools to create inconsistency. The naming is straightforward and predictable.
A single tool for a PostgreSQL server is too few for the apparent scope, as it lacks basic CRUD operations, schema management, or other database functions. This minimal set limits functionality and forces all interactions through a generic query tool.
The tool surface is severely incomplete for a database server. There are no tools for common operations like listing tables, inserting data, or managing connections, leaving significant gaps that will cause agent failures in typical database workflows.