MCP ConfigsMay 13, 2026·2 min read

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
Agent ready

This asset can be read and installed directly by agents

TokRepo exposes a universal CLI command, install contract, metadata JSON, adapter-aware plan, and raw content links so agents can judge fit, risk, and next actions.

Stage only · 17/100Stage only
Agent surface
Any MCP/CLI agent
Kind
Mcp Config
Install
Stage only
Trust
Trust: Established
Entrypoint
Asset
Universal CLI install command
npx tokrepo install 0b7eef82-ddb4-52b1-93a3-d64a27bfc5b9
install contractmetadata JSONadapter planraw content
Intro

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 & Thanks

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

Discussion

Sign in to join the discussion.
No comments yet. Be the first to share your thoughts.

Related Assets

PostgreSQL MCP — SQL Database Server for AI Agents

MCP server that gives AI agents direct access to PostgreSQL databases. Run queries, explore schemas, manage tables, and analyze data through natural language. 3,000+ stars.

MCP Configs
MCP Hub

PostgreSQL MCP Server — Database Queries for AI

MCP server for PostgreSQL database access. Run read-only SQL queries, inspect schemas, list tables, and analyze data directly from Claude Code or Cursor.

MCP Configs
MCP Hub

Cupertino — Offline Apple Docs MCP Server

Cupertino crawls and serves Apple docs to agents via MCP; verified 736★ and ships a bundle with 277k+ pages across 402 frameworks.

MCP Configs
MCP Hub

pg-aiguide — Postgres Skills + MCP Search

pg-aiguide upgrades AI coding assistants for PostgreSQL: install best-practice skills via `npx skills` and add an MCP server for semantic doc search.

MCP Configs
MCP Hub
◈Home🔍Search👤Me