Skip to content
GitHub (opens in a new tab)

Databases · Integration guide

How to connect Azure Databricks to any AI IDE (Claude/Codex/Cursor/VS Code/Antigravity)

Before you start, install GateRook and connect it to your AI development environment: Claude Desktop, Codex, Cursor, Antigravity or VS Code.

Connect your AI app

Azure Databricks uses GateRook’s Databricks SQL connector. Azure Databricks workspaces and their SQL warehouses.

The screenshots show GateRook 2.0.0: the Azure Databricks form, the endpoint selector, and this connector’s actual tool preview. The form and preview have not been saved. Select a screenshot to open it at full size.

1. Create a connection and enter the settings

In GateRook, open Connections, select Add connection, search for Azure Databricks, choose its card and select Continue to configure.

Open the Azure Databricks workspace and choose a SQL warehouse. Copy the workspace URL and warehouse connection details; this connector executes SQL against the warehouse.

For OAuth, create a Databricks service principal and its Databricks OAuth secret. Grant warehouse CAN USE and the required USE CATALOG, USE SCHEMA and SELECT permissions. An arbitrary Azure application secret is not automatically a Databricks OAuth secret.

Enter a Name, for example azure-databricks-demo. Your AI app uses this name to choose the connection.

Enter the HTTPS workspace address in Workspace URL. Set SQL warehouse ID to the ID at the end of /sql/1.0/warehouses/<ID> from the warehouse HTTP path, rather than pasting the entire path.

Under Sign in with, select A service principal (OAuth machine-to-machine, recommended) and enter Client ID and Client secret. If using the supported personal-token route, select A personal access token and fill Personal access token instead.

Set Default catalog and Default schema, and restrict Catalogs and Schemas to the required data.

Choose Development, Staging or Production to match the service. Review the connector’s limit and access settings before continuing.

GateRook 2.0.0 Configure Azure Databricks form before saving.
The Azure Databricks configuration form. Enter your own connection settings before testing.

2. Test the connection and add it to an endpoint

Select Continue to test. GateRook checks the settings from your computer. Review the result and resolve any connection, certificate or permission error before continuing.

If OAuth fails, confirm that the client and secret were created for Databricks and can access this workspace. If authentication works but SQL fails, check warehouse availability, CAN USE and the catalog/schema/table grants separately.

After the test passes, select Continue to add to an endpoint. Choose the endpoint your AI app uses, review its tool modes, then select Save connection. GateRook offers default as the starter endpoint.

GateRook endpoint selector with default selected; no connector tool list is shown.
Choose the endpoint your AI app uses. This selector is shared across connector types; the next screenshot shows this connector’s own tools.

3. Use the connection from your AI IDE

After saving Azure Databricks on the endpoint and passing its connection test, ask your AI app to use azure-databricks-demo, or the name you chose. If its tools are missing, confirm the endpoint assignment and refresh the MCP connection or start a new chat.

The preview below shows this connector’s default tools before saving. The table explains what each tool can do; connection settings, credentials and endpoint policies can restrict access further.

Azure Databricks connector tool names and default modes in the GateRook 2.0.0 endpoint preview.
Azure Databricks tools in the Development endpoint preview. This is an unsaved preview, not a successful service call.

Start with a small read request. Replace example resource names with existing resources your connection may access. Open Activity after the call to inspect its connection, tool, arguments, policy decision and result metadata.

Ask your AI, for example

  • “List the permitted catalogs and schemas in this Azure Databricks workspace.”
  • “Describe the columns of the orders table without modifying it.”
  • “Summarize daily order counts for the last week using a read-only SQL query.”
Tools your AI gets
ToolWhat it doesStarts as
databricks_list_catalogsUnity Catalog catalogs agents may use.Read only
databricks_list_schemasSchemas agents may use in one catalog.Read only
databricks_list_tablesTables, views and their kinds in one schema.Read only
databricks_describe_tableColumns with their types, partitioning, format and comment of one table or view.Read only
databricks_queryOne SELECT, WITH, VALUES, SHOW, DESCRIBE or EXPLAIN on the connection's SQL warehouse. Values as :name parameters. Pages with nextCursor.Read only
databricks_executeOne INSERT, UPDATE, DELETE, MERGE, DDL or table maintenance statement. You approve the exact text.Approval

You can change each tool’s mode on the endpoint. Every call your AI makes appears in Activity.

Service documentation

Keep exploring

Databricks SQL

Connect Databricks SQL to Claude, Codex, Cursor, VS Code or Antigravity with GateRook. Follow setup, connection testing and tool access with screenshots.

PostgreSQL

Connect PostgreSQL to Claude, Codex, Cursor, VS Code or Antigravity in three steps. Your AI runs read queries; changes wait for your approval.

MySQL

Connect MySQL to Claude, Codex, Cursor, VS Code or Antigravity in three steps. GateRook keeps the password; your AI reads data and asks before changes.

Browse all integration guides

Your local MCP gateway and firewall.

Connect Azure Databricks to your AI IDE.

Choose a connector. Start with read-only access. Approve changes and inspect the audit trail.

Read the getting started guide

Get GateRook

Download GateRook 2.0.0 for your Mac, or get the Windows app from Microsoft Store.

macOS

Version 2.0.0 for Apple Silicon (arm64). This download does not support Intel Macs.

Open the DMG and drag GateRook to Applications.

Windows

Available for free from Microsoft Store. Install GateRook and receive updates through the Store.

macOS release notes and checksums (opens in a new tab)