Skip to main content

Claude

Give Claude Code or Claude Desktop access to your enterprise data context in DataHub — find trustworthy data, trace lineage, look up ownership, and reference documentation while you work.

Prerequisites​

  • Claude Code or Claude Desktop installed
  • A DataHub instance: Cloud (OAuth on v1.0.2+, PAT on v0.3.12+) or self-hosted

Claude Code​

On DataHub Cloud v1.0.2+, Claude Code can use OAuth2 with Dynamic Client Registration — no token to mint or paste.

claude mcp add --transport http datahub https://mcp.datahub.com/mcp

The first DataHub call returns 401 Unauthorized, which Claude Code flags as needing authentication. Run /mcp inside Claude Code, select the DataHub server, and choose Authenticate — a browser opens for the DataHub OAuth flow. Enter your DataHub domain (e.g. <tenant> for https://<tenant>.acryl.io) and sign in. Tokens are stored and refreshed automatically.

Prefer your tenant URL directly? Swap the URL for https://<tenant>.acryl.io/mcp.

DataHub Cloud — Personal Access Token (Legacy)​

For service accounts or DataHub Cloud versions prior to v1.0.2, use a personal access token:

claude mcp add --transport http \
--header "Authorization: Bearer <token>" \
datahub-cloud \
"https://<tenant>.acryl.io/mcp"
Keep Your Token Secret

To avoid putting the token in your shell history, set it as an environment variable first:

export DATAHUB_TOKEN="<your-token>"
claude mcp add --transport http \
--header "Authorization: Bearer $DATAHUB_TOKEN" \
datahub-cloud \
"https://<tenant>.acryl.io/mcp"

DataHub Core​

Install uv (curl -LsSf https://astral.sh/uv/install.sh | sh), then:

claude mcp add datahub \
-e DATAHUB_GMS_URL="<your-datahub-url>" \
-e DATAHUB_GMS_TOKEN="<your-datahub-token>" \
-- uvx mcp-server-datahub@latest

Verify​

Run claude mcp list to confirm the DataHub server appears.

Claude Desktop​

Custom remote MCP connectors are available on Free, Pro, Max, Team, and Enterprise plans (Free is limited to one custom connector; Team/Enterprise restricts adding to Owners).

  1. Open Customize → Connectors. On Team/Enterprise, an owner adds it under Organization settings → Connectors.
  2. Click Add custom connector.
  3. Name: DataHub. Remote MCP server URL: https://mcp.datahub.com/mcp. Leave Advanced settings empty — DataHub registers the client via DCR automatically.
  4. Click Add, then Connect. A browser window opens for the DataHub OAuth flow.
  5. Enter your DataHub domain (e.g. <tenant>), sign in, and approve. The DataHub tools appear in Claude's tool menu (hammer icon).

Prefer your tenant URL directly? Use https://<tenant>.acryl.io/mcp as the connector URL instead.

note

Remote MCP connectors are configured via the Claude Desktop UI, not claude_desktop_config.json — that file is for local stdio servers only.

DataHub Cloud — mcp-remote Bridge (Legacy)​

For older Claude Desktop versions without native remote MCP support, use mcp-remote as a local bridge.

Open Claude Desktop → Settings → Developer → Edit Config and update claude_desktop_config.json:

{
"mcpServers": {
"datahub-cloud": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://<tenant>.acryl.io/mcp",
"--header",
"Authorization: Bearer <token>"
]
}
}
}

DataHub Core​

  1. Run which uvx to find the full path to uvx.
  2. Open Claude Desktop → Settings → Developer → Edit Config and update claude_desktop_config.json:
{
"mcpServers": {
"datahub": {
"command": "<full-path-to-uvx>", // e.g. /Users/you/.local/bin/uvx
"args": ["mcp-server-datahub@latest"],
"env": {
"DATAHUB_GMS_URL": "<your-datahub-url>",
"DATAHUB_GMS_TOKEN": "<your-datahub-token>"
}
}
}
}

Verify​

Restart Claude Desktop. The DataHub tools should appear in the tools menu (hammer icon).

Troubleshooting​

For general troubleshooting (authentication errors, empty results, uvx not found), see the MCP server guide.