Deep Dive · Tools

DBX: A 25 MB Database Client for 90+ Databases — With Your Own AI on Top

✍️ Joe Maddalone ⏱️ 3 min 📅 September 2026
Video thumbnail

1.What DBX Is: 25 MB, 90+ Databases, Open Source0:00

DBX is a database client that weighs in at 25 MB and connects to 90+ databases — PostgreSQL, MySQL, SQLite, Redis, MongoDB, DuckDB, SQL Server, ClickHouse, Dameng, and more. Joe Maddalone's pitch is blunt: "it's probably going to replace any other clients you might be working with now."

It's open source (github.com/t8y2/dbx, Rust, Apache-2.0, ~21K stars), which the video notes means you can "peruse the code or fork it or whatever you want to do." The whole thing is one small binary that ships a desktop app, a Docker image, a CLI, an MCP server, and a web API.

The one-line pitch: the heavy database GUIs (DBeaver-class tools) run to hundreds of megabytes and a dozen panes. DBX gives you the essentials — connect, browse, query, AI assist — in a 25 MB Rust binary you can drop on any machine.

2.Connect & Query: Autocomplete and Command-Enter0:30

The workflow starts with New Connection, where you pick from a long list of database types. The demo uses a plain PostgreSQL connection — name, IP, user, password — then a test connection that confirms before you save. Once connected, the left panel lists your tables and you can drill into any database.

Querying is immediate: a new query window gives you autocomplete as you type, and Cmd/Ctrl-Enter runs it and drops the results below. That's the whole core loop — connect, type, run, read — with none of the ceremony of the big clients.

3.The AI Layer: Point It at Your Own Endpoint1:20

The feature that makes DBX stand out is the built-in AI, and the detail that matters is that it's provider-agnostic. Under Settings → AI → Add Config, you name a config, mark it OpenAI-compatible, drop in an API key, and point it at a URL.

Why the endpoint matters: because it's OpenAI-compatible, that URL can be a local model — LM Studio, Ollama, or anything exposing an OpenAI-style API on localhost. Maddalone's channel is "local AI on Mac," so this is the whole point: a database client whose AI runs against whatever model you already have, not a vendor's cloud.

The config has a test button that pings the endpoint before you apply it, so you know the AI is actually reachable before you try to use it.

4.AI in Action: Explain Schema, Generate SQL1:48

With the AI configured, the demo is two taps: hit the little robot button, pick your connection, and type "Explain the database structure to me." It returns a plain-language rundown of your tables and relationships — the fastest onboarding there is for a schema you didn't write.

Then the useful part: you can build complex queries with AI and apply them directly to the database. Natural language in, SQL out, executed in place — no copying between a chatbot and your client. For a developer who knows SQL but is tired of writing boilerplate joins, that's the killer feature.

5.Beyond the GUI: CLI, MCP, Docker, Web2:16

The video closes by flagging that the desktop app is "just the surface." DBX also ships a CLI, an MCP server, a web-based API, and a Docker image for self-hosting. The MCP server is the interesting one for agent workflows: it lets an AI agent query your databases through the Model Context Protocol, turning DBX from a human tool into an agent tool.

SurfaceWhat it's for
DesktopConnect, browse, query with autocomplete + AI
CLIScriptable, terminal-first database access
MCP serverLet an AI agent query your databases
DockerSelf-host the whole thing
Web APIProgrammatic access
Bottom line: a 25 MB, Apache-2.0, 90+-database client with a local-first AI layer and an MCP server is a genuinely useful combination — small enough to keep everywhere, and capable enough that an agent can drive it. Check it out at dbxio.com.

Key Takeaways

  1. DBX is a 25 MB, open-source database client (Rust, Apache-2.0, ~21K stars) for 90+ databases.
  2. Core loop is dead simple: connect, browse tables, type with autocomplete, Cmd/Ctrl-Enter to run.
  3. The AI layer is OpenAI-compatible and endpoint-agnostic — you can point it at a local model on localhost.
  4. AI can explain your schema in plain language and generate complex SQL applied in place.
  5. Beyond the GUI there's a CLI, MCP server, web API, and Docker image.
  6. The MCP server turns DBX into an agent tool — an AI can query your databases through MCP.

Timestamp Index

☰ View all