Minimal, token-efficient Database MCP Server for PostgreSQL, MySQL, SQL Server, SQLite, MariaDB
io.github.bytebase/dbhub - MCP Server
The Minimal, token-efficient Database MCP Server supports PostgreSQL, MySQL, SQL Server, SQLite, and MariaDB. It delivers a compact, secure Model Context Protocol implementation tailored for large language model interactions with database systems.
🛠️ Key Features
Multi-database protocol support (PostgreSQL, MySQL, SQL Server, SQLite, MariaDB)
Token-efficient MCP design for cost-conscious usage
Lightweight, minimal server footprint
Integrates with Bytebase-backed DevSecOps workflows
AI/ML friendly topics and tooling interoperability
🚀 Use Cases
Embedding LLM-driven database queries with context-aware reasoning
Secure, low-overhead MCP for cross-database tooling
Prototyping AI-assisted database management and automation
⚡ Developer Benefits
Small, focused server suitable for integration into existing pipelines
Clear separation of concerns between MCP logic and database drivers
Open source foundation with recognizable ecosystem (dbhub/Bytebase)
⚠️ Limitations
Data about the exact API surface is limited in the excerpt
May require additional documentation for advanced features or custom adapters
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:
Minimal: Zero dependency, token efficient with a minimal set of MCP tools to maximize context window
Multi-Database: PostgreSQL, MySQL, MariaDB, SQL Server, 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 is the official example in the Claude Code docs for connecting to PostgreSQL via MCP.
Token Efficiency
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.
MCP Server
Default Config
Default Tools
DBHub
1.4k
2 (execute_sql, search_objects)
MCP Toolbox
19.0k
28
Supabase MCP
19.3k
all
Use Cases
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
Supported Databases
PostgreSQL, MySQL, SQL Server, MariaDB, and SQLite.
MCP Tools
DBHub implements MCP tools for database operations:
execute_sql: Execute SQL queries with transaction support and safety controls
search_objects: Search and explore database schemas, tables, columns, indexes, and procedures with progressive disclosure
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 in your dbhub.toml configuration file
Workbench
DBHub includes a built-in web interface for interacting with your database tools. It provides a visual way to execute queries, run custom tools, and view request traces without requiring an MCP client.
Requires Node.js >= 22.5.0 (DBHub uses the built-in node:sqlite module).
bash
# Install dependencies
pnpm install
# Run in development mode
pnpm dev
# Build and run for production
pnpm build && pnpm start --transport stdio --dsn "postgres://user:password@localhost:5432/dbname"