Integrates with DataHub's API to enable metadata management, discovery, and governance across diverse data assets in com...
Created byApr 22, 2025
mcp-server-datahub
A Model Context Protocol server implementation for DataHub.
This enables AI agents to query DataHub for metadata and context about your data ecosystem.
Supports both DataHub Core and DataHub Cloud.
Features
Searching across all entity types and using arbitrary filters
Fetching metadata for any entity
Traversing the lineage graph, both upstream and downstream
Listing SQL queries associated with a dataset
Demo
Check out the demo video, done in collaboration with the team at Block.
Locate your authentication detailsFor authentication, you'll need the following:You can also use a ~/.datahubenv file to configure your authentication. The easiest way to create this file is to run datahub init and follow the prompts.
Configure your MCP client. See below - this will vary depending on your agent.
Claude Desktop
Run which uvx to find the full path to the uvx command.
In your claude_desktop_config.json file, add the following:
Cursor
In .cursor/mcp.json, add the following:
Other MCP Clients
Troubleshooting
`spawn uvx ENOENT`
The full stack trace might look like this:
Solution: Replace the uvx bit of the command with the output of which uvx.
Developing
See DEVELOPING.md.
mcp-server-datahub
A Model Context Protocol server implementation for DataHub.
This enables AI agents to query DataHub for metadata and context about your data ecosystem.
Supports both DataHub Core and DataHub Cloud.
Features
Searching across all entity types and using arbitrary filters
Fetching metadata for any entity
Traversing the lineage graph, both upstream and downstream
Listing SQL queries associated with a dataset
Demo
Check out the demo video, done in collaboration with the team at Block.
Locate your authentication detailsFor authentication, you'll need the following:You can also use a ~/.datahubenv file to configure your authentication. The easiest way to create this file is to run datahub init and follow the prompts.
Configure your MCP client. See below - this will vary depending on your agent.
Claude Desktop
Run which uvx to find the full path to the uvx command.
In your claude_desktop_config.json file, add the following:
Cursor
In .cursor/mcp.json, add the following:
Other MCP Clients
Troubleshooting
`spawn uvx ENOENT`
The full stack trace might look like this:
Solution: Replace the uvx bit of the command with the output of which uvx.