PostgreSQL MCP Server

Created By
aadarshjaina year ago
MCP Server (STDIO) for PostgreSQL Database
Overview

what is PostgreSQL MCP Server?

PostgreSQL MCP Server is a Model Context Protocol (MCP) server implementation designed for exploring and querying PostgreSQL databases.

how to use PostgreSQL MCP Server?

To use the server, run it with a PostgreSQL connection string and interact with it through various MCP tools to execute queries and retrieve database information.

key features of PostgreSQL MCP Server?

  • Connects to any PostgreSQL database using a standard connection string.
  • Executes custom SELECT queries with structured results.
  • Lists all tables in the connected database.
  • Provides detailed schema information for any table.
  • Filters database records based on specified criteria.
  • Retrieves database statistics including size and table count.

use cases of PostgreSQL MCP Server?

  1. Exploring database structure and contents.
  2. Executing complex SQL queries for data analysis.
  3. Integrating with applications like Claude Desktop for enhanced data interaction.

FAQ from PostgreSQL MCP Server?

  • What programming language is used for the server?

The server is implemented in Python.

  • Can I use this server with any PostgreSQL version?

Yes, as long as the connection string is valid and the server is accessible.

  • Is there a limit to the queries I can execute?

No, you can execute as many SELECT queries as needed, but only SELECT queries are allowed to prevent modifications.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
aadarshjain
Star
0
Language
Python
License
MIT license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

35 minutes ago