Skip to main content
hc
Submit
mcpSource-backed
DBHub logo

DBHub MCP Server

Token-efficient database MCP server for PostgreSQL, MySQL, MariaDB, SQL Server, and SQLite.

by Bytebase · submitted by oktofeesh1·added 2026-06-05·
Claude CodeCodexCursorClaude Desktop
HarnessClaude CodeCodexCursorClaude Desktop
Review first — review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Canonical URL
https://heyclau.de/entry/mcp/dbhub-mcp-server
Source URLs
https://dbhub.ai/installation, https://github.com/bytebase/dbhub
Brand
DBHub
Brand domain
dbhub.ai
Brand asset source
brandfetch
Safety notes
DBHub can execute SQL queries against configured databases., SQL execution can read, create, update, delete, or otherwise modify data depending on database permissions and requested queries., Configure read-only mode, row limits, query timeouts, least-privilege credentials, and human review before using DBHub with production or sensitive databases., Custom tools can wrap reusable parameterized SQL, so review their definitions before allowing agents to call them.
Privacy notes
Database connection strings, hostnames, schemas, table names, column names, row data, query text, query results, traces, and errors may be visible to the MCP client and model provider., Databases can contain personal data, customer records, credentials, business metrics, audit logs, payment data, healthcare data, and proprietary operational state., Avoid exposing production databases or regulated data unless the database, MCP client, and model session are approved for that access.
Author
Bytebase
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-05

Decision playbook

Review trust signals before you adopt

Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.

Compare context
Selected

0

Current score

63

Baseline

—

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Needs review

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done

  • Source provenance statusRequired

    Marked as source-backed.

    Done

  • Metadata reviewed

    No reviewed flag detected in metadata.

    Pending

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done

  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done

  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Needs review

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done

  • Package verification flag

    No package verification flag provided.

    Pending

  • Checksum metadata

    No checksum provided for downloaded artifact.

    Pending

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending

  • Baseline comparison available

    No baseline peer selected yet.

    Pending

  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

CLI install

Copy-ready — paste the snippet to get started.

10 minutes

Install command

Provided

Config snippet

Provided

Copy snippet

Provided

Prerequisites

5 to clear

Platforms

4 listed

Install type

CLI install

Adoption plan

Balanced adoption plan

Current risk score 24/100. Use staged verification before broader rollout.

Risk 24

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done

  • Confirm metadata review state

    No review metadata found; increase manual validation.

    Pending

  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done

  • Review privacy notesRequired

    Privacy notes are present.

    Done

  • Verify package integrity metadata

    No package verification/checksum metadata.

    Pending

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending

  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending

  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Missing required evidence: Metadata review. Risk score 31.

Risk 31

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Missing

Review metadata is missing.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required gaps: Metadata review

Decision timeline

Decision timeline · balanced

Blocking gaps: Check metadata review status. Risk 28.

Risk 28

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is missing.

Pending

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

Blockers: Check metadata review status

Prerequisite readiness

Prerequisite readiness

5 prerequisites to line up before setup. Have accounts and credentials ready first.

0/5 ready
Account & credentials1Install & runtime1Configuration2Permissions & scopes110 minutes

Safety & privacy surface

Safety & privacy surface

4 safety and 3 privacy notes across 5 risk areas. Review closely: credentials & tokens, permissions & scopes, third-party handling.

5 areas
  • SafetyExecution & processesDBHub can execute SQL queries against configured databases.
  • SafetyPermissions & scopesSQL execution can read, create, update, delete, or otherwise modify data depending on database permissions and requested queries.
  • SafetyCredentials & tokensConfigure read-only mode, row limits, query timeouts, least-privilege credentials, and human review before using DBHub with production or sensitive databases.
  • SafetyGeneralCustom tools can wrap reusable parameterized SQL, so review their definitions before allowing agents to call them.
  • PrivacyThird-party handlingDatabase connection strings, hostnames, schemas, table names, column names, row data, query text, query results, traces, and errors may be visible to the MCP client and model provider.
  • PrivacyCredentials & tokensDatabases can contain personal data, customer records, credentials, business metrics, audit logs, payment data, healthcare data, and proprietary operational state.
  • PrivacyCredentials & tokensAvoid exposing production databases or regulated data unless the database, MCP client, and model session are approved for that access.

Safety notes

  • DBHub can execute SQL queries against configured databases.
  • SQL execution can read, create, update, delete, or otherwise modify data depending on database permissions and requested queries.
  • Configure read-only mode, row limits, query timeouts, least-privilege credentials, and human review before using DBHub with production or sensitive databases.
  • Custom tools can wrap reusable parameterized SQL, so review their definitions before allowing agents to call them.

Privacy notes

  • Database connection strings, hostnames, schemas, table names, column names, row data, query text, query results, traces, and errors may be visible to the MCP client and model provider.
  • Databases can contain personal data, customer records, credentials, business metrics, audit logs, payment data, healthcare data, and proprietary operational state.
  • Avoid exposing production databases or regulated data unless the database, MCP client, and model session are approved for that access.

Prerequisites

  • Node.js and npx available to the MCP client runtime.
  • A PostgreSQL, MySQL, MariaDB, SQL Server, or SQLite database connection.
  • Database credentials with the minimum privileges needed for the workflow.
  • Read-only permissions or DBHub guardrails configured before connecting production data.
  • SSH tunneling or SSL/TLS settings configured when required by the database environment.

Schema details

Install type
cli
Troubleshooting
No
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
10 minutes
Difficulty
advanced
Full copyable content
{
  "mcpServers": {
    "dbhub": {
      "command": "npx",
      "args": [
        "@bytebase/dbhub@latest",
        "--transport",
        "stdio",
        "--dsn",
        "YOUR_DATABASE_DSN"
      ]
    }
  }
}

About this resource

Content

DBHub is a token-efficient database MCP server from Bytebase. It connects MCP clients to PostgreSQL, MySQL, MariaDB, SQL Server, and SQLite databases through a small tool surface focused on SQL execution, schema/object search, and custom reusable SQL tools.

The upstream README documents NPM, Docker, demo, and multi-database configuration options. The scoped NPM package exposes the dbhub binary for MCP clients.

Source Review

These sources were reviewed on 2026-06-05. Prefer the live repository, installation docs, and NPM registry metadata for current package version, command options, supported databases, guardrails, and setup guidance.

Features

  • Connect to PostgreSQL, MySQL, MariaDB, SQL Server, and SQLite.
  • Execute SQL with transaction support and safety controls.
  • Search database schemas, tables, columns, indexes, and procedures.
  • Define reusable parameterized SQL operations as custom tools.
  • Connect to multiple databases with TOML configuration.
  • Use guardrails such as read-only mode, row limits, and query timeouts.
  • Support SSH tunneling and SSL/TLS encryption.
  • Use the built-in workbench interface for database tools and request traces.

Installation

For MCP clients that launch stdio servers:

{
  "mcpServers": {
    "dbhub": {
      "command": "npx",
      "args": [
        "@bytebase/dbhub@latest",
        "--transport",
        "stdio",
        "--dsn",
        "YOUR_DATABASE_DSN"
      ]
    }
  }
}

Replace YOUR_DATABASE_DSN with an approved database connection string and restart the MCP client after adding the server.

Use Cases

  • Ask Claude to inspect schema structure before writing a query.
  • Search tables, columns, indexes, and procedures in a development database.
  • Run approved read-only SQL queries for analytics or debugging.
  • Define reusable custom SQL tools for repeated safe database operations.
  • Connect several development or staging databases from one MCP server.
  • Use the workbench to inspect tool requests and query traces.

Safety and Privacy

Database access is high impact. Use least-privilege credentials, prefer read-only mode, configure row limits and query timeouts, and require human approval before running writes, migrations, deletes, broad updates, or queries against production data.

Connection strings, schemas, table names, row data, query results, traces, and errors can expose sensitive information. Do not connect databases containing regulated, customer, payment, healthcare, credential, or production data unless that access is approved for the MCP client and model session.

Duplicate Check

No bytebase/dbhub entry, @bytebase/dbhub package entry, or matching source URL was found in content/mcp.

#database#postgres#mysql#sqlite#sql-server

Source citations

Add this badge to your README

Show that DBHub MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/dbhub-mcp-server.svg)](https://heyclau.de/entry/mcp/dbhub-mcp-server)

How it compares

DBHub MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

Field
DBHub logoDBHub MCP Server

Token-efficient database MCP server for PostgreSQL, MySQL, MariaDB, SQL Server, and SQLite.

Open dossier
MySQL MCP Server

MCP server for connecting Claude to MySQL databases with schema inspection, SQL query execution, SSH tunnel support, multi-database mode, and configurable write-operation controls.

Open dossier
Omnisearch MCP Server

MCP server that unifies web search, AI answer, GitHub search, and web extraction providers including Tavily, Brave, Kagi, Exa, Linkup, Firecrawl, and GitHub behind four consolidated tools.

Open dossier
pg-aiguide MCP Server

PostgreSQL documentation and best-practice MCP server from Timescale that gives Claude semantic and keyword search across PostgreSQL, TimescaleDB, and PostGIS docs.

Open dossier
Next steps
Open dossierAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing
Trust
Review statusNot reviewedNot reviewedNot reviewedNot reviewed
Package trustPackage not verifiedPackage not verifiedPackage not verifiedPackage not verified
Source provenanceSource-backedSource-backedSource-backedSource-backed
Submitteroktofeesh1oktofeesh1oktofeesh1oktofeesh1
Install riskReview firstReview firstReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
BrandDBHub logoDBHub———
Categorymcpmcpmcpmcp
SourceSource-backedSource-backedSource-backedSource-backed
AuthorBytebasebenborlaScott SpenceTimescale
Added2026-06-052026-06-052026-06-062026-06-05
Platforms
Claude CodeCodexCursorClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Harness
Claude CodeCodexCursorClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Source repo————
Safety notes✓DBHub can execute SQL queries against configured databases. SQL execution can read, create, update, delete, or otherwise modify data depending on database permissions and requested queries. Configure read-only mode, row limits, query timeouts, least-privilege credentials, and human review before using DBHub with production or sensitive databases. Custom tools can wrap reusable parameterized SQL, so review their definitions before allowing agents to call them.✓MySQL MCP Server can inspect schemas and run SQL queries against configured databases. Write and DDL operations can be enabled through environment variables, so keep insert, update, delete, and DDL permissions disabled unless explicitly required. Use a least-privilege MySQL user and avoid connecting the server to production databases with broad grants. Multi-database mode can expose every database visible to the configured MySQL user. SSH tunnel settings, query timeouts, cache settings, logging, and rate limits should be reviewed before connecting an MCP client.✓Omnisearch MCP Server can query multiple third-party search, AI answer, GitHub search, extraction, scraping, crawling, summarization, and content-processing providers. Firecrawl crawl, scrape, map, extract, and action modes can interact with websites and may trigger robots.txt, TOS, rate-limit, or authentication concerns. GitHub search depends on the configured token scope and can reveal private code, repositories, users, or organization metadata when a broad token is used. Large result mode can write response content to files; review where those files are stored before using it with private or regulated data. Require confirmation before crawling sites, extracting private URLs, using authenticated providers on sensitive targets, or running broad GitHub searches against private organizations.✓The hosted MCP endpoint is documentation-focused and read-only, but generated SQL and migration advice still needs human review before execution. Documentation search results can influence schema design, indexes, retention policies, and extension setup, so test generated SQL in development first. Self-hosted deployments need database credentials and embedding configuration; keep those scoped to the docs database, not production application data. The package can expose stdio and HTTP transports; bind local HTTP deployments only where intended and protect any non-local endpoint.
Privacy notes✓Database connection strings, hostnames, schemas, table names, column names, row data, query text, query results, traces, and errors may be visible to the MCP client and model provider. Databases can contain personal data, customer records, credentials, business metrics, audit logs, payment data, healthcare data, and proprietary operational state. Avoid exposing production databases or regulated data unless the database, MCP client, and model session are approved for that access.✓Database hostnames, schema names, table names, column names, query text, query results, credentials, prompts, logs, and tool outputs may be visible to the MCP client and model provider. Query results may contain customer data, credentials, tokens, personal data, financial data, internal IDs, or regulated records. MCP client configs, shell history, logs, screenshots, and shared project files can leak MySQL credentials if not handled carefully. Prefer local or user-scoped MCP configuration for database credentials instead of committing project-scoped configs.✓Provider API keys, GitHub tokens, search queries, URLs, extracted page content, crawled site maps, scraped text, summaries, AI answers, GitHub search results, and large-result files can be exposed to the MCP client. Search and extraction providers may log queries, URLs, source content, account identifiers, usage metadata, and generated responses according to their own policies. Web extraction can capture personal data, paywalled content, internal URLs, or proprietary documents if supplied by the user or available to an authenticated provider. GitHub search output may include repository names, code snippets, file paths, commit metadata, and organization details. Keep provider credentials in local MCP configuration only, and avoid sharing transcripts that contain private queries, URLs, source text, or tokens.✓Queries sent to the hosted MCP endpoint may reveal database names, schema intent, performance problems, product plans, or internal architecture details. Self-hosted semantic search can send queries or documentation chunks to the configured embedding provider unless a local compatible endpoint is used. Tool outputs can contain excerpts from PostgreSQL, TimescaleDB, Tiger Cloud, or PostGIS documentation that are then included in the model context. Do not include customer data, credentials, production connection strings, or private incident details when a generalized documentation query is enough.
Prerequisites
  • Node.js and npx available to the MCP client runtime.
  • A PostgreSQL, MySQL, MariaDB, SQL Server, or SQLite database connection.
  • Database credentials with the minimum privileges needed for the workflow.
  • Read-only permissions or DBHub guardrails configured before connecting production data.
  • Node.js 20 or newer available to the MCP client runtime.
  • MySQL 5.7 or newer, with MySQL 8.0 or newer recommended upstream.
  • Dedicated MySQL user with only the database grants required for the intended workflow.
  • MySQL host, port, credentials, database name, SSL, and optional SSH tunnel settings prepared.
  • Node.js 22 or newer for the published npm package.
  • At least one provider API key for Tavily, Kagi, Brave Search, GitHub, Exa, Linkup, or Firecrawl.
  • Optional `FIRECRAWL_BASE_URL` when using a self-hosted Firecrawl instance.
  • Optional `OMNISEARCH_LARGE_RESULT_MODE` choice for file or inline handling of large results.
  • An MCP-compatible client that supports remote HTTP MCP servers.
  • Network access to `mcp.tigerdata.com`.
  • PostgreSQL, TimescaleDB, Tiger Cloud, or PostGIS questions where documentation grounding is useful.
  • Optional self-hosting dependencies if running the package locally, including a populated Postgres docs database and embedding provider key.
Install
npx @bytebase/dbhub@latest --transport stdio --dsn YOUR_DATABASE_DSN
npx -y @benborla29/mcp-server-mysql
npx mcp-omnisearch
claude mcp add --transport http pg-aiguide https://mcp.tigerdata.com/docs
Config
{
  "mcpServers": {
    "dbhub": {
      "command": "npx",
      "args": [
        "@bytebase/dbhub@latest",
        "--transport",
        "stdio",
        "--dsn",
        "YOUR_DATABASE_DSN"
      ]
    }
  }
}
{
  "mcpServers": {
    "mysql": {
      "command": "npx",
      "args": ["-y", "@benborla29/mcp-server-mysql"],
      "env": {
        "MYSQL_HOST": "127.0.0.1",
        "MYSQL_PORT": "3306",
        "MYSQL_USER": "YOUR_MYSQL_USER",
        "MYSQL_PASS": "YOUR_MYSQL_PASSWORD",
        "MYSQL_DB": "YOUR_DATABASE",
        "ALLOW_INSERT_OPERATION": "false",
        "ALLOW_UPDATE_OPERATION": "false",
        "ALLOW_DELETE_OPERATION": "false",
        "ALLOW_DDL_OPERATION": "false"
      }
    }
  }
}
{
  "mcpServers": {
    "omnisearch": {
      "command": "npx",
      "args": [
        "mcp-omnisearch"
      ],
      "env": {
        "TAVILY_API_KEY": "your-tavily-key",
        "KAGI_API_KEY": "your-kagi-key",
        "BRAVE_API_KEY": "your-brave-key",
        "GITHUB_API_KEY": "your-github-token",
        "EXA_API_KEY": "your-exa-key",
        "LINKUP_API_KEY": "your-linkup-key",
        "FIRECRAWL_API_KEY": "your-firecrawl-key"
      },
      "type": "stdio"
    }
  }
}
{
  "mcpServers": {
    "pg-aiguide": {
      "type": "http",
      "url": "https://mcp.tigerdata.com/docs"
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.