Dryrun MCP Server

The PostgreSQL MCP server that doesn't need connection to the production. dryrun gives AI agents, IDEs, and CI full schema awareness. From offline snapshot, not live database connection. Lint your schema, validate queries, check migration safety, and explore foreign key graphs. All without credentials leaving the DBA's machine. It runs locally over stdio via the published package.

People who work with ai coding assistant, database and migration safety and want it reachable from Claude, Cursor, VS Code, or another MCP client. The project is written in Go.

VERIFIED ACTIVE

LAST COMMIT 2026-09-17 · ★ 35 · #29 OF 168 MAINTAINED DATABASE · VERIFIED 2026-09-18

BSD-2-Clause · Go servers · how we verify → /methodology

01 · Install Dryrun

before you install - you'll need

The README does not document required environment variables for a basic install.

Claude Code

claude mcp add boringsql-dryrun -- npx -y @boringsql/dryrun

Claude Desktop / Cursor / VS Code - add to config

{
  "mcpServers": {
    "boringsql-dryrun": {
      "command": "npx",
      "args": [
        "-y",
        "@boringsql/dryrun"
      ]
    }
  }
}

Same JSON for Cursor. For VS Code, rename the top-level key from `mcpServers` to `servers`.

Using another client? Same JSON, different key

Claude Desktop · mcpServers

Cursor · mcpServers

VS Code · servers

Windsurf · mcpServers

Zed · context_servers

Cline · mcpServers

Roo Code · mcpServers

Continue · mcpServers

LibreChat · mcpServers

Gemini CLI · mcpServers

Codex CLI · mcp_servers

Full setup guides: every client.

02 · Evidence

Security posture

What to check before giving this server access to your agent - from the registry, GitHub, and our own probes. We don't score safety; we show what's verifiable.

runs as local process (stdio) - runs on your machine with your user's permissions

license BSD-2-Clause - declared in the repository

npm package @boringsql/dryrun - published under the repo owner's npm scope (@boringsql)

registry namespace io.github.boringSQL is GitHub-verified and matches the repo owner

03 · What Dryrun can do

Prose above is summarized from the project's README and registry record - no invented capabilities.

Latest releases

v0.17.0 · 2026-09-13

Quality of life release. v0.16 brought performance improvements and this release build on top of it. · Fleet capture · Capture from v0.15 gets cadence and identity it can rely on. · Schema is a capture stream with…

v0.16.6 · 2026-09-03

v0.16.5 · 2026-09-02

04 · Who maintains Dryrun

dryrun is maintained by boringsql. It's the only MCP server we track from this author; the repo dates to Mar 2026.

05 · Facts

category
database - ranked #29 of 168 actively-maintained database servers as of 2026-09-18.
release cadence
10+ releases in the last 90 days (latest 2026-09-13)
registry
io.github.boringSQL/dryrun (active, first published 2026-08-23 · 4 versions)
packages
npm:@boringsql/dryrun

06 · Dryrun FAQ

What is Dryrun?

The PostgreSQL MCP server that doesn't need connection to the production. dryrun gives AI agents, IDEs, and CI full schema awareness. From offline snapshot, not live database connection. Lint your schema, validate queries, check migration safety, and explore foreign key graphs. All without credentials leaving the DBA's machine. It runs locally over stdio via the published package.

Is Dryrun still maintained?

Yes - as of 2026-09-18, its last commit was 2026-09-17 and it shipped 10+ releases in the last 90 days. We re-verify nightly.

How do I install Dryrun?

Run `npx -y @boringsql/dryrun`. The README does not document required environment variables for a basic install. You can also paste the ready-made client config above.

Does Dryrun run locally?

Yes - it's a stdio server: it runs on your machine (via npx) with your user's permissions. Your data stays local unless the server itself calls external APIs.

07 · Alternatives to Dryrun