PostgreSQL MCP Server (Model Context Protocol)

Created By
VivekMalipatela year ago
FastMCP Based MCP Server to Control Postgres
Overview

What is PostgreSQL MCP Server?

PostgreSQL MCP Server is a basic implementation of FastMCP for PostgreSQL, enabling direct interaction with PostgreSQL databases from Claude AI, transforming AI chat experiences with persistent data storage.

How to use PostgreSQL MCP Server?

To use the PostgreSQL MCP Server, clone the repository, set up a Python virtual environment, install dependencies, and configure your PostgreSQL connection details in a .env file.

Key features of PostgreSQL MCP Server?

  • Query execution against PostgreSQL databases
  • Table management (create, drop)
  • Data operations (select, insert, update, delete)
  • Schema inspection
  • Integrated with Claude through MCP protocol

Use cases of PostgreSQL MCP Server?

  1. Storing and retrieving chat data in PostgreSQL databases
  2. Creating AI applications with persistent data storage
  3. Building knowledge management systems with structured database queries
  4. Analyzing large datasets directly through natural language prompts
  5. Implementing database-driven workflows without writing traditional code

FAQ from PostgreSQL MCP Server?

  • What are the prerequisites for using PostgreSQL MCP Server?

You need Python 3.8+, a PostgreSQL server, and access to Claude AI with MCP capabilities.

  • Is there a license for PostgreSQL MCP Server?

Yes, it is licensed under the MIT license.

  • How do I configure the PostgreSQL MCP Server?

You need to create a .env file with your PostgreSQL connection details and add the configuration to the Claude AI app settings.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
VivekMalipatel
Star
0
Language
Python
License
MIT license

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