Sezzlee PostgreSQL

io.github.sezzleePublished by GitHub account sezzleev0.2.1Updated Oct 24, 2026

Explore and query PostgreSQL read-only: catalogue search, schema introspection and bounded queries.

VerifiedSTDIODesktop onlyDatabasesData & Analytics

Overview

AI-generated overview

Lets an assistant explore a PostgreSQL database read-only: search the catalog, inspect schemas, and run bounded SELECT queries.

What you can do
A local stdio MCP server exposing four tools: describe_connection, search_catalog, describe_table, and run_query. Catalog introspection covers readable tables, partitions, foreign tables, views and materialized views, column and table descriptions, and primary, unique and foreign constraints. Every query runs in its own read-only transaction with statement and lock deadlines and always ends in ROLLBACK, and results arrive through server cursors in batches of at most 128 rows.
When to use it
Useful when an assistant needs to answer questions about an existing PostgreSQL schema or read data without any risk of writes. It suits exploration, schema documentation, and ad-hoc read-only reporting against a database you can point it at.
Requirements
Runs locally over stdio as the npm package @sezzlee/postgres-mcp, so Node.js is needed. Required environment variables: SEZZLEE_POSTGRES_SERVER, SEZZLEE_POSTGRES_DATABASE, SEZZLEE_POSTGRES_USER, and the secret SEZZLEE_POSTGRES_PASSWORD. Optional: SEZZLEE_POSTGRES_PORT, SEZZLEE_POSTGRES_SSL_MODE (default verify-full), SEZZLEE_POSTGRES_CONNECT_TIMEOUT_MS, SEZZLEE_POSTGRES_QUERY_TIMEOUT_MS. Network access to the database host is required; desktop only.
Before you install
The server asks for a database password in SEZZLEE_POSTGRES_PASSWORD; use a dedicated read-only role granted SELECT only, never a shared application login. Read-only transactions prevent writes, but a database-defined function can still reach outside the database, and the statement guard does not see what a view or function calls. Other sessions are only partly protected: a role may cancel or terminate other sessions of the same role. Verified TLS requires verify-full.

Installation

In SourceWeft

  1. Open Sezzlee PostgreSQL in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.2.1LatestOct 11, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.