Skip to content

mcp-data-platform-v1.57.2

Choose a tag to compare

View all tags
@github-actions github-actions released this 30 Apr 08:22
· 157 commits to main since this release
v1.57.2
7473fcd
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

v1.57.2

Highlights

Gateway toolkit auto-activates when persistence is available

The MCP gateway toolkit now activates automatically whenever the platform has a database-backed connection store, eliminating the need to declare toolkits.mcp.enabled: true in platform.yaml before saving connections through the admin UI. Connections of kind=mcp that an admin saves through the API or UI become live immediately on the next platform start, without further configuration.

The same auto-activation applies to the trino and s3 toolkit kinds when an admin saves their first DB-backed instance.

Stateless deployments (no database) still require explicit YAML opt-in. Operator-set values are never overridden — explicit enabled: false continues to disable the kind.

Improved OAuth admin UX for disabled-gateway deployments

Deployments that explicitly disable the gateway toolkit while having saved MCP connections in the database now surface a clear amber status card in the admin UI:

Gateway toolkit disabled — This connection is saved in the database but not active. Set toolkits.mcp.enabled: true (or remove the explicit false) and restart to activate.

Previously the OAuth status panel rendered nothing in this configuration.

Architectural improvements

  • ConnectionStore.Persistent() bool is now part of the public interface, enabling persistence-aware feature activation without runtime type inspection.
  • Platform.WireGatewayTokenStore() is exposed as a public method, making the post-construction OAuth wiring step part of the platform contract and discoverable for embedders.
  • WithConnectionStore(store) option for advanced embedders supplying alternative persistence backends.

Behavior change

Deployments that did not previously declare toolkits.mcp: in platform.yaml will see the gateway toolkit enabled after upgrade. To opt out:

toolkits:
  mcp:
    enabled: false

No config changes are required for any other deployment shape. No database migrations.

Full changelog

  • 7473fcd fix(platform): auto-enable manageable toolkit kinds when requirements are met (#348)

Compare: v1.57.1...v1.57.2

Installation

Homebrew (macOS)

brew install txn2/tap/mcp-data-platform

Claude Code CLI

claude mcp add mcp-data-platform -- mcp-data-platform

Docker

docker pull ghcr.io/txn2/mcp-data-platform:v1.57.2

Go (library composition)

go get github.com/txn2/mcp-data-platform@v1.57.2

Verification

All release artifacts are signed with Cosign (keyless, GitHub Actions OIDC) and ship with SBOMs.

cosign verify-blob --bundle mcp-data-platform_1.57.2_linux_amd64.tar.gz.sigstore.json \
  mcp-data-platform_1.57.2_linux_amd64.tar.gz

Container images:

cosign verify ghcr.io/txn2/mcp-data-platform:v1.57.2 \
  --certificate-identity-regexp='https://github.com/txn2/mcp-data-platform/.+' \
  --certificate-oidc-issuer='https://token.actions.githubusercontent.com'
Assets 25
Loading