Repository navigation
Releases
mcp-datahub-v1.15.1
A correctness release for the three by-URN reads, plus a dependency and Go toolchain rollup.
Upgrade if any consumer relies on GetEntity, GetGlossaryTerm or GetDataProduct returning an error for an entity that does not exist. Before this release those three reads silently reported nonexistent entities as found.
Bug Fixes
Missing entities were reported as found (#204, #205)
GetEntity, GetGlossaryTerm and GetDataProduct decided an entity was missing by testing whether the GraphQL response echoed an empty URN. Against a real DataHub that test never fires — the entity resolvers hydrate a stub from the key aspect, returning the URN that was asked for, a name derived from it, no GraphQL error, and every real aspect null.
Verified against DataHub v1.6.0:
glossaryTerm(urn: "urn:li:glossaryTerm:Qa1605Nonexistent")
-> {"urn":"urn:li:glossaryTerm:Qa1605Nonexistent","exists":false,"name":"Qa1605Nonexistent","properties":null}
dataProduct(urn: "urn:li:dataProduct:qa-1605-nonexistent")
-> {"urn":"urn:li:dataProduct:qa-1605-nonexistent","properties":null}
A caller following the documented error-on-missing contract got a stub back and could not tell it from a real entity that happens to be undocumented. The glossary-term stub was the most convincing: its name is the URN's id segment, which is exactly what a real term's name usually is.
Each read now uses the signal its entity type actually offers, following the rule GetGlossaryNodeChildren already used:
| Read | Signal |
|---|---|
GetEntity |
exists, selected inside each inline fragment — the field lives on the concrete types, not on the Entity interface |
GetGlossaryTerm |
exists on the term |
GetDataProduct |
properties == nil — DataProduct has no exists field, and a product cannot be created without dataProductProperties |
GetEntityQuery also gained GlossaryTerm and GlossaryNode fragments, since rawAspectReadTypes routes those URNs through GetEntity for tag enrichment and both types carry exists.
Behaviour change: these three reads now return ErrNotFound where they previously returned a populated struct and a nil error. Code that treated a successful return as proof of existence will start seeing errors it did not see before — that is the fix, but it is a visible change at the call site.
Known limitation: Domain and Tag are still indistinguishable from their stubs. Neither type has an exists field in any DataHub schema version, and neither has a properties aspect that is mandatory at creation, so there is no honest absence signal to substitute. GetEntity on a nonexistent domain or tag URN still returns a stub.
Compatibility: unchanged. Only a definitive exists: false means absent — a DataHub version that omits the field leaves the pointer nil and the entity still stands, so older servers behave exactly as they did before.
Security
The Go toolchain moved from go1.26.4 to go1.26.8, clearing four called standard-library advisories that govulncheck flags on the previous toolchain (all fixed in go1.26.6):
| Advisory | Issue | Reached via |
|---|---|---|
| GO-2026-6218 | Quadratic resolvePath in net/url |
client.doRequest → http.Client.Do |
| GO-2026-6090 | Post-handshake message limit in crypto/tls |
client.doRequest → tls.Conn.Read |
| GO-2026-5972 | encoding/asn1 recursion depth |
extensions.LoggingMiddleware.After |
| GO-2026-5026 | ASCII-only Punycode labels in x/net/idna |
net/http |
Released binaries and container images are built with go1.26.8. Library consumers get the fix by building with go1.26.6 or newer — the toolchain directive in go.mod requests it, but your own build's toolchain is what ships in your binary.
Dependencies
| Dependency | From | To |
|---|---|---|
github.com/modelcontextprotocol/go-sdk |
v1.6.1 | v1.7.0 |
golang.org/x/sync (indirect, new) |
— | v0.20.0 |
golang.org/x/time (indirect, new) |
— | v0.15.0 |
github/codeql-action/* |
v4.37.3 | v4.37.4 |
ossf/scorecard-action |
v2.4.3 | v2.4.4 |
docker/login-action |
v4.4.0 | v4.6.0 |
docker/setup-buildx-action |
v4.2.0 | v4.3.0 |
anchore/sbom-action/download-syft |
v0.24.0 | v0.24.2 |
Supersedes Dependabot PRs #196, #197, #198, #201, #202, #203.
Unchanged
No changes to the tool surface: still 12 tools (9 read, 3 write). No config, environment variable, or MCP schema changes. Minimum supported DataHub stays v1.3.x, with the full feature set at v1.4.x+; queries are validated against the v1.5.0.1 schema and the fix was verified against a live v1.6.0.
Full changelog: v1.15.0...v1.15.1
Installation
Claude Desktop (macOS/Windows)
Download the .mcpb bundle for your platform and double-click to install:
- macOS Apple Silicon (M1/M2/M3/M4):
mcp-datahub_1.15.1_darwin_arm64.mcpb - macOS Intel:
mcp-datahub_1.15.1_darwin_amd64.mcpb - Windows:
mcp-datahub_1.15.1_windows_amd64.mcpb
Homebrew (macOS)
brew install txn2/tap/mcp-datahubClaude Code CLI
claude mcp add datahub \
-e DATAHUB_URL=https://your-datahub.example.com/api/graphql \
-e DATAHUB_TOKEN=your-token \
-- mcp-datahubGo library
go get github.com/txn2/mcp-datahub@v1.15.1Docker
docker pull ghcr.io/txn2/mcp-datahub:v1.15.1Verification
All release artifacts are signed with Cosign. Verify with:
cosign verify-blob --bundle mcp-datahub_1.15.1_linux_amd64.tar.gz.sigstore.json \
mcp-datahub_1.15.1_linux_amd64.tar.gzmcp-datahub-v1.15.0
Highlights
The business glossary is browsable as a tree. Until now the client could look up an individual glossary term or search terms by name, but it could not create a glossary node, list the top of the glossary, walk a node's children, or place a term in its branch. This release adds glossary node creation and full hierarchy enumeration to the client library.
Library-only release. No new MCP tools, no changes to any existing tool, and no behaviour change for existing term operations — get, create-with-parent, delete, and description update are untouched. If you use mcp-datahub as a server, nothing about your setup changes.
What's new
Glossary node create and hierarchy enumeration (#199, #200)
// Create
CreateGlossaryNode(ctx, name, definition, parentNode string) (string, error)
// Enumerate
GetRootGlossaryNodes(ctx, start, count int) ([]types.GlossaryNode, int, error)
GetRootGlossaryTerms(ctx, start, count int) ([]types.GlossaryTerm, int, error)
GetGlossaryNodeChildren(ctx, nodeURN string, start, count int) (*types.GlossaryChildren, error)
GetGlossaryParentChain(ctx, urn string) ([]types.GlossaryNode, error)Two new domain types in pkg/types:
// A directory in the glossary.
type GlossaryNode struct {
URN, Name, Description, ParentNode string
TermsCount, NodesCount int // DataHub's own childrenCount tally
}
// A page of what sits directly under a node. DataHub returns child nodes and
// child terms as one mixed result set, so Start/Count/Total describe the
// combined page rather than either slice on its own.
type GlossaryChildren struct {
Nodes []GlossaryNode
Terms []GlossaryTerm
Start, Count, Total int
}Root and children enumeration are paged via start/count and surface total, so a caller can walk a large glossary. count falls back to DefaultLimit when non-positive and is clamped to MaxLimit.
Walking the tree
// Top of the glossary.
nodes, total, err := c.GetRootGlossaryNodes(ctx, 0, 50)
// One level down. Nodes and terms arrive together.
children, err := c.GetGlossaryNodeChildren(ctx, nodes[0].URN, 0, 50)
for _, n := range children.Nodes { /* sub-directories */ }
for _, t := range children.Terms { /* terms in this directory */ }
// Where does a term live? Direct parent first, up to the root.
chain, err := c.GetGlossaryParentChain(ctx, "urn:li:glossaryTerm:arr")Each node in a parent chain carries its own ParentNode (the next link up), so the branch can be rebuilt without a second round trip.
Behaviour worth knowing
Both of these were found by running against a live DataHub, not inferred from the schema.
Children lag writes. A node's children are served from DataHub's graph index, which is populated asynchronously through its MCL consumers. A term or node created moments earlier will not appear in GetGlossaryNodeChildren immediately. If you are building an interactive glossary browser, expect to poll or refresh after a create rather than reading back straight away.
GetGlossaryParentChain reads the entity itself and is immediately consistent, so prefer it when confirming a just-written parent.
Unknown nodes return ErrNotFound. DataHub answers a lookup of a missing glossary node with an empty stub rather than an error, which is indistinguishable from a node that simply has no children. The client selects exists and converts that case to ErrNotFound. It is decoded through a pointer, so a DataHub version that omits the field is not misread as "absent" — only a definitive false counts.
Non-glossary URNs are rejected. GetGlossaryParentChain and GetGlossaryNodeChildren return ErrInvalidURN for a URN that is not a glossary term / node, rather than silently returning an empty result that reads as "this is at the root".
How children are enumerated
DataHub's RelationshipsInput.types is a free-form [String!]!, so the GraphQL schema does not name the relationship used for glossary parentage — it cannot be read out of entity.graphql. It was determined empirically against a live DataHub v1.6.0 instance rather than guessed. A node's children are the INCOMING side of the IsPartOf relationship on the parent:
glossaryNode(urn: $urn) {
children: relationships(input: {types: ["IsPartOf"], direction: INCOMING, start: 0, count: 100}) {
total start count
relationships { entity { urn type ... } }
}
}Verified against a real tree (root → child node → grandchild term, plus a child term): the edge returns both kinds of children, pages correctly on start/count, and its total matches the node's own childrenCount (termsCount + nodesCount). This also matches how DataHub's own UI fetches node children, so the relationship name is not an artifact of one deployment.
Compatibility
No change to the minimum supported DataHub version. Every mechanism used here is present in entity.graphql at the v1.3.0 tag — the project's documented floor — verified against the upstream repository:
| Mechanism | Present at v1.3.0 |
|---|---|
createGlossaryNode |
entity.graphql:763 |
getRootGlossaryTerms / getRootGlossaryNodes |
:180 / :187 |
GlossaryNode.childrenCount |
:2693 |
ParentNodesResult |
:2718 |
All four new queries are registered in TestGraphQLQueriesMatchSchema and validated against the pinned schema (v1.5.0.1) on every make schema-check.
This release is fully backward compatible: additive API only, no signature changes, no behaviour changes to existing calls.
Fixed
The integration test suite no longer compiled. getAspect, readGlobalTags, readGlossaryTerms, and readInstitutionalMemory had each gained an entityType parameter that write_integration_test.go was never updated for, so make test-integration failed at build time. Fixed — the full integration suite builds and passes against DataHub v1.6.0 again. This affects contributors only; no shipped behaviour changed.
Verification
make verifyclean — lint 0 issues across 43 linters, coverage 93.0% (client package 95.1%), schema-check, gosec, govulncheck, build-check- Patch coverage 182/182 changed lines = 100%
make test-integrationgreen against a live DataHub v1.6.0, including a newTestIntegrationGlossaryHierarchythat builds a glossary tree, enumerates it every way the API supports, cross-checkschildrenCount, and cleans up after itself- Unit coverage via GraphQL httptest mocks: field mapping, the mixed node/term split, relationship input, paging clamps,
existshandling in both directions, parent-chain ordering and linkage, and URN rejection
Note on versioning
There is no v1.14.0 release. A tag was cut against a stale commit during a merge race and contained no changes over v1.13.0; the release was removed and this one cut from the correct commit. Nothing was lost — v1.14.0 was byte-identical to v1.13.0. Upgrade from v1.13.0 straight to v1.15.0.
Installation
Claude Desktop (macOS/Windows)
Download the .mcpb bundle for your platform and double-click to install:
- macOS Apple Silicon (M1/M2/M3/M4):
mcp-datahub_1.15.0_darwin_arm64.mcpb - macOS Intel:
mcp-datahub_1.15.0_darwin_amd64.mcpb - Windows:
mcp-datahub_1.15.0_windows_amd64.mcpb
Homebrew (macOS)
brew install txn2/tap/mcp-datahubClaude Code CLI
claude mcp add datahub \
-e DATAHUB_URL=https://your-datahub.example.com/api/graphql \
-e DATAHUB_TOKEN=your-token \
-- mcp-datahubGo library
go get github.com/txn2/mcp-datahub@v1.15.0Docker
docker pull ghcr.io/txn2/mcp-datahub:v1.15.0Verification of artifacts
All release artifacts are signed with Cosign. Verify with:
cosign verify-blob --bundle mcp-datahub_1.15.0_linux_amd64.tar.gz.sigstore.json \
mcp-datahub_1.15.0_linux_amd64.tar.gzChangelog
Full Changelog: v1.13.0...v1.15.0
mcp-datahub-v1.13.0
Highlights
datahub_update no longer erases a description when the new text arrives in the description parameter instead of value. That call wrote an empty string and answered {"action": "updated"}, so a documentation pass could report success while clearing the very fields it was meant to fill.
Fixed
Description updates resolve their text from value or description (#194, #195)
datahub_update with what: description or what: column_description took the new text from value only. The same input schema also exposes a description parameter — the field what: query, incident, and structured_property use — so text sent there left value empty and the handler wrote an empty string.
The empty write was destructive rather than inert. editableFieldInfo.Description is omitempty, so the schema field entry was rewritten without a description: the column's existing text was gone while the response still reported updated.
Both handlers now resolve the text through one rule:
valueis authoritative.descriptionis used whenvalueis empty.- Both set to different text is rejected, mirroring how
target_urnandvalueare reconciled for association operations. - Neither set is refused with
value (the description text) parameter is required.
For column_description the missing-field_path error still takes precedence, so a call missing both is told the more specific problem.
Behavior change. A description update carrying no text is now an error instead of a write. datahub_update what=description value="" previously cleared an entity's description; that path is gone. Clearing by omission is indistinguishable from the misdirected-field case above, and that case silently destroys text.
Surfaced downstream as txn2/mcp-data-platform#1102.
Documentation
- The tools reference states which of
valueanddescriptioneachwhatvalue uses, matching the parameter descriptions in the tool schema. (#195) - Documentation site re-skin, keeping the txn2 sister sites visually parity-mapped: Geist and Geist Mono type in place of the Fraunces display serif, a graphite ground with a single cyan accent, the project symbol on the homepage rail, de-railed admonitions where type is signalled by title and icon color, and a trimmed feature list. (#184)
CI and supply chain
Every GitHub Action remains pinned to a SHA digest.
actions/checkout7.0.0 to 7.0.1 (#193)actions/setup-go6.5.0 to 7.0.0 (#192)actions/setup-python6.3.0 to 7.0.0 (#192)github/codeql-action4.37.0 to 4.37.3 (#192)golang/govulncheck-action1.0.4 to 1.1.0 (#185)- Dependabot now groups
github/codeql-action*into a single pull request. Itsinit,autobuild,analyze, andupload-sarifsub-actions must run the same version: a partial bump makesinitwrite a configuration the olderautobuildrejects. (#192)
Compatibility
No exported Go API changed. UpdateInput keeps the same fields; only two jsonschema_description strings differ, so the tool's JSON schema advertises where description text belongs. Library consumers upgrade by bumping the module version, with no source changes.
MCP clients see one behavioral difference, described under Fixed: a description update that carries no text is now refused.
Changelog
Bug Fixes
Documentation
Others
- 56d0061: ci/deps: roll up open Dependabot action bumps (#192) (@cjimti)
- 71dd351: ci: bump actions/checkout from 7.0.0 to 7.0.1 (#193) (@dependabot[bot])
- 395f9ab: ci: bump golang/govulncheck-action from 1.0.4 to 1.1.0 (#185) (@dependabot[bot])
Installation
Claude Desktop (macOS/Windows)
Download the .mcpb bundle for your platform and double-click to install:
- macOS Apple Silicon (M1/M2/M3/M4):
mcp-datahub_1.13.0_darwin_arm64.mcpb - macOS Intel:
mcp-datahub_1.13.0_darwin_amd64.mcpb - Windows:
mcp-datahub_1.13.0_windows_amd64.mcpb
Homebrew (macOS)
brew install txn2/tap/mcp-datahubClaude Code CLI
claude mcp add datahub \
-e DATAHUB_URL=https://your-datahub.example.com/api/graphql \
-e DATAHUB_TOKEN=your-token \
-- mcp-datahubDocker
docker pull ghcr.io/txn2/mcp-datahub:v1.13.0Verification
All release artifacts are signed with Cosign. Verify with:
cosign verify-blob --bundle mcp-datahub_1.13.0_linux_amd64.tar.gz.sigstore.json \
mcp-datahub_1.13.0_linux_amd64.tar.gzmcp-datahub-v1.12.0
mcp-datahub v1.12.0
Maintenance and correctness release. The headline is a read-side bug fix for tag display names (created tags no longer render as UUIDs) plus a usability fix that lets datahub_update accept the association URN in value — eliminating a common avoidable failed round trip for AI agents. The rest is dependency and CI hardening.
No breaking changes. No schema-compatibility changes — still validated against DataHub v1.5.0.1 (minimum supported v1.3.x).
🐛 Bug Fixes
Created tags rendered as UUIDs on read (#180)
Tags created through datahub_create (without an explicit id) showed up as UUIDs on every subsequent read instead of the name you chose.
Root cause: DataHub's createTag mutation generates a UUID entity key when the input carries no id; the display name lands in the tagProperties.name aspect. The read path's tag fragments selected only the tag's top-level name, which DataHub derives from the entity key (deprecated in the GraphQL schema in favor of properties.name). For a UUID-keyed tag, that field is the UUID. Seeded tags with human-readable keys (e.g. urn:li:tag:PII) were unaffected, so the bug only bit tags created through this toolkit's own create→attach→read round trip.
Fix (read-side): Every tag fragment now also selects properties { name description } and prefers those values, falling back to the legacy top-level fields for older servers and key-named tags. Applied across all read paths:
datahub_search(SearchQuery)datahub_get_entity(GetEntityQuery)datahub_get_schemafield-level tags (GetSchemaQuery,BatchGetSchemasQuery)- document queries
The optional write-side change (passing id to createTag for human-readable URNs) was intentionally not made — the issue flagged it as cosmetic. The read-side fix alone resolves the observed defect.
✨ Enhancements
datahub_update accepts value as the association target (#181)
Attaching a tag/term/owner/domain required the association URN in target_urn, but agents frequently passed it in the generic value field — so a natural first attempt failed with target_urn parameter is required and only succeeded on retry.
Fix: New resolveTargetURN() logic, wired into the tag, glossary_term, owner, and domain (set) handlers:
target_urnstays authoritative.- A lone
valuecarrying a URN is now accepted. - Both set and equal → succeeds.
- Both set and different → rejected with a clear message (no silent guessing).
- Neither set → still errors, naming
target_urn.
Schema descriptions were also tightened so first attempts succeed more often: value now states it is not the association URN for add/remove/set (accepted only as a fallback), and target_urn documents which what/action combinations require it.
🔧 CI & Maintenance
- ci: roll up Dependabot GitHub Actions bumps (#183, closing #175/#176/#177/#178):
github/codeql-action(init,autobuild,analyze,upload-sarif) → v4.37.0 (all sub-actions kept in lockstep)docker/setup-buildx-action→ v4.2.0
- ci: bump
docker/login-action→ v4.4.0 (#179)
📦 What's Changed
- fix: tag display names on read (#180) and value-as-target in
datahub_update(#181) by @cjimti in #182 - ci: bump
docker/login-actionfrom 4.2.0 to 4.4.0 by @dependabot in #179 - ci: roll up dependabot action bumps (#175, #176, #177, #178) by @cjimti in #183
Full Changelog: v1.11.0...v1.12.0
Installation
Claude Desktop (macOS/Windows)
Download the .mcpb bundle for your platform and double-click to install:
- macOS Apple Silicon (M1/M2/M3/M4):
mcp-datahub_1.12.0_darwin_arm64.mcpb - macOS Intel:
mcp-datahub_1.12.0_darwin_amd64.mcpb - Windows:
mcp-datahub_1.12.0_windows_amd64.mcpb
Homebrew (macOS)
brew install txn2/tap/mcp-datahubClaude Code CLI
claude mcp add datahub \
-e DATAHUB_URL=https://your-datahub.example.com/api/graphql \
-e DATAHUB_TOKEN=your-token \
-- mcp-datahubDocker
docker pull ghcr.io/txn2/mcp-datahub:v1.12.0Verification
All release artifacts are signed with Cosign. Verify with:
cosign verify-blob --bundle mcp-datahub_1.12.0_linux_amd64.tar.gz.sigstore.json \
mcp-datahub_1.12.0_linux_amd64.tar.gzmcp-datahub-v1.11.0
Highlights
This release adds two client capabilities requested for downstream metadata curation (#173) and fixes two write-path defects that were surfaced while validating those features against a live DataHub instance. Everything below was validated end-to-end against DataHub v1.6.0 (latest OSS) on both the v1 (Rest.li) and v3 (OpenAPI) API paths.
✨ New capabilities (#173)
Edit a tag's description. Client.UpdateDescription now accepts tag URNs (urn:li:tag:...), routing them through the GraphQL updateDescription mutation — the same path already used for domains and glossary terms/nodes. Previously a tag URN returned ErrUnsupportedEntityType, so a tag with a stale definition could only be deleted, not corrected. Also reachable through the datahub_update tool with what: "description".
Write non-structured customProperties. Two new client methods manage the legacy customProperties map (distinct from structured properties):
SetCustomProperties(ctx, urn, map[string]string)— set or overwrite keysRemoveCustomProperties(ctx, urn, []string)— delete keys
Both use REST read-modify-write and preserve every other field on the aspect (e.g. glossaryTermInfo.termSource). Supported entity types were verified against the upstream DataHub PDL models: dataset, dashboard, chart, dataFlow, dataJob, container, dataProduct, glossaryTerm, glossaryNode, and domain. tag is intentionally unsupported (its tagProperties aspect has no customProperties field) and returns ErrUnsupportedCustomPropertiesEntity.
Exposed through the reference datahub_update tool as what: "custom_properties" (action: set | remove) — no new tool was added; the toolkit still exposes 12 tools.
🐛 Bug fixes (write path)
These two defects affected the write path broadly — not just the new features — and were masked by unit-test mocks. They were caught only by exercising the client against a real DataHub instance.
v3 writes no longer fail on existing aspects. The OpenAPI v3 writer posted with default CREATE semantics, so any read-modify-write (UpdateDescription, AddTag, AddGlossaryTerm, custom properties, …) returned HTTP 400 — "Cannot perform CREATE since the aspect already exists" whenever the target aspect was already present. Writes now use createIfNotExists=false (UPSERT), which correctly creates when absent and updates when present.
v1 read-modify-write no longer drops existing data. On the legacy Rest.li path the client parsed only the v3 {"value": …} envelope, but the v1 GET returns {"aspect": {"<class>": …}}. As a result every v1 read-modify-write started from an empty aspect and silently discarded existing tags, terms, and links (and failed with 422 on aspects that have required fields). Because the default DATAHUB_API_VERSION is v1, this affected the default configuration. The client now parses the Rest.li envelope correctly (and tolerates a normalized flat body).
✅ Validation matrix (live, DataHub v1.6.0)
| Check | v3 | v1 |
|---|---|---|
| Tag description persists | ✅ | ✅ |
glossaryTerm customProperties set + remove |
✅ | ✅ |
domain customProperties set + remove |
✅ | ✅ |
dataset customProperties set + remove |
✅ | ✅ |
AddTag preserves existing tags |
✅ | ✅ |
AddGlossaryTerm / AddLink preserve existing entries |
✅ | ✅ |
⬆️ Upgrade notes
- No breaking API changes; the new methods are additive.
- If you run against the default v1 API path, the fix restores correct read-modify-write behavior — earlier versions could drop existing tags/terms/links on the v1 path. No action required beyond upgrading.
- Custom properties require an aspect that carries
customProperties; unsupported entity types returnErrUnsupportedCustomPropertiesEntity.
Changelog
Features
Others
- e7837fa: ci: bump docker/setup-qemu-action from 4.1.0 to 4.2.0 (#171) (@dependabot[bot])
- b29d61e: ci: bump golangci/golangci-lint-action from 9.2.1 to 9.3.0 (#172) (@dependabot[bot])
- 781aaff: ci: bump goreleaser/goreleaser-action from 7.2.2 to 7.2.3 (#170) (@dependabot[bot])
Installation
Claude Desktop (macOS/Windows)
Download the .mcpb bundle for your platform and double-click to install:
- macOS Apple Silicon (M1/M2/M3/M4):
mcp-datahub_1.11.0_darwin_arm64.mcpb - macOS Intel:
mcp-datahub_1.11.0_darwin_amd64.mcpb - Windows:
mcp-datahub_1.11.0_windows_amd64.mcpb
Homebrew (macOS)
brew install txn2/tap/mcp-datahubClaude Code CLI
claude mcp add datahub \
-e DATAHUB_URL=https://your-datahub.example.com/api/graphql \
-e DATAHUB_TOKEN=your-token \
-- mcp-datahubDocker
docker pull ghcr.io/txn2/mcp-datahub:v1.11.0Verification
All release artifacts are signed with Cosign. Verify with:
cosign verify-blob --bundle mcp-datahub_1.11.0_linux_amd64.tar.gz.sigstore.json \
mcp-datahub_1.11.0_linux_amd64.tar.gzmcp-datahub-v1.10.2
Overview
Patch release fixing a read gap for tags and glossary terms on GraphQL-only entity types. Library consumers can now read back the globalTags / glossaryTerms they write to domain, glossaryTerm, and glossaryNode entities.
Bug Fixes
Read tags/terms for GraphQL-only entity types (#168, #169)
domain, glossaryTerm, and glossaryNode could have tags and glossary terms written (via the addTag / removeTag / addTerm / removeTerm GraphQL mutations) but their associations could not be read back. GetEntity returned an empty Tags / GlossaryTerms set for these three types.
Root cause
- These types do not expose typed
tags: GlobalTags/glossaryTerms: GlossaryTermsGraphQL fields (verified against the upstream DataHub schema at v1.5.0.1). - The REST aspect API does not register
globalTags/glossaryTermsfor them — which is exactly why their writes already route through GraphQL. GetEntityQueryonly carried typed inline fragments forDatasetandDashboard, so every other type returned empty tags/terms.
Impact (for downstream consumers, e.g. txn2/mcp-data-platform)
- Post-write verification of tags/terms was impossible for these entity types.
- A rollback relying on a pre-change before-image could remove a tag/term the entity already had, because the "kept pre-existing" guard saw an empty prior set.
Fix
GetEntity now populates Tags / GlossaryTerms for domain / glossaryTerm / glossaryNode by reading the globalTags and glossaryTerms raw aspects through DataHub's experimental aspects(input:) API — the only GraphQL read path these types expose for this data. The read:
- runs as a separate
GetEntityAspectsQuery, so it degrades gracefully — any failure (older DataHub, unauthorized token) leaves the associations empty and logs at debug level rather than failing the wholeGetEntitycall, matching the existingGetIncidents/GetStructuredPropertiesfallback pattern; - reuses the same aspect structs the write path serializes, so payload shapes stay consistent;
- adds no new tools and no new public API — existing
GetEntity(and thedatahub_get_entitytool) simply return more data for these types.
Known limitation
Raw aspect payloads carry only URNs, so Name / Description are left empty for tags/terms on these three types. URNs are sufficient for the post-write verification and rollback before-image use cases that motivated the issue. Tags/terms on Dataset / Dashboard are unaffected and continue to include names.
Compatibility
The experimental aspects field predates the minimum supported DataHub (1.3.x). On instances where it is unavailable or unauthorized, the read degrades to empty instead of erroring. No configuration changes required.
Changelog
Full diff: v1.10.1...v1.10.2
Installation
Claude Desktop (macOS/Windows)
Download the .mcpb bundle for your platform and double-click to install:
- macOS Apple Silicon (M1/M2/M3/M4):
mcp-datahub_1.10.2_darwin_arm64.mcpb - macOS Intel:
mcp-datahub_1.10.2_darwin_amd64.mcpb - Windows:
mcp-datahub_1.10.2_windows_amd64.mcpb
Homebrew (macOS)
brew install txn2/tap/mcp-datahubClaude Code CLI
claude mcp add datahub \
-e DATAHUB_URL=https://your-datahub.example.com/api/graphql \
-e DATAHUB_TOKEN=your-token \
-- mcp-datahubDocker
docker pull ghcr.io/txn2/mcp-datahub:v1.10.2Verification
All release artifacts are signed with Cosign. Verify with:
cosign verify-blob --bundle mcp-datahub_1.10.2_linux_amd64.tar.gz.sigstore.json \
mcp-datahub_1.10.2_linux_amd64.tar.gzmcp-datahub-v1.10.1
Highlights
Patch release. Fixes a document visibility leak in GetRelatedDocuments: documents that a steward explicitly hid from global context (showInGlobalContext = false) could be surfaced through entity-keyed lookups, because the hide flag never traveled on that path. Anyone using GetRelatedDocuments for visibility-gated document discovery should upgrade.
No API changes, no breaking changes.
Bug fix
GetRelatedDocuments now returns the full document projection (#166, #167)
GetRelatedDocuments(ctx, urn) returned a thinner projection than GetDocument and SearchDocuments. Each per-entity ... on Document block in the query requested a hand-written subset (urn, subType, title, contents, status) and omitted settings{showInGlobalContext} and relatedAssets — even though the response parse struct and mapping already supported both fields. Every related document therefore parsed with Settings == nil and an empty RelatedAssets.
Impact. A steward sets showInGlobalContext = false to keep a context document out of global search. A caller doing an entity-keyed lookup (GetRelatedDocuments for a dataset the hidden document links to) received that document with Settings == nil. Because DataHub's documented default for global_context is true, a correct consumer treats absent settings as visible — and surfaces a document the steward explicitly hid. The same document fetched via GetDocument or SearchDocuments carried the flag and was correctly suppressed, so a document leaked through one path only. Provenance was also lost, since relatedAssets (what the document is about) was always empty.
Fix. The four relatedDocuments blocks now reuse the shared documentSelectionFields fragment (added in v1.10.0 for GetDocument/SearchDocuments). Related documents now carry the identical projection — settings, relatedAssets, status, subType, owners, tags, glossary terms, and domain — from a single source of truth, so the projection can no longer drift between document accessors. A regression test asserts a related document returned with showInGlobalContext: false and a relatedAssets entry parses with Settings.ShowInGlobalContext == false and the related-asset URN populated.
Compatibility. Documents are a DataHub 1.4.x+ feature; this path requires DataHub 1.4.x or later. The expanded query is validated against the pinned upstream schema (v1.5.0.1) by make schema-check.
Upgrade notes
Drop-in for existing users. The fix only adds fields to the GraphQL selection and populates struct fields that were previously always nil/empty. No signatures changed and no existing behavior was altered.
Callers that gate document visibility off Settings.ShowInGlobalContext will now see the real flag on related documents instead of nil. If your code previously treated Settings == nil as "visible" on this path, it will now correctly suppress hidden documents.
Full changelog: v1.10.0...v1.10.1
Installation
Claude Desktop (macOS/Windows)
Download the .mcpb bundle for your platform and double-click to install:
- macOS Apple Silicon (M1/M2/M3/M4):
mcp-datahub_1.10.1_darwin_arm64.mcpb - macOS Intel:
mcp-datahub_1.10.1_darwin_amd64.mcpb - Windows:
mcp-datahub_1.10.1_windows_amd64.mcpb
Homebrew (macOS)
brew install txn2/tap/mcp-datahubClaude Code CLI
claude mcp add datahub \
-e DATAHUB_URL=https://your-datahub.example.com/api/graphql \
-e DATAHUB_TOKEN=your-token \
-- mcp-datahubDocker
docker pull ghcr.io/txn2/mcp-datahub:v1.10.1Verification
All release artifacts are signed with Cosign. Verify with:
cosign verify-blob --bundle mcp-datahub_1.10.1_linux_amd64.tar.gz.sigstore.json \
mcp-datahub_1.10.1_linux_amd64.tar.gzmcp-datahub-v1.10.0
Highlights
Document discovery for the client library. This release adds Client.SearchDocuments, the first way to find DataHub context documents without already knowing a URN. Every prior document accessor (GetDocument, GetRelatedDocuments, GetContextDocuments) was a point lookup, so context-document knowledge could only be read if you already held the URN or a related entity's URN. SearchDocuments answers "what documents exist?" and "find documents about X."
The rest of the release is routine CI, Docker, and GitHub Action dependency maintenance. There are no breaking changes.
What's new
SearchDocuments — relevance search and listing for context documents (#164, #165)
A new client method:
func (c *Client) SearchDocuments(
ctx context.Context,
query string,
opts ...SearchOption,
) ([]types.Document, error)- Runs DataHub's
searchAcrossEntitiesGraphQL scoped to theDOCUMENTentity type. query = "*"lists every document; a text query ranks by relevance.- Honors the existing search options (
WithLimit,WithOffset,WithSearchFilters) and caps results toMaxLimit. - Each hit returns the same metadata as
GetDocument: URN, title, sub-type, related-asset URNs,showInGlobalContext, ownership, tags, glossary terms, and domain. A consumer can filter to globally-visible documents or surface the rest for a backfill.
// Find documents about incidents
docs, err := c.SearchDocuments(ctx, "incident runbook", client.WithLimit(20))
// List all documents
all, err := c.SearchDocuments(ctx, "*")Why a library method and not a new MCP tool. This is a composable building block, in keeping with the toolkit's design. It unblocks txn2/mcp-data-platform#692: with document search available upstream, the platform can add a DataHub-documents source to its unified search so context-document knowledge becomes discoverable and migratable into knowledge pages — a new search source, not a new tool. The MCP tool count is unchanged (still 12).
Compatibility. Documents are a DataHub 1.4.x+ feature; SearchDocuments requires DataHub 1.4.x or later. The query is validated against the pinned upstream schema (v1.5.0.1) by make schema-check.
Under the hood
- A shared
documentSelectionFieldsGraphQL fragment now backs bothGetDocumentQueryandSearchDocumentsQuery, so single-document reads and document search always return identical metadata from one source of truth (no field drift). - A shared
buildBaseSearchInputhelper consolidates the query/offset/limit/filter input-building previously duplicated across the search paths. - Added the
EntityTypeDocumentconstant.
Dependency updates
- GitHub Actions:
actions/checkout6.0.3 → 7.0.0 (#161),actions/setup-go6.4.0 → 6.5.0 (#162),actions/setup-python6.2.0 → 6.3.0 (#163),codecov/codecov-action6.0.1 → 7.0.0 (#159),github/codeql-action4.36.1 → 4.36.2 (#158) - Docker: Alpine base 3.23 → 3.24 (#157) and digest pin refresh (#160)
Upgrade notes
Drop-in for existing users. SearchDocuments is purely additive — no signatures changed and no behavior of existing methods was altered. Library consumers calling document search need DataHub 1.4.x+.
Full changelog: v1.9.0...v1.10.0
Installation
Claude Desktop (macOS/Windows)
Download the .mcpb bundle for your platform and double-click to install:
- macOS Apple Silicon (M1/M2/M3/M4):
mcp-datahub_1.10.0_darwin_arm64.mcpb - macOS Intel:
mcp-datahub_1.10.0_darwin_amd64.mcpb - Windows:
mcp-datahub_1.10.0_windows_amd64.mcpb
Homebrew (macOS)
brew install txn2/tap/mcp-datahubClaude Code CLI
claude mcp add datahub \
-e DATAHUB_URL=https://your-datahub.example.com/api/graphql \
-e DATAHUB_TOKEN=your-token \
-- mcp-datahubDocker
docker pull ghcr.io/txn2/mcp-datahub:v1.10.0Verification
All release artifacts are signed with Cosign. Verify with:
cosign verify-blob --bundle mcp-datahub_1.10.0_linux_amd64.tar.gz.sigstore.json \
mcp-datahub_1.10.0_linux_amd64.tar.gzmcp-datahub-v1.9.0
Highlights
datahub_get_data_product now returns constituent datasets (#156)
datahub_get_data_product advertised that it returns a data product's "constituent datasets" and lets you "discover all its member datasets," but it never returned them: the underlying query did not request members and the assets field was always empty.
This release fetches a data product's members through the DataHub DataProduct.entities GraphQL resolver and returns them in the assets field. Each asset includes its urn, name, and type:
{
"urn": "urn:li:dataProduct:customer-360",
"name": "Customer 360",
"domain": { "name": "Sales", "urn": "urn:li:domain:sales" },
"owners": [ { "name": "Customer Data Team", "type": "DATAOWNER" } ],
"assets": [
{ "urn": "urn:li:dataset:(urn:li:dataPlatform:snowflake,prod.customer360.profile,PROD)", "name": "profile", "type": "DATASET" },
{ "urn": "urn:li:dataset:(urn:li:dataPlatform:snowflake,prod.customer360.interactions,PROD)", "name": "interactions", "type": "DATASET" }
]
}Behavior notes:
- Members are fetched in a separate, best-effort query. A DataHub instance whose schema does not expose the data product entities resolver returns the product without members rather than failing the whole lookup.
- The
assetsfield shape is now an array of objects (urn,name,type), matching the documented output schema and API reference. Previously the field was typed as a list of URN strings and never populated.
Build hardening (#156)
Pinned toolchain go1.26.4 in go.mod so the build uses the patched standard library, clearing reachable govulncheck findings GO-2026-5039 (net/textproto) and GO-2026-5037 (crypto/x509). The repository previously had no toolchain directive, so builds floated to whatever Go version was installed.
Dependencies and CI
github.com/modelcontextprotocol/go-sdk1.4.1 -> 1.6.1 (#132, #141, #149)- Documentation site re-skinned to the txn2 identity (#139)
- Routine CI action and base image bumps (checkout, codeql-action, goreleaser-action, cosign-installer, docker actions, alpine, and others)
Upgrade notes
The assets field in datahub_get_data_product output changed from a list of URN strings (never populated in prior releases) to a list of objects with urn, name, and type. Consumers that read assets should expect objects. Because the field was empty in prior releases, no real payload shape is broken by this change.
Changelog
Features
Others
- 9f59552: ci: bump actions/checkout from 6.0.2 to 6.0.3 (#155) (@dependabot[bot])
- a020b50: ci: bump actions/upload-artifact from 7.0.0 to 7.0.1 (#134) (@dependabot[bot])
- c76f6af: ci: bump actions/upload-pages-artifact from 4.0.0 to 5.0.0 (#135) (@dependabot[bot])
- d72f362: ci: bump codecov/codecov-action from 6.0.0 to 6.0.1 (#146) (@dependabot[bot])
- 2eabf85: ci: bump docker/login-action from 4.0.0 to 4.1.0 (#133) (@dependabot[bot])
- 89d051d: ci: bump docker/login-action from 4.1.0 to 4.2.0 (#151) (@dependabot[bot])
- 601ae33: ci: bump docker/setup-buildx-action from 4.0.0 to 4.1.0 (#150) (@dependabot[bot])
- e19e3bd: ci: bump docker/setup-qemu-action from 4.0.0 to 4.1.0 (#148) (@dependabot[bot])
- 929bf01: ci: bump github/codeql-action from 4.35.1 to 4.35.2 (#136) (@dependabot[bot])
- 38f1133: ci: bump github/codeql-action from 4.35.2 to 4.35.3 (#142) (@dependabot[bot])
- a95446d: ci: bump github/codeql-action from 4.35.3 to 4.35.5 (#144) (@dependabot[bot])
- d162bed: ci: bump github/codeql-action from 4.35.5 to 4.36.0 (#152) (@dependabot[bot])
- 331e4b7: ci: bump github/codeql-action from 4.36.0 to 4.36.1 (#154) (@dependabot[bot])
- f38abf6: ci: bump golangci/golangci-lint-action from 9.2.0 to 9.2.1 (#153) (@dependabot[bot])
- 5e708e2: ci: bump goreleaser/goreleaser-action from 7.0.0 to 7.1.0 (#138) (@dependabot[bot])
- abb80c0: ci: bump goreleaser/goreleaser-action from 7.1.0 to 7.2.1 (#140) (@dependabot[bot])
- f32293b: ci: bump goreleaser/goreleaser-action from 7.2.1 to 7.2.2 (#145) (@dependabot[bot])
- 265fa09: ci: bump sigstore/cosign-installer from 4.1.1 to 4.1.2 (#143) (@dependabot[bot])
- a898dee: deps: bump github.com/modelcontextprotocol/go-sdk from 1.4.1 to 1.5.0 (#132) (@dependabot[bot])
- 55fa7af: deps: bump github.com/modelcontextprotocol/go-sdk from 1.5.0 to 1.6.0 (#141) (@dependabot[bot])
- 2f9388d: deps: bump github.com/modelcontextprotocol/go-sdk from 1.6.0 to 1.6.1 (#149) (@dependabot[bot])
- f2366eb: docker: bump alpine from
2510918to5b10f43(#137) (@dependabot[bot])
Installation
Claude Desktop (macOS/Windows)
Download the .mcpb bundle for your platform and double-click to install:
- macOS Apple Silicon (M1/M2/M3/M4):
mcp-datahub_1.9.0_darwin_arm64.mcpb - macOS Intel:
mcp-datahub_1.9.0_darwin_amd64.mcpb - Windows:
mcp-datahub_1.9.0_windows_amd64.mcpb
Homebrew (macOS)
brew install txn2/tap/mcp-datahubClaude Code CLI
claude mcp add datahub \
-e DATAHUB_URL=https://your-datahub.example.com/api/graphql \
-e DATAHUB_TOKEN=your-token \
-- mcp-datahubDocker
docker pull ghcr.io/txn2/mcp-datahub:v1.9.0Verification
All release artifacts are signed with Cosign. Verify with:
cosign verify-blob --bundle mcp-datahub_1.9.0_linux_amd64.tar.gz.sigstore.json \
mcp-datahub_1.9.0_linux_amd64.tar.gzmcp-datahub-v1.8.1
mcp-datahub v1.8.1 — Fix OutputSchema Validation on Empty Search Results
Fixes a bug where datahub_search returned "entities": null instead of "entities": [] when a search matched zero results, causing MCP OutputSchema validation failures. This affected both keyword and semantic search modes.
Bug fix
datahub_search returns null entities on zero results (#131)
When a search query matched no entities, SearchResult.Entities was never initialized (Go nil slice), and json.Marshal serialized it as null. The OutputSchema declares entities as "type": "array" which rejects null, causing clients to receive a validation error instead of an empty result set.
Root cause: doSearchAcrossEntities and Search created the SearchResult struct without initializing the Entities slice. The slice was only populated via append in a loop over results — zero results meant the loop never executed and Entities stayed nil.
Fix: Initialize Entities with make([]SearchEntity, 0, len(results)) in both code paths. This produces "entities": [] in JSON and pre-allocates the right capacity when results do exist.
Affected methods:
client.SearchAcrossEntities()(keyword + semantic viadoSearchAcrossEntities)client.Search()(legacy type-scoped search)
Upgrading
This is a patch release with no breaking changes. All users of v1.8.0 should upgrade.
Installation
Claude Desktop (macOS/Windows)
Download the .mcpb bundle for your platform and double-click to install:
- macOS Apple Silicon (M1/M2/M3/M4):
mcp-datahub_1.8.1_darwin_arm64.mcpb - macOS Intel:
mcp-datahub_1.8.1_darwin_amd64.mcpb - Windows:
mcp-datahub_1.8.1_windows_amd64.mcpb
Homebrew (macOS)
brew install txn2/tap/mcp-datahubClaude Code CLI
claude mcp add datahub \
-e DATAHUB_URL=https://your-datahub.example.com/api/graphql \
-e DATAHUB_TOKEN=your-token \
-- mcp-datahubDocker
docker pull ghcr.io/txn2/mcp-datahub:v1.8.1Verification
All release artifacts are signed with Cosign. Verify with:
cosign verify-blob --bundle mcp-datahub_1.8.1_linux_amd64.tar.gz.sigstore.json \
mcp-datahub_1.8.1_linux_amd64.tar.gz