Required runtime environment for the MCP server, enabling the execution of database management operations through a Node.js application.
Provides PostgreSQL database management capabilities, including analyzing existing PostgreSQL setups, implementation guidance, debugging database issues, managing schemas, migrating data, and monitoring database performance.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@PostgreSQL MCP Server show me the top 10 customers by total orders"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
A Model Context Protocol (MCP) server that provides direct PostgreSQL database query execution capabilities. This server enables custom SQL query execution against PostgreSQL databases with support for parameterized queries and configurable timeouts. This project is designed specifically for use with the Cursor IDE.
Node.js >= 18.0.0
PostgreSQL server (for target database operations)
Network access to target PostgreSQL instances
Related MCP server: PostgreSQL MCP Server
To install PostgreSQL Database Query Server for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @1Levick3/postgresql-mcp-server --client claudeClone the repository
Install dependencies:
npm installBuild the server:
npm run buildAdd to MCP settings file:
{
"mcpServers": {
"postgresql-mcp": {
"command": "node",
"args": ["/Users/1Levick3/Desktop/postgresql-mcp-server/build/index.js"],
"disabled": false,
"alwaysAllow": [],
"env": {
"POSTGRES_CONNECTION_STRING": "postgresUrl",
"POSTGRES_SSL_CERT_PATH": "/Users/1levick3/Desktop/root.crt"
}
}
}
}npm run dev - Start development server with hot reload
npm run lint - Run ESLint
npm test - Run tests
Connection Security
Uses connection pooling
Implements connection timeouts
Validates connection strings
Supports SSL/TLS connections
Fork the repository
Create a feature branch
Commit your changes
Push to the branch
Create a Pull Request
Execute a custom SQL query against the database. WARNING: Use with care. Do not expose to untrusted input.
| Name | Required | Description | Default |
|---|---|---|---|
| connectionString | Yes | PostgreSQL connection string | |
| query | Yes | SQL query to execute | |
| values | No | Optional parameter values for the query | |
| timeout | No | Optional query timeout in milliseconds |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively communicates critical behavioral traits: that this is a potentially dangerous operation (executing arbitrary SQL), includes security warnings, and implies it can modify data. However, it doesn't specify what happens on success/failure, whether transactions are used, or what format results are returned in.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is perfectly concise with just two sentences that each earn their place: the first states the core functionality, the second provides critical warnings. It's front-loaded with the main purpose and appropriately sized for the tool's complexity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a potentially destructive database operation with no annotations and no output schema, the description provides adequate but incomplete context. It covers the dangerous nature and security considerations well, but doesn't explain what happens on execution (e.g., returns results, affects rows), error handling, or result formats, leaving gaps for the agent to navigate.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With 100% schema description coverage, the schema already documents all 4 parameters thoroughly. The description doesn't add any parameter-specific information beyond what's in the schema, so it meets the baseline expectation but doesn't provide additional value regarding parameter usage or semantics.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose with a specific verb ('execute') and resource ('custom SQL query against the database'), making it immediately understandable. It distinguishes what this tool does from potential alternatives by specifying it's for custom SQL execution rather than predefined operations.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear contextual guidance with the 'WARNING: Use with care. Do not expose to untrusted input' statement, which helps the agent understand appropriate usage scenarios and security considerations. However, it doesn't specify when to use this tool versus alternative query methods or database tools since no sibling tools are listed.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
execute_custom_queryWith 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.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Hosted MCP server for PostgreSQL diagnostics: slow queries, missing indexes, connection pressure.
Comprehensive PostgreSQL documentation and best practices, including ecosystem tools
MCP server for interacting with the Supabase platform
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/1Levick3/postgresql-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
