mcp-data-platform-v1.55.5

Managed resources automatically use the default S3 connection

When resources.managed.s3_connection was not explicitly configured, managed resources disabled blob storage entirely — resources/read could not serve file content even though an S3 toolkit was available for other features (portal, DataHub). Since managed resources are enabled by default when a database is available, they should also use an available S3 connection by default.

What changed

Added managedResourceS3Connection() which returns the explicit s3_connection if set, otherwise falls back to the default/first S3 toolkit instance. This follows the same convention-over-configuration pattern as managedResourceURIScheme() and the instance resolution used by semantic, query, and storage providers.

The info log now shows the resolved S3 connection name instead of the raw config value, so operators can see which S3 backend is actually in use.

Upgrade notes

• No config changes required. Deployments with an S3 toolkit configured for any purpose (portal, DataHub, etc.) will now automatically use it for managed resources.
• Deployments without any S3 toolkit continue to work — blob storage is disabled gracefully and resources store metadata only.
• To use a specific S3 connection for managed resources (different from the default), set resources.managed.s3_connection explicitly.

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.55.5

Verification

All release artifacts are signed with Cosign. Verify with:

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