Skip to content

Tags: bytebase/dbhub

Tags

v1.2.0

Toggle v1.2.0's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
1.2.0 (#393)

v1.1.0

Toggle v1.1.0's commit message
chore: upgrade from 1.0.0 to 1.1.0

v1.0.0

Toggle v1.0.0's commit message
chore: bump version 0.24.0 to 1.0.0

First major release: MCP TypeScript SDK v2 and native 2026-07-28
protocol serving (stateless core, cacheable tool lists, header-based
routing) with full 2025-era client compatibility on the same endpoints.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

v0.24.0

Toggle v0.24.0's commit message
chore: upgrade 0.23.0 to 0.24.0

v0.23.0

Toggle v0.23.0's commit message
chore: upgrade from 0.22.6 to 0.23.0

Minor bump for the new MCP Bundle (.mcpb) distribution channel. Merging
this to main triggers the npm, Docker, MCP registry, and mcpb-release
workflows for 0.23.0 — the first GitHub release ships v0.23.0 with the
bundle attached.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

v0.22.6

Toggle v0.22.6's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
feat: package DBHub as a Claude Desktop MCP Bundle (.mcpb) (#356)

* feat: package DBHub as a Claude Desktop MCP Bundle (.mcpb)

Add one-click Claude Desktop distribution via the MCP Bundle format:
double-click install, DSN prompted from user settings (stored in the OS
keychain), running locally over stdio. The bundle is read-only by design
(readonly = true, max_rows = 1000 on execute_sql) — the curated path for
giving non-technical users database access without a remote HTTP endpoint
or OAuth setup (#146).

No server code changes: the bundle ships a static dbhub.toml that uses the
existing ${ENV_VAR} interpolation (dsn = "${DBHUB_DSN}"), with DBHUB_DSN
injected by the client from the manifest's user_config.

- mcpb/: manifest (MCPB v0.3), read-only TOML config, icon
- scripts/build-mcpb.mjs: stages dist/ + runtime deps + drivers (derived
  from optionalDependencies, cloud-auth packages excluded), packs and
  validates with @anthropic-ai/mcpb; `pnpm run build:mcpb`
- scripts/smoke-test-mcpb.mjs: unpacks the archive outside the repo (so
  module resolution can't lean on the project's node_modules) and drives
  it over stdio with the MCP SDK client; `pnpm run test:mcpb`
- .github/workflows/mcpb-release.yml: on version bumps, builds, smoke
  tests, and attaches the bundle to GitHub release v<version>
- docs: new dbhub.ai/mcpb page + pointers from README/installation

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* fix: harden mcpb smoke test error paths per review

- Attach the stderr listener before connect() — the SDK exposes the
  PassThrough before spawning, so a startup crash now surfaces its stderr
  instead of logging an empty string
- Convert stderr chunks to text explicitly
- Handle non-Error throws in the catch path; make client.close()
  best-effort so a close failure can't mask the real outcome
- Include the spawn error message when mcpb unpack fails to start

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* docs: describe .mcpb as an open, multi-client format, not Claude Desktop-only

MCPB is governed by the Model Context Protocol project and installs
directly in Claude Desktop, Claude Code, and MCP for Windows; other
clients can run the unpacked bundle as a plain stdio server. Reword
README, docs, manifest, and comments accordingly, keeping Claude
Desktop as the concrete install walkthrough.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* fix: bootstrap npm upgrade in mcpb-release workflow

build-mcpb.mjs stages the bundle's node_modules via npm install, and
Node 22.22.2's bundled npm is broken (missing promise-retry). Apply the
same bootstrap-without-npm upgrade step npm-publish.yml already uses.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>