PostgreSQL Products MCP Server

Created By
michael7736a year ago
MCP server for interacting with a PostgreSQL products database.
Overview

what is PostgreSQL Products MCP Server?

PostgreSQL Products MCP Server is a Model Context Protocol (MCP) server designed to interact with a PostgreSQL database containing product information, allowing clients to query the database using SQL.

how to use PostgreSQL Products MCP Server?

To use the server, clone the repository, install the dependencies, configure the PostgreSQL connection details in your MCP client settings, and run the server to execute SQL queries.

key features of PostgreSQL Products MCP Server?

  • Interacts with PostgreSQL databases to retrieve product information.
  • Executes read-only SQL queries (SELECT statements).
  • Configurable via environment variables for database connection.

use cases of PostgreSQL Products MCP Server?

  1. Querying product details from a PostgreSQL database.
  2. Integrating with AI assistants to provide product information.
  3. Running analytics on product data stored in PostgreSQL.

FAQ from PostgreSQL Products MCP Server?

  • What is required to run the server?

You need Node.js, npm or yarn, and access to a PostgreSQL database with the products schema.

  • Can I run multiple MCP servers?

Yes, you can configure multiple MCP servers in your settings.

  • Is there a specific version of PostgreSQL required?

The server is compatible with PostgreSQL 9.6 and later.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
michael7736
Star
0
Language
JavaScript
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