DBHub is a minimal MCP server: token-efficient, zero-dependency, and just two tools by default with opt-in extras. This lightweight gateway allows MCP-compatible clients to connect to and explore different databases.

 +------------------+    +--------------+    +------------------+
 |                  |    |              |    |                  |
 |  Claude Desktop  +--->+              +--->+    PostgreSQL    |
 |                  |    |              |    |                  |
 |  Claude Code     +--->+              +--->+    SQL Server    |
 |                  |    |              |    |                  |
 |  Cursor          +--->+    DBHub     +--->+    Oracle        |
 |                  |    |              |    |                  |
 |  VS Code         +--->+              +--->+    SQLite        |
 |                  |    |              |    |                  |
 |  Other Clients   +--->+              +--->+    MySQL         |
 |                  |    |              |    |                  |
 |                  |    |              +--->+    MariaDB       |
 |                  |    |              |    |                  |
 +------------------+    +--------------+    +------------------+
     MCP Clients           MCP Server             Databases

DBHub is the official example in the Claude Code docs for connecting to PostgreSQL via MCP.

DBHub loads just 2 tools by default at 1.4k tokens — 13-14x fewer than alternatives — keeping the context window open for your actual work.

• Local Development: Schema exploration, query validation, and data debugging with Claude Code, VS Code, Cursor, etc.
• Non-Technical Access: Expose curated, read-only views to non-technical staff via Claude Desktop, VS Code, Cursor, etc.
• Multi-Database Consolidation: Replace separate MCP servers for each database with a single DBHub process
• Production Troubleshooting: Read-only diagnostics with guardrails against runaway queries

PostgreSQL, MySQL, SQL Server, MariaDB, Oracle, and SQLite.

DBHub brings powerful database capabilities to AI coding assistants:

• Minimal: Zero dependency, token efficient with a minimal set of MCP tools to maximize context window
• Multi-Database: PostgreSQL, MySQL, MariaDB, SQL Server, Oracle, and SQLite through a single interface
• Multi-Connection: Connect to multiple databases simultaneously with TOML configuration
• Guardrails: Read-only mode, row limiting, and query timeout to prevent runaway operations
• Secure Access: SSH tunneling and SSL/TLS encryption

DBHub provides AI assistants with direct database access through these tools:

• execute_sql: Run queries with transaction support and safety controls
• search_objects: Explore schemas, tables, columns, indexes, and procedures
• explain_sql (opt-in): Show a query's execution plan without running it
• health_check (opt-in): Report connection pool state and buffer cache hit ratio
• Custom Tools: Define reusable, parameterized SQL operations

A web-based interface for running database tools and viewing request traces without requiring an MCP client.

flowchart TB
    %% Human User
    User["Human User"]

    %% Workbench
    WB["DBHub Workbench"]

    %% AI Agent with MCP Client
    subgraph Agent["AI Agent"]
        MC["MCP Client"]
    end

    %% Configuration
    Config["dbhub.toml"]

    %% DBHub Server
    subgraph DBHub["DBHub Server"]
        MCP["/mcp endpoint"]
        subgraph Tools["MCP Tools"]
            ES["execute_sql"]
            SO["search_objects"]
            EX["explain_sql (opt-in)"]
            HC["health_check (opt-in)"]
            CT["custom tools"]
        end
    end

    %% Databases
    Databases["PostgreSQL, MySQL, SQL Server, MariaDB, Oracle, SQLite"]

    %% Connections
    User --> WB
    WB --> DBHub

    Agent --> MC
    MC --> MCP
    MCP --> Tools

    Config -.->|loads| DBHub
    Tools --> Databases

DBHub acts as a gateway between databases and AI agents. AI agents access databases through the /mcp endpoint using MCP tools, while the Workbench provides direct browser-based access for humans.