// the find
bytebase/dbhub
Token conscious database MCP server for Postgres, MySQL, SQL Server, Oracle, MariaDB, SQLite.
DBHub is an MCP server that lets Claude Code, Cursor, VS Code, and similar clients query Postgres, MySQL, MariaDB, SQL Server, Oracle, or SQLite through one process. It's aimed at developers already using MCP-based AI coding tools who want schema exploration and query execution without a database-specific server per engine.
The core pitch is real: 2 tools and ~1.4k tokens by default versus 19k+ for MCP Toolbox or Supabase's MCP server, which matters once you're juggling several MCP servers in one client's context window. One process handles six database engines via TOML config instead of running six separate servers. Guardrails (read-only mode, row limits, query timeout) are actual connector-level features, not just prompt instructions, and the test suite has per-connector integration tests (Postgres, MySQL, MariaDB, SQL Server, Oracle, SQLite) plus SSH tunnel and connection-pool cases, which is more coverage than most MCP servers bother with.
It requires Node >= 22.5.0 because it depends on the still-fairly-new built-in node:sqlite module — that's a narrow runtime pin that will break on anything still deployed with Node 20 LTS or an older Docker base image. The README leads with an upsell to Bytebase's paid product for approval flows, access control, data masking, and audit logging, so the moment you need real production controls beyond read-only/row-limit, you're pointed at a commercial tool rather than an OSS extension path. explain_sql, health_check, and custom tools are opt-in and need TOML configuration, so the 'zero dependency, 2 tools' framing only holds for the most basic use case. Most actual tool documentation lives external to the repo on dbhub.ai rather than in-repo docs, so you can't fully evaluate tool behavior from the source tree alone.