mcp-data-platform-v1.55.4

MCP clients now see managed resources after REST API changes

Managed resources uploaded via the REST API (POST /api/v1/resources) were invisible to MCP clients because the MCP SDK client caches resources/list responses and only refreshes when the server sends a notifications/resources/list_changed notification. The REST API never triggered this notification, so clients showed a stale resource list for the entire session.

What changed

• NotifyResourceListChanged added to Platform — triggers notifications/resources/list_changed so connected MCP clients refresh their cached resource list.
• Resource handler now calls NotifyFn after successful create, update, and delete operations.
• Managed resources middleware now authenticates users directly for resources/list and resources/read methods instead of depending on PlatformContext from the tools/call pipeline. This fixes the case where the middleware had the right data in the database but couldn't serve it because the auth context was missing.

Full managed resources round-trip now works

1. Upload a resource via POST /api/v1/resources
2. Connected MCP clients receive notifications/resources/list_changed
3. resources/list returns the new resource (filtered by caller's visible scopes)
4. resources/read returns the resource content via the mcp:// URI scheme

Upgrade notes

• No config changes required.
• Deployments without an S3 connection for managed resources will store metadata in the database but cannot serve blob content via resources/read. The resources/list will still show the resource metadata.

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

Verification

All release artifacts are signed with Cosign. Verify with:

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