Skip to content

mcp-data-platform-v1.90.2

Choose a tag to compare

@github-actions github-actions released this 27 Jun 00:44
54bab03

A focused release that makes agents able to reliably attach entity references to a knowledge page. No migrations, no config changes; upgrading from v1.90.1 is drop-in. The one user-visible behavior addition is the new page.references input on apply_knowledge.

The problem

Citing an entity on a knowledge page was unreliable. The only path was embedding a reference token in the page body, and the platform's own guidance ("cite the reference string") led an agent to wrap that token in backticks. The body scanner intentionally ignores code spans (a token shown in backticks is treated as a documentation example), so the citation silently produced no stored reference and no rendered link.

What's new and fixed

Guidance that actually produces a reference

The agent instructions and the knowledge-apply guidance now state the rule explicitly: to make a citation a tracked, clickable reference, write it in plain text or a markdown link, or pass it in page.references. A reference wrapped in backticks or a fenced code block is treated as an example and is intentionally ignored. The docs also correct two inaccuracies: only internal (mcp:) references are existence-checked (a DataHub urn:li: reference is free text, stored as given), and the stale note that schema_entity insights are rejected from the page sink (that gate was removed in v1.90.0).

Explicit references on apply

apply_knowledge with sink=knowledge_page now accepts an optional page.references list of serialized reference strings (mcp:asset:<id>, mcp:prompt:<uuid>, mcp:collection:<id>, mcp:knowledge_page:<id>, mcp:connection:(kind,name), or a DataHub urn:li:...). This is a structured, format-proof citation path that does not depend on body formatting:

  • Each entry is parsed up front; a malformed or cross-namespace (urn:li:mcp:...) entry is a clean error rather than a silently dropped citation.
  • Internal references are existence-checked before the page is written, so a citation to a missing entity rejects the apply with nothing written. The list is capped at 50 entries.
  • Explicit references attach with the promotion, so they appear in the changeset and are undone by a rollback, and they never collide with references added through the portal's manual picker.

No more partial pages or over-blocking

References carried from a source insight, and references scanned from the page body, are now filtered to those that still exist. A deleted entity or a stale mcp: token typed in prose is skipped rather than failing the reference write after the page row was already created. Previously such a stale reference could leave a partially written page with the source insights unapplied.

A target cited both explicitly and in the body is stored once as a single durable reference.

Upgrade notes

Drop-in from v1.90.1. The new page.references field is optional and additive; existing apply_knowledge callers are unaffected.

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

Verification

All release artifacts are signed with Cosign. Verify with:

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