Databricks

​

Overview

There are two ways to connect Databricks to Dust:

1. Official Databricks managed MCP servers (recommended): connect Dust directly to the MCP endpoints hosted and maintained by Databricks. Use this option first. It relies on the standard remote MCP server setup in Dust and gives agents access to Databricks SQL, Genie spaces, Unity Catalog functions, and vector search.
2. Dust-built Databricks tool: a Databricks tool built by Dust, configured with a dedicated OAuth application. Use it if the managed MCP servers are not available on your Databricks workspace.

---

​

Option 1: Official Databricks managed MCP servers (recommended)

Databricks hosts one MCP endpoint per capability. Each endpoint is added to Dust as a separate remote MCP server: See the Databricks managed MCP servers documentation for the full list.

​

Step 1: Find your Databricks workspace URL

The workspace hostname is the domain you see in your browser when you are logged into your Databricks workspace, for example dbc-a1b2c3d4-e5f6.cloud.databricks.com. You can also find it from the Account Console:

1. Go to the Databricks Account Console (on Azure, use the Azure portal).
2. In the left sidebar, click Workspaces.
3. Click the workspace you want to connect.
4. On the Configuration tab, the workspace URL is displayed at the top of the page, next to the workspace status. It also appears under Networking > Connectivity > Per-workspace URL.
5. Copy the URL without the trailing slash, for example https://dbc-a1b2c3d4-e5f6.cloud.databricks.com.

​

Step 2: Create an OAuth app connection in Databricks

You need Databricks account admin rights for this step.

1. Go to the Databricks Account Console.
2. In the left sidebar, click Settings.
3. Open the App connections tab. It lists the existing OAuth applications (Tableau, dbt, and so on).
4. Click the Add connection button in the top right corner of the list.
5. Fill in the Add connection form:
   • Application Name: Dust
   • Redirect URLs: add the Dust Static OAuth callbacks (one per line):
     https://dust.tt/oauth/mcp_static/finalize
     https://app.dust.tt/oauth/mcp_static/finalize
     https://eu.dust.tt/oauth/mcp_static/finalize
     
   • Access scopes: check All APIs, or the fine-grained scope matching the endpoint you want to connect (for example SQL for the /api/2.0/mcp/sql server)
   • Client secret: check Generate a client secret
   • Single-use Refresh Tokens: leave unchecked
   • Access token TTL (in minutes): 60 (default)
   • Refresh token TTL (in minutes): 10080 (default)
6. Click Add, then copy the Client ID and Client Secret from the confirmation dialog immediately.

​

Step 3: Add the MCP server in Dust

1. In Dust, go to Spaces > Administration > Tools.
2. Click Add Tools, then Add MCP Server.
3. Select the Static OAuth authentication method and fill in the fields:

4. Click Connect and complete the Databricks login flow.

5. To connect several capabilities (for example SQL and Genie), repeat the operation with one MCP server per endpoint. The same Databricks app connection can be reused if its scopes cover all endpoints.

​

Step 4: Add the tool to your agents

In the Agent Builder, click Add Tool and select your Databricks MCP server. Save or publish the agent.

​

Troubleshooting

---

​

Option 2: Dust-built Databricks tool

Use this option if the managed MCP servers are not available on your Databricks workspace.

​

Admin: Setup in Databricks

​

Create a Custom OAuth Application in Databricks

1. Log in to the Databricks Account Console
   • Go to accounts.cloud.databricks.com
   • Click the Settings icon in the sidebar
2. Navigate to App Connections
   • Click on the App connections tab
   • Click Add connection
3. Fill in Application Information
   • Connection Name: “Dust Integration”
   • Redirect URLs: Add both callback URLs:
     https://dust.tt/oauth/databricks/finalize
     https://eu.dust.tt/oauth/databricks/finalize
     
4. Configure Access Scopes
   • Select ALL APIs scope (required for full Databricks API access) The following scopes are automatically included:
   • openid, email, profile (for ID token generation)
   • offline_access (for refresh tokens)
5. Set Token Time-to-Live (TTL)
   • Access token TTL: 60 minutes (default, adjust as needed)
   • Refresh token TTL: 10080 minutes (default, adjust as needed)
6. Generate Client Secret
   • Check Generate a client secret (required for confidential clients)
   • Click Create

​

Get Your Credentials

After creation, a Connection created dialog will display:

• Client ID: Copy this value
• Client Secret: Copy and securely store this value immediately Important: You cannot retrieve the client secret later. Store it securely now.

---

​

Admin: Setup in Dust

1. Navigate to Tools Settings
   • Go to Spaces > Administration > Tools in your Dust workspace
   • Click Add Tools
   • Select Databricks
2. Enter Connection Details
   • Databricks Account URL: Your Databricks account URL (e.g., https://[your_workspace_url].cloud.databricks.com)
   • Client ID: The Client ID from your Databricks app connection
   • Client Secret: The Client Secret from your Databricks app connection
3. Choose Credentials Type
   • Personal: Each user must authenticate with their own Databricks account. Queries execute with individual user permissions (recommended for security and compliance)
   • Workspace: All users share the admin’s credentials and permissions when executing queries
4. Complete OAuth Flow
   • You’ll be redirected to complete the Databricks OAuth flow
   • Log in with an admin Databricks account to authorize the connection
   • Note: For Personal credential type, this admin account is only used during setup
5. Default Availability
   • By default, this tool is added to the Company data Space, making it accessible workspace-wide

​

Usage

​

Enable Databricks Tool on an Agent

1. In the Agent Builder
   • Click Add Tool
   • Select Databricks

​

First-Time User Experience (Personal Credentials)

When users interact with an agent using the Databricks tool for the first time with Personal credential type:

1. They’ll see an authentication prompt:
    Databricks authentication required
   You need to connect your Databricks account to use this tool.
   [Connect] button
   
2. After clicking Connect:
   • Users authenticate with their own Databricks credentials
   • OAuth flow completes
   • Status updates to show successful connection
3. Ready to Use:
   • Click Retry to re-run the agent query
   • All subsequent queries will use their authenticated account

​

Workspace Credentials Mode

If configured with Workspace credentials:

• No individual authentication required
• All users share the admin’s permissions
• Queries execute immediately