Server facts
DBHub MCP Server
Project
- Author
- bytebase
- Repository
- github.com/bytebase/dbhub
- Website
- dbhub.ai
- License
- MIT
- Category
- Databases
Tech
- Runtime / language
- node
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 3,664
- Last commit
- Data as of
Tags
- Database Workbench
- Multi Connection
- Query Controls
- Schema Discovery
- Sql
Overview
DBHub can be used from an assistant or directly through its browser workbench. The workbench runs database queries and configured custom operations, and lets users inspect request traces without connecting an MCP client. On the MCP side, the built-in interface concentrates work into two tools: SQL execution with transaction handling, and object discovery that reveals detail progressively. The latter covers schemas and the objects within them, including procedures, indexes, columns, and tables. Parameterized operations can also be defined as reusable custom tools in dbhub.toml. A single instance can hold multiple connections through TOML configuration, including connections to different database engines.
The supported engines are SQLite and SQL Server alongside MariaDB, PostgreSQL, and MySQL. Execution controls include query deadlines, limits on returned rows, and a read-only setting; encrypted connections and SSH tunnels are also supported. Deployment security is a separate concern from query safeguards. HTTP clients receive no authentication from DBHub itself, and its default listener binds across all interfaces. The README therefore advises restricting the listener to loopback and using a firewall or reverse proxy for production access. Host-header checks help resist DNS rebinding, with explicitly allowed names available for custom domains. Startup examples cover Docker, npm, and demo operation. The npm path needs at least Node.js 22.5.0 because DBHub relies on the runtime's SQLite module.
Install & configure
Requirements
- npm launch: Node.js version 22.5.0 or above
- MCP client for tool calls, or a browser for workbench interaction
npx @bytebase/dbhub@latest --transport http --host 127.0.0.1 --port 8080 --demoThe arguments exactly follow the loopback demo example. Actual database connections use the documented --dsn example or TOML setup. Demo mode is not a configured connection to your database. Before exposing real data over HTTP, account for the lack of built-in client authentication.
Examples are translated from the published configuration. Supply your own credentials and verify requirements in the upstream README. Remote connectors are shown only where a supported configuration format is known.
Config file · macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
Use Settings → Developer → Edit Config when available. Do not assume a Linux configuration path; check the client documentation for your platform. Remote servers use the app’s connector flow when supported, not the local stdio file shown here. Merge this example with existing settings; do not overwrite unrelated servers.
No install command stated in the README — see repo. Check the client documentation for a supported connection method.
Read the Claude Desktop setup guideConfig file · Project: .cursor/mcp.json
User: ~/.cursor/mcp.json
The project path is relative to the workspace root. The tilde denotes your user home directory. Use Cursor’s MCP settings to confirm which configuration and scope your installed version is reading. Merge this example with existing settings; do not overwrite unrelated servers.
No install command stated in the README — see repo. Check the client documentation for a supported connection method.
Read the Cursor setup guideConfig file · Workspace: .vscode/mcp.json
For user scope, use the “MCP: Open User Configuration” command if available. Do not guess a user configuration path across operating systems, profiles, containers, or remote workspaces; check the client documentation. Merge this example with existing settings; do not overwrite unrelated servers.
No install command stated in the README — see repo. Check the client documentation for a supported connection method.
Read the VS Code setup guideConfig file · macOS/Linux: ~/.codeium/windsurf/mcp_config.json
Windows: %USERPROFILE%\.codeium\windsurf\mcp_config.json
Open the MCP configuration through Windsurf’s settings when possible to confirm the active file. Paths can differ in managed or future releases; check the client documentation if this location is not present. Merge this example with existing settings; do not overwrite unrelated servers.
No install command stated in the README — see repo. Check the client documentation for a supported connection method.
Read the Windsurf setup guideConfig file · Project scope: .mcp.json at the repository root
The project file uses mcpServers. For user scope, use claude mcp add --scope user rather than assuming .mcp.json in your home directory is the user configuration. Check the client documentation for managed settings and storage details. Merge this example with existing settings; do not overwrite unrelated servers.
No install command stated in the README — see repo. Check the client documentation for a supported connection method.
Read the Claude Code setup guideExamples are translated from the published configuration. Supply your own credentials and verify requirements in the upstream README. Remote connectors are shown only where a supported configuration format is known.
Tools
Source: repository README. Tool descriptions are a documented snapshot, not a live capability check.
| Tool | What it does |
|---|---|
| search_objects | Explore database structure, revealing object details progressively rather than returning everything immediately. |
| execute_sql | Submit SQL with transaction support and the server's execution controls. |
Names, permissions, and defaults can change. Check the current upstream documentation before granting access.
Use cases
- Inspect database objects incrementally before asking an assistant to write SQL.
- Configure reusable parameterized queries instead of repeating SQL for routine operations.
- Keep several database connections behind one TOML-configured instance.
- Review query behavior and request traces through the web workbench.
Strengths
- Separates SQL execution from discovery using only two built-in tool identifiers.
- Includes an interactive workbench that does not depend on an MCP host.
- Combines connection options with configurable restrictions on query execution.
Limitations
- Network clients are not authenticated by the HTTP server.
- The default HTTP listener is broader than loopback; exposure needs deliberate configuration.
- npm execution depends on a relatively recent Node.js runtime, starting at 22.5.0.
Frequently asked questions
Independent listing, not an affiliation or security review. Grant the least access needed and verify the upstream instructions before running code.
