
Mcp Datahub
io.github.txn2Published by GitHub account txn2v1.15.1Updated Oct 24, 2026
MCP server for DataHub data catalogs. Discover datasets, explore lineage, and access metadata.
Overview
Connects an AI assistant to a DataHub metadata catalog so it can search datasets, read schemas, trace lineage and manage catalog entities.
- What you can do
- Search the catalog for datasets, dashboards and pipelines, and browse tags, domains and data products
- Read entity metadata by URN, dataset schemas, glossary terms, data product details and associated SQL queries
- Trace upstream and downstream lineage, including column-level lineage
- Create, update and delete catalog entities such as tags, domains, glossary terms, data products, documents, incidents and data contracts (write tools off by default)
- List configured DataHub connections and target a specific one in multi-server setups
- When to use it
- Useful when an assistant needs to answer questions about an organization's data estate: finding the right table, understanding its schema and owners, or seeing what depends on it. Also fits teams that want the assistant to maintain catalog metadata, not just read it.
- Requirements
- Runs as a local process installed from a macOS or Windows bundle, Homebrew or Go. Needs a reachable DataHub GraphQL endpoint and an API token, set via DATAHUB_URL and DATAHUB_TOKEN (or a YAML/JSON config file). DataHub 1.3.x or newer; documents need 1.4.x. Optional DATAHUB_ADDITIONAL_SERVERS for multiple instances.
Installation
In SourceWeft
- Open Mcp Datahub in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
[GitHub license] [Go Reference] [Go Report Card] [codecov] [OpenSSF Scorecard] [SLSA 3]
An MCP server and composable Go library that connects AI assistants to DataHub metadata catalogs. Search datasets, explore schemas, trace lineage, and access glossary terms and domains.
mcp-datahub.txn2.com | Installation | Library Docs
MCP Data Platform Ecosystem
mcp-datahub is part of a broader suite of open-source MCP servers designed to work together as a composable data platform. Each component can run standalone or be combined to give AI assistants unified access to storage, query engines, and metadata catalogs.
Two Ways to Use
1. Standalone MCP Server
Install and connect to Claude Desktop, Cursor, or any MCP client:
Claude Desktop (Easiest) - Download the .mcpb bundle from releases and double-click to install:
- macOS Apple Silicon:
mcp-datahub_X.X.X_darwin_arm64.mcpb - macOS Intel:
mcp-datahub_X.X.X_darwin_amd64.mcpb - Windows:
mcp-datahub_X.X.X_windows_amd64.mcpb
Other Installation Methods:
Manual Claude Desktop Configuration (if not using MCPB):
Multi-Server Configuration
Connect to multiple DataHub instances simultaneously:
Use datahub_list_connections to discover available connections, then pass the connection parameter to any tool.
2. Composable Go Library
Import into your own MCP server for custom authentication, tenant isolation, and audit logging:
Customizing Tool Descriptions
Override tool descriptions to match your deployment:
Customizing Tool Annotations
Override MCP tool annotations (behavior hints for AI clients):
All 12 tools ship with default annotations: read tools are marked ReadOnlyHint: true; datahub_create is non-destructive and non-idempotent; datahub_update is non-destructive and idempotent; datahub_delete is destructive and idempotent.
Extensions (Logging, Metrics, Error Hints)
Enable optional middleware via the extensions package:
See the library documentation for middleware, selective tool registration, and enterprise patterns.
Combining with mcp-trino
Build a unified data platform MCP server by combining DataHub metadata with Trino query execution:
See txn2/mcp-trino for the companion library.
Bidirectional Integration with QueryProvider
The library supports bidirectional context injection. While mcp-trino can pull semantic context from DataHub, mcp-datahub can receive query execution context back from a query engine:
When a QueryProvider is configured, tool responses are enriched:
- Search results: Include
query_contextwith table availability - Entity details: Include
query_table,query_examples,query_availability - Schema: Include
query_tablefor immediate SQL usage - Lineage: Include
execution_contextmapping URNs to tables
Integration Middleware
Enterprise features like access control and audit logging are enabled through middleware adapters:
See the library documentation for complete integration patterns.
Available Tools
Read Tools (always available)
Write Tools (require DATAHUB_WRITE_ENABLED=true)
3 CRUD tools using the what discriminator pattern — 37 operations total:
Write tools are disabled by default for safety.
DataHub Version Compatibility
Minimum: DataHub 1.3.x. Full feature set: DataHub 1.4.x.
The client gracefully handles version differences — read queries return empty results (not errors) when a feature is unavailable on older versions.
See the tools reference for detailed documentation.
Configuration
Extensions
Config File
As an alternative to environment variables, configure via YAML or JSON:
Load with extensions.LoadConfig("config.yaml"). Environment variables override file values for sensitive fields. Token values support $VAR / ${VAR} expansion.
See configuration reference for all options.
Development
Related Projects
- txn2/mcp-trino (docs) - Composable MCP toolkit for Trino query execution
- DataHub - The open-source metadata platform
Contributing
See CONTRIBUTING.md for guidelines.
License
Open source by Craig Johnston, sponsored by Deasil Works, Inc.
Source: README.md at commit 8b66462
Tools
0Version history
1- v1.15.1LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts