Skip to content

mcp-data-platform-v1.86.0

Choose a tag to compare

@github-actions github-actions released this 14 Jun 18:31
019a0de

This release makes human feedback easy to find and act on. The portal gains a Feedback hub that gathers all the feedback on your work in one place, and a new manage_feedback MCP tool lets an agent review and respond to pending feedback in a single call. The portal's asset areas are also consolidated so you browse by ownership instead of hopping between pages.

Highlights

  • See and act on all your feedback in one place (#617). A Feedback hub that lists every comment, question, and correction across the assets, collections, and prompts you can access, newest first, each linking back to the item. It also carries your worklist, the shared general channel, and a composer, and a sidebar badge tells you when feedback is waiting, so nothing slips by without a notification system.
  • Agents can review and respond to feedback (#618). A new manage_feedback tool. manage_feedback list with no target hands an agent everything awaiting you across your artifacts and the general channel, then get / reply / resolve and the validation actions work each thread, so you can ask an agent to "review and reply to any pending feedback" in one pass.
  • Browse assets by ownership, not by page (#616). Collections and "Shared With Me" fold into a single Assets area with Assets | Collections tabs and a Mine / Shared / All filter; Prompts gains a Shared tab.
  • Dependency bump: esbuild in the UI (#613).

Feedback hub (#617)

Feedback used to be reachable only one item at a time, and there was no way to tell whether anything you own or can see had new comments. The hub answers "what feedback is waiting on my work?" in one view:

  • Recent. Every feedback thread across the assets, collections, and prompts you own or have shared access to, most recent first. Each row links to its item and opens the thread in a side panel with a "Go to item" link.
  • Worklist. Your "Needs resolution" and "Awaiting my validation" lists.
  • General. The shared channel for feedback that is not tied to a specific item.
  • New feedback. A composer for posting to the general channel.
  • Sidebar badge. The Feedback nav item shows how many threads are waiting on you, a stand-in until there is a push-notification system.

New endpoint for integrators: GET /api/v1/portal/feedback/activity returns the caller's feedback across reachable assets/collections/prompts, scoped server-side so it never discloses feedback on items you cannot see.

manage_feedback MCP tool (#618)

Agents now have a dedicated, discoverable tool for feedback, with a cross-artifact entry point:

  • list with no target. The "review and act on any pending feedback" call. Returns your pending feedback across the assets and collections you own or can edit and the shared general channel (unresolved threads you did not author), plus any threads awaiting your validation, newest first.
  • list with a target. Threads on one asset/collection/prompt or the general channel, with status / validation-state / requires-resolution filters.
  • get / reply / resolve / request_validation / respond_validation. Read a thread and its timeline, comment, resolve, and run the validation handshake.

The agent loop is list (no target), then get, then reply/resolve. capture_insight thread_ids=[...] folds a thread into the knowledge loop and resolves it. Access follows the existing model: owner or editor for artifact threads (admins see all); the general channel is readable and replyable by any authenticated caller and resolved only by the thread author or an admin. Prompt-thread feedback stays admin-only and is reached by targeting the prompt.

Where the feedback actions live now

The feedback actions used to be sub-actions of manage_artifact; they now live on manage_feedback and dropped the _thread suffix:

Was (manage_artifact) Now (manage_feedback)
list_threads list
get_thread get
reply_thread reply
resolve_thread resolve
request_validation request_validation
respond_validation respond_validation

MCP clients read the tool list dynamically, so connected agents pick this up on their own with nothing to upgrade. The only thing to update is a hard-coded reference in a saved prompt, script, or workflow that names manage_artifact action=list_threads (and friends): point it at manage_feedback instead. The capture_insight thread_ids=[...] bridge is unchanged.

Assets consolidation (#616)

The asset areas no longer sprawl across the sidebar:

  • Collections and "Shared With Me" are removed as top-level nav items and folded into a single Assets area with an Assets | Collections tab strip and a Mine / Shared / All ownership filter (default All, remembered per browser).
  • Shared lists items others shared with you, with Shared by <email> attribution and a Viewer/Editor badge; All merges owned and shared, keeping the owned copy on overlap.
  • Shared assets open in the standard viewer at /assets/:id.
  • Prompts gains a Shared tab for prompts shared with you.

Upgrade notes

  • No new database migrations and no new required configuration.
  • Agents: the feedback actions are now on manage_feedback and are served via the dynamic tool list, so connected clients need no change. Update any hard-coded manage_artifact feedback action names in saved prompts/scripts to manage_feedback (see the table above).
  • New endpoint: GET /api/v1/portal/feedback/activity (authenticated, self-scoped).
  • The Feedback hub and manage_feedback auto-enable wherever the portal and its thread store are configured; no platform.yaml changes are needed.

Changelog

Features

Others

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

Verification

All release artifacts are signed with Cosign. Verify with:

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