PostgreSQL

Created By
vinsidiousa year ago
MCP server for getting schema information from a PostgreSQL database
Overview

what is MCP-PG-Schema?

MCP-PG-Schema is a Model Context Protocol server that provides read-only access to PostgreSQL databases, enabling LLMs to inspect database schemas and execute read-only queries.

how to use MCP-PG-Schema?

To use MCP-PG-Schema, configure it with the Claude Desktop app or run it using Docker or NPX with the appropriate PostgreSQL connection string.

key features of MCP-PG-Schema?

  • Execute read-only SQL queries against PostgreSQL databases.
  • Automatically discover and provide JSON schema information for each table, including column names and data types.
  • Supports configuration through Docker and NPX for easy deployment.

use cases of MCP-PG-Schema?

  1. Inspecting database schemas for data analysis.
  2. Executing read-only queries for reporting purposes.
  3. Integrating with LLMs for enhanced data interaction.

FAQ from MCP-PG-Schema?

  • Can MCP-PG-Schema modify data in the database?

No, MCP-PG-Schema only allows read-only access to the database.

  • Is there a specific PostgreSQL version required?

MCP-PG-Schema is compatible with standard PostgreSQL databases, but it's recommended to use the latest version for best performance.

  • How do I configure the server?

You can configure the server using the "mcpServers" section in your claude_desktop_config.json or by using Docker/NPX commands.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
vinsidious
Star
-
Language
-
License
-

Recommend Servers

View All
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.

8 hours ago