PgSQL MCP Server

Created By
twn39a year ago
🔧 A powerful tool server based on the Model Context Protocol (MCP), enabling interaction with PostgreSQL databases via MCP calls.
Overview

what is Pgsql Mcp Server?

Pgsql Mcp Server is a server application designed to facilitate the management and interaction with PostgreSQL databases using the Model Context Protocol (MCP).

how to use Pgsql Mcp Server?

To use Pgsql Mcp Server, run the server using the provided command with the appropriate Data Source Name (DSN) for your PostgreSQL database.

key features of Pgsql Mcp Server?

  • Easy setup for PostgreSQL database management
  • Supports Model Context Protocol for enhanced database interactions
  • Debugging and previewing capabilities for database operations

use cases of Pgsql Mcp Server?

  1. Managing PostgreSQL databases in development environments.
  2. Debugging database interactions during application development.
  3. Facilitating communication between applications and PostgreSQL databases.

FAQ from Pgsql Mcp Server?

  • What is the required environment to run Pgsql Mcp Server?

Pgsql Mcp Server requires Python and a PostgreSQL database to operate.

  • Is there a graphical interface for Pgsql Mcp Server?

No, Pgsql Mcp Server is a command-line tool designed for developers.

  • Can I use Pgsql Mcp Server with other databases?

No, Pgsql Mcp Server is specifically designed for PostgreSQL databases.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
twn39
Star
2
Language
Python
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.

6 hours ago