Skip to main content
July 28, 2026 DBHub 1.0.0 is out — the first major version of our database MCP server for PostgreSQL, MySQL, MariaDB, SQL Server, and SQLite.

​
Why now

MCP shipped its 2026-07-28 spec revision, which makes the protocol stateless at its core. 1.0.0 adopts it: the stateless serving model, cacheable tool lists, and header-based routing, while 2025-era clients keep working unchanged on the same endpoints. The changes are documented with before/after code in How DBHub Adopts the New MCP Spec 2026-07-28. DBHub has been stateless by design since its first release. With the spec now standardizing that model, this is the right point to call it 1.0.

​
17 months in numbers

Since the first commit in March 2025:
  • 573 commits, 73 npm releases
  • 164 pull requests merged from 34 contributors
  • 158 issues closed, 3 open
  • 3,200+ GitHub stars, 270+ forks
1.0.0 ships: multi-database TOML configuration with hot reload, custom parameterized tools, SSH tunnels with multi-hop ProxyJump, read-only enforcement with engine-level guards, a web workbench, an MCP Bundle for Claude Desktop, and a Claude Code plugin.

​
Referenced by the Claude Code docs

The Claude Code documentation uses DBHub in its “Query your PostgreSQL database” example: Claude Code docs referencing DBHub for PostgreSQL

​
Compatibility

1.0.0 is a protocol upgrade, not a breaking release: every existing dbhub.toml, DSN, and command-line flag works unchanged, and 2025-era MCP clients are served alongside 2026-07-28 clients. The one caveat for hand-rolled HTTP scripts is in the adoption post. Try it:
DBHub is MIT-licensed at github.com/bytebase/dbhub. Thanks to everyone who filed the issues and sent the pull requests.