Skip to main content
Glama

PostgreSQL MCP by InsightfulPipe

Server Details

Hosted PostgreSQL MCP server for Claude, ChatGPT and Cursor, with each action switched per account.

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
OAuth
Works in Glama
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
Insightful-Pipe/postgresql-mcp-server
GitHub Stars
0
ChatGPT
–
Claude
–

TDQS

A4/5.0

Scored across 4 tools

Disambiguation4/5

The read/write split between query_data and execute_action is clear, and prompts_menu serves a distinct prompt-catalog purpose. query_contexts is more of a workflow helper than a peer tool, but the two 'Step 3 FINAL' tools could briefly confuse an agent until the read-only vs write distinction is read.

Naming Consistency4/5

Three of four tools follow a verb_noun pattern (execute_action, query_contexts, query_data). prompts_menu is noun_noun and slightly breaks the pattern, but the overall set remains predictable and readable.

Tool Count4/5

Four tools is well-scoped for a PostgreSQL gateway: one read path, one write path, one context planner, and one prompt catalog. The surface is lean rather than bloated, though the heavy reliance on meta-tools means only two tools perform core SQL operations.

Completeness4/5

The tool set covers the essential lifecycle: context discovery, read queries, write/DDL execution, and prompt access. Minor gaps exist around explicit schema browsing, transaction control, and connection management, but these are largely workable through SQL or the context workflow.

Available Tools

4 tools
execute_actionpostgresql Data Execute ActionA
Destructive
Inspect

Execute postgresql action (Step 3 (FINAL) of workflow).

REQUIRED: Complete these steps first using query_contexts:

  1. request='accounts' - Get workspace_id, brand_id, connection_slug AND available_actions

  2. request='actions_details' with actions=['xxxxxx', 'xxxxxx', 'xxxxxx'] - Get detailed body structure for specific action(s) using actions from available_actions

IMPORTANT: Always call step 2 to see the exact body structure before executing.

execute_action runs write SQL (INSERT/UPDATE/DELETE/DDL). Writes succeed only if your workspace role allows writes and the connected database role has the needed privileges.

Inputs: body (required). Returns: object

prompts_menupostgresql PromptsA
Read-only
Inspect

Access postgresql prompt catalog with 4 operations:

  1. List Public Prompts: • request='menu' - No additional params needed • Returns: All public/system prompts available for postgresql

  2. List Custom Prompts: • request='menu', prompt_type='custom', workspace_id= • Returns: All custom prompts for the specified workspace

  3. Get Public Prompt Details: • request='prompt_details', prompt_id= • Returns: Full text/details of a public prompt

  4. Get Custom Prompt Details: • request='prompt_details', prompt_id=, is_custom=True, workspace_id= • Returns: Full text/details of a custom prompt

Inputs: request (required), is_custom, prompt_id, prompt_type, +1 more. Returns: object

query_contextspostgresql Setup HelperA
Read-only
Inspect

Helper for planning InsightfulPipe postgresql requests.

Step 1: request='accounts' – Retrieve workspace_id, brand_id, connection_slug, other source metadata, AND available_actions (all read-only actions you can call).

Step 2: request='actions_details' with actions=['xxxxxx', 'xxxxxx', 'xxxxxx'] – REQUIRED before querying. Replace with actions from available_actions to get the exact request body, required identifiers, fields, and notes for each action.

Optional: request='available_actions' – Standalone call to list all available actions (already included in accounts response).

Optional: request='brands' with brand_id + workspace_id to pull brand guidelines.

Inputs: request (required), actions, brand_id, platform, +1 more. Returns: object

query_datapostgresql DataA
Read-only
Inspect

Query postgresql data (Step 3 (FINAL) of workflow).

REQUIRED: Complete these steps first using query_contexts:

  1. request='accounts' - Get workspace_id, brand_id, connection_slug AND available_actions

  2. request='actions_details' with actions=['xxxxxx', 'xxxxxx', 'xxxxxx'] - Get detailed body structure for specific action(s) using actions from available_actions

IMPORTANT: Always call step 2 to see the exact body structure before querying.

query_data accepts read-only SQL only: a single SELECT (or EXPLAIN) statement. Write statements (INSERT/UPDATE/DELETE/DDL) are rejected here - send them through execute_action.

Inputs: body (required). Returns: object

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      A production-ready MCP server for PostgreSQL — built for Claude Desktop, Claude Code, and any MCP-compatible AI agent.
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      A general-purpose PostgreSQL MCP server with full read-write SQL access, atomic multi-statement transactions, and schema inspection. Works with any PostgreSQL instance — local, Supabase, AWS RDS, or self-hosted — and connects to Claude, Cursor, Windsurf, or any MCP-compatible AI client.
      123 npm
      3
      ISC
    • F
      license
      Not graded
      quality
      D
      maintenance
      A secure PostgreSQL MCP server allowing AI models to read, write, update, and delete database records with parameterized queries, transactional dry-runs, disposable testing, and automated backups.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      An extensible MCP server for database operations that supports PostgreSQL for managing schemas, tables, data, and user permissions. It features automatic migration recording for DDL changes and integrates with various AI-powered editors like Cursor, Zed, and Claude Code.
      26 npm
      2
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.