Skip to content
Enterpret Help Center home
InboxAsk a human

Connect Databricks to Enterpret Agent

Updated by Amlesh Prusty

In this article

In this article group

Connect a managed Databricks MCP server so Enterpret Agent can use the tools configured for your workspace. The selected server determines whether Agent can work with SQL, Genie, AI Search, or Unity Catalog functions.

This setup supports one managed Databricks MCP endpoint per Enterpret organization. Users authorize their own Databricks access to that configured endpoint.

Before you connect

You need an Enterpret Owner or Admin for the initial organization setup, a Databricks account administrator to register an OAuth application, and a Databricks user with access to the workspace and resources the Agent should use.

  1. Ask your Databricks account administrator to register a confidential OAuth application under Settings → App connections in the Databricks account console.

  2. Ask your Enterpret team for the exact callback URL for your Enterpret environment, and register that URL in the Databricks OAuth application.

  3. Configure delegated user access with the all-apis and offline_access scopes. Keep the OAuth client ID and secret for the initial setup.

  4. Copy the managed MCP server URL from your Databricks workspace. Use the actual endpoint for the server you want to connect; not every server type is available in every workspace.

  5. Confirm that your workspace network rules allow the connection.

The supported URL is an HTTPS workspace URL on *.cloud.databricks.com, *.azuredatabricks.net, or *.gcp.databricks.com, with a path under /api/2.0/mcp/ or /ai-gateway/mcp-services/. For example: https://your-workspace.cloud.databricks.com/api/2.0/mcp/sql.

Connect in Enterpret

  1. Open Settings → Agent → Connectors and find Databricks.

  2. An Enterpret Owner or Admin selects Connect and enters the Databricks MCP server URL, OAuth client ID, and OAuth client secret. Enter the secret only in its masked setup field.

  3. Complete Databricks sign-in and consent with the account whose access Agent should use.

  4. Return to Enterpret and check that the connection is ready and its available tools have loaded.

  5. Each additional user connects with their own Databricks account using the organization’s configured application. They do not need the OAuth client secret.

Test your connection

Open an Agent Session, enable Databricks, and ask a small question appropriate for your configured server. For a SQL server, a safe starting request is: “Use Databricks to run SELECT 1 AS connection_test. Do not read or change any customer tables.” Review the tool call and result.

The connector respects the connected user’s Databricks permissions and Enterpret’s tool approvals. It is not inherently read-only: SQL and function tools can change data when the selected server exposes those operations and access permits them.

Maintain the connection

An Owner or Admin can rotate the OAuth application credentials for the same configured server. To change the MCP server endpoint, contact your Enterpret team; changing the destination requires reconnection rather than simply replacing the URL.

Troubleshooting

  • The initial credential fields are unavailable: ask an Enterpret Owner or Admin to complete organization setup.

  • The URL is rejected: use the managed MCP URL from the supported workspace host and path. Custom domains, Databricks Apps URLs, and personal access tokens are outside this setup.

  • Sign-in fails: confirm that the OAuth callback URL, client credentials, environment, and delegated scopes match the registered app.

  • A tool or dataset is unavailable: check the selected MCP server’s tools and the connected user’s Databricks grants.

For shared authentication, connection status, and approval concepts, see Connectors.