Claude Databricks Genie connectorWhat Claude can do in your Databricks Genie account.
The Claude Databricks Genie connector exposes 5 tools. 4 read your data through Genie, 0 are documented as changing anything, and 1 is described without a clear read or write effect. Below: what you can ask, who controls access, and where it stops.
Verified Trustpilot reviews · AI, automation & growth agency
What the Claude Databricks Genie connector changes for analysts
A sales director wants last quarter's churn by region and doesn't know which table holds it. Instead of filing a request with the data team, she types the question to Claude. Claude hands it to Genie, the Databricks assistant that searches your data and writes the SQL, and brings back an answer with links to the Databricks sources it cited.
Get a figure without knowing SQL. genie_ask passes a question in everyday language to Genie, which searches your data, drafts the query itself and returns a conversation reference. Claude then follows the answer with genie_poll_response until it is ready, with the progress steps and the source links attached.
See the answer, not just read it. In Claude, view_ask opens an interactive panel inside the conversation where Genie shows its progress, its charts and the final result. Databricks says clients that can display this panel get it with no extra setup.
Pull the full table when the summary is not enough. To keep the conversation readable, Genie shortens the results it sends back. When you need every row, genie_get_query_result fetches the complete result of a query Genie ran, with its columns.
Now what the connector does not do. Your Unity Catalog permissions apply on every request: Claude only reaches the data you could already query yourself. No tool on the sheet is documented as modifying a table or a dashboard. And nothing runs on its own: no report lands on Monday morning unless someone asks for it in a conversation. For scheduled extractions, look at the Databricks Genie n8n integration or the Databricks Genie Make integration, which are built to run without anyone watching.
Five words before you plug it in
- Connector
- The link you set up once between Claude and an account you already have, so Claude can work in it while answering you.
- Tool
- One named action a connector opens to Claude. Claude picks the ones it needs by itself, and the directory lists them by name.
- Authorization
- The sign-in screen of the service itself, where you hand Claude the access it will use. Granted once per person, and revocable.
- Approval
- The confirmation Claude waits for in the conversation before going ahead with something that would alter an account.
- MCP
- The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service such as Databricks.
Plug Databricks Genie into Claude in three steps
- 01
Find Databricks Genie in Claude
In Claude's settings, open Customize, then Connectors, and look for Databricks Genie in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to switch the connector on first so each member can sign in.
- 02
Start the connection
Click Connect on its row, then sign in to Databricks in the window Databricks opens itself. If the link breaks later, use Disconnect and plug it in again from the same place.
- 03
Read the authorization screen
Take a moment on the authorization screen before you accept. It belongs to Databricks, not to Claude, and it is what decides the scope of the access you grant. That access can also be withdrawn later from the Databricks side.
The 5 tools, sorted by what they do
Databricks Genie gives Claude 5 tools: 4 that read your account, 0 that change something in it, and 1 no official source describes.
Two groups here: what Claude reads through Genie, and one tool no source ties to a read or a write. Names stay exactly as Claude shows them.
- 4 read
- 1 not documented
What Claude reads (4)
4 toolsFour tools that query your data through Genie.
genie_ask
Hands your question, phrased in everyday words, to Genie and opens a response. Genie searches your data, produces the SQL query and returns a reference to the conversation so follow-up questions keep the same context.
genie_poll_response
Genie answers asynchronously, so Claude checks back on a response that is still running or already finished. It gets the progress steps, the final answer and links pointing to the cited Databricks sources.
genie_get_query_result
Retrieves the complete output of a query Genie ran: the column layout and every row, rather than the shortened version shown in the answer.
view_ask
Puts a question to Genie and opens the interactive view inside the conversation, where progress, charts and results appear as they arrive. Databricks offers it in place of the plain question tool when the client can show the panel.
Not classified (1)
1 toolDescribed by Databricks, but no source says whether it reads or alters anything, so we leave it unclassified.
genie_cancel_response
Databricks describes this one as a request to stop a Genie turn in progress. No source says whether that touches your data or not, so this page does not class it as a read or a write.
What Claude asks before acting
By default, Claude pauses and asks for your go-ahead before any action it takes on an account in your place. The request shows up in the conversation, at the moment it matters.
On a Team or Enterprise workspace, owners decide whether a member may let some actions run without being asked each time. They can also limit what a connector may do for the whole organization, keeping reads open and closing writes, for instance, and nobody overrides that from their own account. On the Databricks side, Unity Catalog grants decide who may call the Genie service at all, and service policies can allow or refuse individual tool calls, each one logged for audit. Claude works with your rights and nothing more: a table you cannot query, it cannot query either.
Which plans include it
Out of 819 sheets in the official directory, none shows availability per plan. That connector-by-connector answer is published nowhere: a real gap in the catalogue, not in our research.
The general rule is public: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner turns the connector on for the organization before members can sign in. For the current state, check the connector's sheet in the official directory. Databricks adds that Genie usage is billed on its side, under its own Genie pricing.
Where the Claude Databricks Genie connector stops
A connector is not an automation. Claude calls these tools while answering you: nothing starts when a table refreshes or a metric crosses a threshold.
This connector is documented only by its publisher: no Claude help article covers it, so what follows comes from the Databricks documentation and the directory sheet. By default the sheet shows no documented write, but that is an observed floor, not a promise: an administrator can open actions that appear on no public sheet. The directory's partner badge is not a security audit either, and Anthropic says on every sheet that it does not choose the tools a publisher exposes. To see a connector that does write, compare with the Claude gmail connector.
Need help connecting Databricks Genie to Claude?
A person reads every message.
