Cursor

Give Cursor access to your enterprise data context in DataHub — find trustworthy data, trace lineage, look up ownership, and reference documentation without leaving the editor.

Prerequisites

Cursor v1.1+
A DataHub instance: Cloud (OAuth on v1.0.2+, PAT on v0.3.12+) or self-hosted

DataHub Cloud — OAuth (Recommended, v1.0.2+)

On DataHub Cloud v1.0.2+, Cursor can connect via OAuth2 with Dynamic Client Registration — no token to mint or paste.

Navigate to Cursor → Settings → Cursor Settings → Tools & MCP → New MCP Server (or edit ~/.cursor/mcp.json globally / .cursor/mcp.json per project) and paste:

json

{
  "mcpServers": {
    "datahub": {
      "url": "https://mcp.datahub.com/mcp"
    }
  }
}

Save. Cursor opens a browser tab for the DataHub OAuth flow (callback cursor://anysphere.cursor-mcp/oauth/callback) — 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? Replace the URL with https://<tenant>.acryl.io/integrations/ai/mcp.

DataHub Cloud — Personal Access Token (Legacy)

For service accounts or DataHub Cloud versions prior to v1.0.2, use a personal access token. Navigate to Cursor → Settings → Cursor Settings → MCP, add a new server, and paste:

json

{
  "mcpServers": {
    "datahub-cloud": {
      "url": "https://<tenant>.acryl.io/integrations/ai/mcp/",
      "headers": {
        "Authorization": "Bearer <token>"
      }
    }
  }
}

Replace <tenant> with your DataHub Cloud tenant name and <token> with your personal access token.

:::tip Keep Your Token Secret If your MCP config is checked into version control, reference an environment variable instead of a literal token:

json

"Authorization": "Bearer ${DATAHUB_TOKEN}"

:::

Self-Hosted DataHub

Install uv (curl -LsSf https://astral.sh/uv/install.sh | sh), then add a new MCP server in Cursor settings with:

json

{
  "mcpServers": {
    "datahub": {
      "command": "uvx",
      "args": ["mcp-server-datahub@latest"],
      "env": {
        "DATAHUB_GMS_URL": "<your-datahub-url>",
        "DATAHUB_GMS_TOKEN": "<your-datahub-token>"
      }
    }
  }
}

Verify

After saving, the MCP settings page should show a green dot and list the DataHub tools. If the dot doesn't appear, check that:

The JSON is valid (no trailing commas).
For self-hosted: uvx is on Cursor's PATH — run which uvx and use the full path in command if needed.

For general troubleshooting, see the MCP server guide.