mcp-data-platform-v1.55.6

Fix: S3 instance name resolution for managed resources

The default S3 connection fallback in v1.55.5 resolved the correct instance config internally but returned an empty ConnectionName, causing the S3 client to never be created. The root cause was getS3Config("") — it found the default instance but its ConnectionName fallback used the empty string that was passed in.

What changed

Added resolveDefaultS3Instance() which resolves the instance name directly from the S3 toolkits config map, returning the actual key (e.g., "acme"). managedResourceS3Connection() now uses this resolved name, so getS3Config receives a non-empty instance name and sets ConnectionName correctly.

Upgrade notes

• No config changes required. This fixes the default S3 connection fallback introduced in v1.55.5.

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

Verification

All release artifacts are signed with Cosign. Verify with:

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