Skip to main content
Glama
RathodDarshil

PostgreSQL Query MCP Server

query-postgres

Execute SQL queries on PostgreSQL databases to retrieve data through natural language interaction, enabling direct database access for information retrieval.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes

Implementation Reference

  • The inline handler function for the "query-postgres" tool. Validates the query is a read-only SELECT, executes it using the Postgres pool with a 10-second timeout, formats results as JSON (rows, rowCount, fields), or returns an error message.
    server.tool("query-postgres", { query: z.string() }, async ({ query }) => {
        try {
            // Validate that the query is read-only
            if (!isReadOnlyQuery(query)) {
                return {
                    content: [
                        {
                            type: "text",
                            text: "Error: Only SELECT queries are allowed. INSERT, UPDATE, DELETE, and other write operations are not permitted.",
                        },
                    ],
                    isError: true,
                };
            }
    
            // Create a promise that will be rejected after 10 seconds
            const timeoutPromise = new Promise((_, reject) => {
                setTimeout(() => {
                    reject(new Error("Query execution timed out after 10 seconds. Pls modify the query and try again."));
                }, 10000); // 10 seconds in milliseconds
            });
    
            // Execute the query with a timeout
            const result = (await Promise.race([pool.query(query), timeoutPromise])) as any; // Using 'any' here to handle the type after the race
    
            return {
                content: [
                    {
                        type: "text",
                        text: JSON.stringify(
                            {
                                rows: result.rows,
                                rowCount: result.rowCount,
                                fields: result.fields.map((f: any) => ({
                                    name: f.name,
                                    dataType: f.dataTypeID,
                                })),
                            },
                            null,
                            2
                        ),
                    },
                ],
            };
        } catch (error) {
            return {
                content: [
                    {
                        type: "text",
                        text: `Error executing query: ${(error as Error).message}`,
                    },
                ],
                isError: true,
            };
        }
    });
  • Input schema for the tool using Zod, requiring a single 'query' parameter of type string.
    server.tool("query-postgres", { query: z.string() }, async ({ query }) => {
  • src/index.ts:79-79 (registration)
    Registration of the "query-postgres" tool on the MCP server instance.
    server.tool("query-postgres", { query: z.string() }, async ({ query }) => {
  • Helper function to validate that the SQL query is read-only (starts with SELECT, excludes common write operations like INSERT, UPDATE, etc.). Called within the tool handler.
    function isReadOnlyQuery(query: string): boolean {
        // Normalize the query by removing comments, extra whitespace, and converting to lowercase
        const normalizedQuery = query
            .replace(/--.*$/gm, "") // Remove single-line comments
            .replace(/\/\*[\s\S]*?\*\//g, "") // Remove multi-line comments
            .replace(/\s+/g, " ")
            .trim()
            .toLowerCase();
    
        // Check if the query starts with SELECT
        if (normalizedQuery.startsWith("select")) {
            return true;
        }
    
        // Check for other write operations
        const writeOperations = [
            "insert",
            "update",
            "delete",
            "drop",
            "create",
            "alter",
            "truncate",
            "grant",
            "revoke",
            "copy", // COPY can write data
        ];
    
        for (const op of writeOperations) {
            if (normalizedQuery.startsWith(op) || normalizedQuery.includes(" " + op + " ")) {
                return false;
            }
        }
    
        return true;
    }
  • Postgres connection pool initialized from DATABASE_URL or command-line argument, used by the query-postgres tool handler.
    const pool = new Pool({
        connectionString,
        ssl: {
            rejectUnauthorized: false, // Use this if you're getting SSL certificate errors
        },
    });
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/RathodDarshil/mcp-postgres-query-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server