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
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago