Cette page est affichée en anglais. Une traduction française est en cours.
MCP ConfigsMay 13, 2026·2 min de lecture

DryRun — Offline PostgreSQL MCP (No DB Creds)

DryRun snapshots your PostgreSQL schema once and provides offline linting plus migration/query checks via CLI + MCP, without sharing prod credentials.

MCP Hub
MCP Hub · Community
Prêt pour agents

Staging sûr pour cet actif

Cet actif est d'abord staged. Le prompt copié demande à l'agent d'inspecter les fichiers staged avant d'activer scripts, config MCP ou config globale.

Stage only · 17/100Policy : staging
Surface agent
Tout agent MCP/CLI
Type
Mcp Config
Installation
Stage only
Confiance
Confiance : Established
Point d'entrée
Asset
Commande de staging sûr
npx -y tokrepo@latest install 0b7eef82-ddb4-52b1-93a3-d64a27bfc5b9 --target codex

Stage les fichiers d'abord; l'activation exige la revue du README et du plan staged.

Introduction

DryRun snapshots your PostgreSQL schema once and provides offline linting plus migration/query checks via CLI + MCP, without sharing prod credentials.

Best for: teams who want database-aware agents without sharing DATABASE_URL

Works with: PostgreSQL schemas (JSON snapshots), MCP clients over stdio/SSE, Homebrew/Rust installs

Setup time: 10-18 minutes

Key facts (verified)

  • GitHub: 27 stars · 2 forks · pushed 2026-05-12.
  • License: BSD-2-Clause · owner avatar + repo URL verified via GitHub API.
  • README-verified entrypoint: brew install boringsql/boringsql/dryrun.

Main

  • Adopt the “schema file” model: one person dumps/imports a snapshot, everyone else runs dryrun lint offline as shown in the README demo.

  • Use the MCP server to give agents schema intelligence without credentials; README shows claude mcp add dryrun -- dryrun mcp-serve.

  • Treat lint output as actionable checklists: README includes example warnings/errors and suggested fixes (PKs, timestamptz, FK indexes).

Source-backed notes

  • README states dryrun is both a CLI tool and an MCP server, intentionally separated.
  • README explains the MCP server reads snapshots and exposes tools over stdio or SSE without a live DB connection.
  • README includes offline demo output with violations and fixes, and documents dryrun mcp-serve usage.

FAQ

  • Does it need prod DB access for the MCP server?: No — README emphasizes snapshots so credentials stay with DBAs.
  • How do I start the MCP server?: Use dryrun mcp-serve and add it via your client config (README shows Claude).
  • Can it lint offline?: Yes — README demonstrates dryrun lint working entirely from a schema file.
🙏

Source et remerciements

Source: https://github.com/boringSQL/dryrun > License: BSD-2-Clause > GitHub stars: 27 · forks: 2

Fil de discussion

Connectez-vous pour rejoindre la discussion.
Aucun commentaire pour l'instant. Soyez le premier à partager votre avis.

Actifs similaires