PostgreSQL Multi-Schema MCP Server

Created By
HarjjotSinghha year ago
A Model Context Protocol server that provides read-only access to PostgreSQL databases with enhanced multi-schema support.
Overview

What is PostgreSQL Multi-Schema MCP Server?

The PostgreSQL Multi-Schema MCP Server is a Model Context Protocol server that provides read-only access to PostgreSQL databases with enhanced multi-schema support, allowing LLMs to inspect database schemas across multiple namespaces and execute read-only queries while maintaining schema isolation.

How to use PostgreSQL Multi-Schema MCP Server?

To use the server, run the command: npx -y mcp-server-postgres-multi-schema <database-url> [schemas], where <database-url> is the PostgreSQL connection string and [schemas] is an optional comma-separated list of schemas to expose.

Key features of PostgreSQL Multi-Schema MCP Server?

  • Multi-Schema Support: Specify which schemas to expose through command-line configuration.
  • Schema Isolation: Access control to only authorized schemas listed during server startup.
  • Cross-Schema Discovery: Unified view of tables across multiple schemas while maintaining schema boundaries.
  • Metadata Security: Filters system catalogs to expose only user-defined tables in specified schemas.

Use cases of PostgreSQL Multi-Schema MCP Server?

  1. Enabling read-only access to multiple schemas for data analysis.
  2. Allowing LLMs to query and inspect database schemas without compromising security.
  3. Facilitating cross-schema data discovery for applications.

FAQ from PostgreSQL Multi-Schema MCP Server?

  • Can I expose multiple schemas at once?

Yes! You can specify multiple schemas in a comma-separated list when starting the server.

  • Is the server secure?

Yes! The server maintains strict access control and schema isolation to ensure security.

  • What license is the server under?

The server is licensed under the MIT License, allowing you to use, modify, and distribute it.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
HarjjotSinghh
Star
1
Language
JavaScript
License
MIT license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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