// the find
t8y2/dbx
15MB, lightweight, cross-platform database client. Supports MySQL, PostgreSQL, SQLite, Redis, MongoDB, DuckDB, ClickHouse, SQL Server and more.15MB，轻量级跨平台数据库客户端、数据库管理工具。支持 MySQL、PostgreSQL、SQLite、Redis、MongoDB、DuckDB、ClickHouse、SQL Server 等。
DBX is a Tauri-based desktop (and Docker-hosted web) database client that packs support for 50+ databases into a 15 MB binary by using Rust drivers instead of bundling a JVM or Chromium. It targets developers who are tired of DBeaver's Java dependency or TablePlus's macOS lock-in and want one tool that covers everything from Postgres to Redis to ClickHouse. The MCP server integration is a genuine differentiator — it lets AI coding agents query your already-configured connections without any extra setup.
The 15 MB binary claim holds up: Rust + Tauri means no JVM, no Electron, no bundled browser engine — the size advantage over DBeaver or DataGrip is real and meaningful on constrained machines. The MCP server ships as an npm package (`@dbx-app/mcp-server`) that bridges your existing DBX connections to Claude Code or Cursor without re-entering credentials — that's a thoughtful integration, not a bolted-on demo. CodeMirror 6 with metadata-aware autocomplete and schema-context AI SQL generation beats most free alternatives. The Docker/web mode using the same codebase as the desktop app is a real win for team self-hosting scenarios.
The source is not fully open — the repo has a Vue/TypeScript frontend and Rust backend but the actual database driver implementations for many of the '50+' databases appear to live in a separate closed or JDBC-agent repo (`dbx-agents`), so the 'open source' claim is partially marketing. Most CI-visible workflows push to external services (QQ notify, 1Panel app store) which is noise and signals the primary audience is Chinese developers, which may affect English-language community support. The table structure editor says 'reviewable column and index changes for supported engines' — that 'supported engines' qualifier likely means most databases are read-only for DDL, which will bite teams who want unified schema management. There's no plugin system or extension API, so if your database isn't on the list you're writing a PR, not installing a plugin.