The DataHub MCP Server implements the [Model Context Protocol (MCP)](https://modelcontextprotocol.io/introduction), which standardizes how applications provide context to LLMs and AI agents. This enables AI agents to query DataHub metadata and use it to find relevant assets, traverse lineage, and more.
Want to learn more about the motivation, architecture, and advanced use cases? Check out our [deep dive blog post](https://datahub.com/blog/datahub-mcp-server-block-ai-agents-use-case/).
There's two ways to use the MCP server, which vary in setup required but offer the same capabilities.
- [Managed MCP Server](#managed-mcp-server-usage) - Available on DataHub Cloud v0.3.12+
- [Self-Hosted MCP Server](#self-hosted-mcp-server-usage) - Available for DataHub Core
## Capabilities
**Search for Data** <br/>
Find the right data to use for your projects & analysis by asking questions in plain English - skip the tribal knowledge.
**Dive Deeper** <br/>
Separate the signal from noise with rich context about your data, including usage, ownership, documentation, tags, and quality.
**Lineage & Impact Analysis** <br/>
Understand the impact of upcoming changes to tables, reports, and dashboards using DataHub’s end-to-end lineage graph.
**Query Analysis & Authoring** <br/>
Understand how your mission-critical data is typically queried, or build custom queries for your tables.
**Works Where You Work** <br/>
Seamlessly integrates with AI-native tools like Cursor, Windsurf, Claude Desktop, and OpenAI to supercharge your workflows.
## Managed MCP Server Usage
For folks on DataHub Cloud v0.3.12+, you can use our hosted MCP server endpoint.
The managed MCP server endpoint is only available with DataHub Cloud v0.3.12+. For DataHub Core and older versions of DataHub Cloud, you'll need to [self-host the MCP server](#self-hosted-mcp-server-usage).
There are two [transports types](https://modelcontextprotocol.io/docs/concepts/transports) for remote MCP servers: streamable HTTP and server-sent events (SSE). DataHub only supports the newer streamable HTTP transport. SSE has been deprecated in favor of streamable HTTP, but some older MCP clients may still only support SSE. For those cases, you'll need to use something like [mcp-remote](https://github.com/geelen/mcp-remote) to bridge the gap.