MEC Postgres

Created By
Pratye Aggarwala year ago
A Model Context Protocol server that provides read and write access to PostgreSQL databases. This server enables LLMs to inspect database schemas and execute read and write queries.
Overview

What is MEC PostgreSQL?

MEC PostgreSQL is a Model Context Protocol (MCP) server hosted on MCP.so, designed to enable Large Language Models (LLMs) to interact directly with PostgreSQL databases. It provides comprehensive read and write access, empowering LLMs to inspect database schemas, execute queries, and handle data modifications securely.


How to use MEC PostgreSQL?

To use MEC PostgreSQL, configure it in your application's MCP client settings by adding the server details provided by MCP.so. You'll connect your PostgreSQL database to the MEC PostgreSQL server, enabling immediate access for LLM interactions.


Key Features of MEC PostgreSQL

  • Query Execution:

    • Run SQL queries in a read-only transaction environment to safely retrieve data.
  • CSV Upload:

    • Easily upload CSV files directly into your database tables using read-write transactions.
  • Automatic Schema Discovery:

    • Automatically discover and inspect database schemas, including detailed column names and data types, through JSON schema endpoints.

Use Cases for MEC PostgreSQL

  • Quickly inspecting and verifying database schemas and structures.
  • Allowing LLMs to perform database queries for reporting or analytics.
  • Uploading and integrating CSV data into existing database tables.
  • Enabling secure and managed database write operations through structured CSV uploads.

Frequently Asked Questions (FAQ)

Can I write data to PostgreSQL via this server?
Yes! MEC PostgreSQL supports both read-only queries and write operations through CSV uploads.

How do I access schema information for my tables?
Table schema information is automatically provided in JSON format at endpoint URLs (postgres://<host>/<table>/schema), including columns and data types.

Can MEC PostgreSQL integrate with other applications?
Yes! MEC PostgreSQL integrates seamlessly with any application that supports Model Context Protocol (MCP) endpoints.

Server Config

{
  "mcpServers": {
    "postgres": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "mcp/postgres",
        "postgresql://host.docker.internal:5432/mydb"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Pratye Aggarwal
Star
-
Language
-
License
-
Category

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